Use this skill when an operator wants an agent to follow a maintained engineering workflow library instead of improvising each coding, review, planning, or documentation task from scratch. Ring ships a multi-plugin skills library with core software engineering practices, specialized developer agents, product planning workflows, and technical writing specialists.

## What the agent/operator does

1. Choose the Ring plugin set that matches the work: default core practices, dev-team implementation and review agents, pm-team planning workflows, or tw-team documentation workflows.
2. Install Ring through the supported host mechanism, such as Claude Code plugin marketplace, Codex plugin manifests, OpenCode plugin config, Cursor plugin manifests, or the symlink installer.
3. Start a session so Ring’s bootstrap skill or plugin configuration exposes the relevant skills and agents.
4. Route tasks into concrete Ring workflows such as test-driven development, systematic debugging, planning-small-features, reviewing-code, dependency security auditing, pull-request shipping, guide writing, or API documentation review.
5. For code review, dispatch the default and conditional reviewer agents that match the changed stack, then consolidate findings before implementation or merge.
6. Keep the selected scope narrow to the current engineering process rather than installing every team-specific plugin for every task.

## When to invoke

Invoke this instead of using an agent product normally when the main risk is process drift: skipping tests, missing root-cause analysis, shallow reviews, unclear PR shipping, or inconsistent product and documentation handoffs. It is strongest when a team wants repeatable engineering gates encoded as skills and specialist agents.

## Scope boundary

This is not a generic plugin marketplace listing or a claim that one skills library fits every organization. Keep the workflow scoped to installing and invoking Ring’s maintained engineering skill packs for specific TDD, debugging, review, planning, and documentation tasks. The Lerian-specific content should be treated as upstream defaults that may need pruning for another team.

## Requirements

– A supported agent host such as Claude Code, Codex, OpenCode, Cursor, or Factory AI.
– Git access to the Ring repository or the Claude Code plugin marketplace flow.
– For the code analysis pipeline, Go tooling is needed to install Mithril where that workflow is used.
– A software project where Ring’s engineering workflows can operate.

## Installation

For Claude Code, install from the plugin marketplace or add the Ring marketplace and install the relevant plugin set. For Codex, OpenCode, and Cursor, use the native plugin manifests in the Ring repository. For local development across hosts, clone the repository and run the symlink installer:

git clone https://github.com/LerianStudio/ring.git ~/ring
cd ~/ring
bash ring-install.sh –claude
bash ring-install.sh –codex
bash ring-install.sh –opencode

Use ring-default alongside any specialized Ring plugin because it provides the bootstrap and shared practices.

## Verification notes

Source metadata was verified from the exact GitHub repository, Claude plugin marketplace manifest, and upstream README. As of this intake run, LerianStudio/ring had 205 GitHub stars, 24 forks, an Apache-2.0 license, push activity within the last day, and README evidence for 4 active plugins, 76 skills, 33 agents, Claude Code marketplace support, Codex/OpenCode/Cursor manifests, symlink installation, code review orchestration, TDD, systematic debugging, product planning, and technical writing workflows.