developing-plan-reviewers
Create project-specific plan reviewer agents that integrate with the planning-project-features workflow. Use when a project needs domain-specialized reviewers for sub-plans (e.g., Go code reviewer, API layer reviewer, database reviewer) or when the planner warns that no suitable local reviewer exists for a sub-plan's domain.
npx skills add majiayu000/claude-skill-registry --skill developing-plan-reviewers --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Developing Plan Reviewers Create project-specific reviewer agents for the `planning-project-features` workflow. These agents review individual sub-plans for domain-specific correctness — catching issues that the generic global reviewers (architecture, risk) cannot. For general agent development guidance (frontmatter fields, description examples, system prompt design), see the `developing-agents` skill. ## How Plan Reviewers Fit In The planning workflow (Phase 5) uses two types of reviewers: 1. **Global reviewers** (`~/.claude/agents/`) — `plan-architect-reviewer` and `plan-risk-reviewer`. Project-agnostic, already exist. 2. **Local reviewers** (`.claude/agents/`) — project-specific, domain-specialized. **This is what you build.** The planner discovers local reviewers in Phase 4 by reading their descriptions, matches each sub-plan to the most appropriate reviewer, and launches them in Phase 5. No naming convention is assumed — the description is what matters. ## Design Philosophy A reviewer agent is a **thin shell**. It defines: - **What to review** — the domain scope (via description and skills list) - **How to output** — the standard review format (Verdict / Findings / Concerns
- How Plan Reviewers Fit In
- Design Philosophy
- Reviewer Agent Template
- Key Choices
- Choosing Skills to Preload
- Standard Output Format
- Examples
- Rules
What does the developing-plan-reviewers skill do?
Create project-specific plan reviewer agents that integrate with the planning-project-features workflow. Use when a project needs domain-specialized reviewers for sub-plans (e.g., Go code reviewer, API layer reviewer, database reviewer) or when the planner warns that no suitable local reviewer exists for a sub-plan's domain.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill developing-plan-reviewers --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.