rcc

Analyze existing agent system for weaknesses across 9 categories

Execute component plan by invoking writing-* skills in order

Explore user workflows with role templates to design agent system

Initialize new project with Claude Code agent system, best practices, and framework setup

Migrate existing agent system to Claude Code best practices architecture

Plan agent system components with traceability and reuse analysis

Refactor and health-check a Claude Code plugin against official best practices

Analyze and refactor skills - consolidate, optimize, remove redundancy

Review and cleanup agent system - compare before/after, fix remaining issues

Analyze conversation to extract learnings and integrate into skill library or rules

Create CLAUDE.md with law constitution, project structure, and quality review

Create new skill with Task List enforcement, quality review, and best practices

Use this agent after creating or modifying a CLAUDE.md file. Reviews quality including instruction specificity, token efficiency, correct separation of concerns, and actionability.

Use this agent after creating or modifying a hook. Reviews quality including exit code contract, performance, file filtering, settings.json registration, and security.

Use this agent after creating or modifying a rule file in .claude/rules/. Reviews quality including frontmatter paths, rule specificity, and no duplication with CLAUDE.md laws.

Use this agent after creating or modifying a skill. Reviews skill quality against best practices including frontmatter, description triggers, line count, naming conventions, and progressive disclosure.

Use this agent after creating or modifying a subagent. Reviews quality including single responsibility, tool minimalism, model selection, context isolation, and trigger clarity.

Use when starting any skill/agent/rule workflow to validate approach. Use when classifying knowledge type (CLAUDE.md vs rule vs skill vs agent vs hook). Use when checking for component conflicts.

Use when analyzing an existing agent system for weaknesses. Use when user says "analyze agent system", "check agent setup", "audit agent config". Use when called by migrating-agent-systems or refactoring-skills.

Use when executing a component plan to build agent system elements. Use when called by planning-agent-systems after plan is confirmed. Use when user says "apply agent plan", "build agent system".

Use when exploring user workflows to design an agent system. Use when user says "explore workflows", "brainstorm workflows", "what workflows should I automate". Use when called by analyzing-agent-systems or migrating-agent-systems.

Use when creating a new Claude Code plugin package. Use when user says "create plugin", "new plugin", "scaffold plugin", "plugin template".

Use when optimizing a single existing skill. Use when user says "improve skill", "optimize skill", "update skill", "skill needs work". Use when one specific skill is outdated or underperforming. NOT for multi-skill consolidation (use refactoring-skills instead).

Use when bootstrapping a new project from scratch. Use when user says "create project", "new project", "initialize project", "start new app".

Use when setting up or migrating Claude Code agent system for a project. Use when user says "setup agent", "migrate agent system", "configure claude code", "add agent system".

Use when planning which agent system components to create or modify. Use when called by brainstorming-workflows after workflow exploration is complete.

Use when reviewing and cleaning up an agent system after creation or modification. Use when user says "review agent system", "cleanup agent system", "refactor agent setup". Use when called by applying-agent-systems.

Use when refactoring, migrating, or auditing a Claude Code plugin package. Use when user says "refactor plugin", "audit plugin", "plugin health check", "migrate plugin structure". Use when plugin structure drifts from official best practices.

Use when analyzing and refactoring multiple skills across a project. Use when user says "refactor skills", "cleanup skills", "consolidate skills", "skill review". Use when skills overlap, are redundant, or need cross-skill consolidation. NOT for improving a single skill (use improving-skills instead).

Use when completing significant work to extract learnings. Use when user says "reflect", "what did we learn", "capture learnings". Use after resolving complex problems or discovering patterns.

Use when reviewing agent system components after creation or modification. Use when called by applying-agent-systems after all components are built. Use when user says "review agent system", "check quality".

Use when creating CLAUDE.md, improving existing CLAUDE.md, or setting up project configuration. Use when user says "create CLAUDE.md", "setup project", "configure agent".

Use when creating Claude Code hooks for code quality, static analysis, or workflow automation. Use when user says "add hook", "enforce linting", "add pre-commit check", "block bad code".

Use when creating rule files in .claude/rules/, adding project conventions, or scoping guidelines to specific paths. Use when user says "add rule", "create convention", "scope guideline". NOT for broad project instructions (use CLAUDE.md).

Use when creating new skills, modifying existing skills, or improving skill quality. Use when user says "create a skill", "write a skill", "add capability". Use when a repeated pattern should become reusable.

Use when creating specialized Claude Code subagents in .claude/agents/. Use when user says "create agent", "add reviewer", "specialized agent", "isolated context task".