rpi-kit

Merge delta specs into main specs and clean up the feature directory.

Analyze the codebase and generate a CLAUDE.md with project rules, conventions, and architecture.

Quill generates and updates documentation based on the implementation.

Analyze the entire project for technical health, code quality, test coverage, ecosystem status, and product gaps. Generates a prioritized evolution report with actionable opportunities.

Quick bugfix — Luna interviews, Mestre plans (max 3 tasks), Forge implements. One command.

Execute the plan task by task with Forge. Sage assists with tests if TDD enabled.

Configure RPIKit and generate project-context.md by analyzing your codebase.

Manually capture a solution or insight to the knowledge base.

Start a new feature. Luna interviews you, explores approaches, and creates REQUEST.md + DESIGN.md.

First-time setup — analyzes your codebase, generates context, and guides you through your first feature.

Multi-agent debate on any topic. Nexus facilitates, 3-5 agents discuss.

Interview developer, generate specs with Mestre/Clara/Pixel, then adversarial review with Nexus.

Analyze feasibility with Atlas (codebase) and Scout (external). Nexus synthesizes.

Adversarial review with Hawk + Shield + Sage in parallel. Nexus synthesizes.

Auto-progress a feature to its next phase. Detects current state and runs the appropriate step.

Razor analyzes the implementation for reuse, quality, and efficiency improvements.

Show all features, their current phase, and progress.

Personalized coding tutor that adapts to your experience level and uses your real project code as examples.

Update RPIKit plugin to the latest version from the remote repository.

Methodical codebase explorer who maps patterns, conventions, and architecture. Spawned by /rpi:research.

Product manager focused on value who cuts scope ruthlessly. Spawned by /rpi:plan.

Disciplined executor who follows the plan precisely, one task at a time. Spawned by /rpi:implement.

Adversarial code reviewer who is forced to find problems. Spawned by /rpi:review.

Curious analyst and design thinker who elicits requirements and explores approaches through adaptive interviews. Spawned by /rpi:new.

Pragmatic architect who designs systems and hates over-engineering. Spawned by /rpi:plan.

Synthesizer and facilitator who merges agent outputs and moderates debates. Used across all phases and in party mode.

Empathetic UX designer who thinks from the user's perspective. Conditional — only activated for frontend projects. Spawned by /rpi:plan.

Clear and concise technical writer. Spawned by /rpi:docs.

Ruthless simplifier who eliminates unnecessary code. Spawned by /rpi:simplify.

Rigorous tester who finds edge cases and verifies coverage. Spawned by /rpi:implement (TDD) and /rpi:review.

External investigator who researches technical feasibility, libraries, and risks. Spawned by /rpi:research.

Security sentinel, paranoid by nature. Audits for vulnerabilities and edge cases. Spawned by /rpi:review.

This skill should be used when the user asks about RPIKit agents, their roles, or behavior.

This skill should be used when the user wants to develop a feature systematically, asks "how do I start a new feature", "walk me through the workflow", or mentions any RPI command.