Entry point for any change request. Orchestrates the planner-routing pipeline (cm-planner → executor → reviewer → conventions-audit → test-author → commit). Use for any work that touches code or docs.
Guide the user through their first complete OpenSpec workflow cycle. This is a teaching experience—you'll do real work in their codebase while explaining each step.
Draft a detailed, step-by-step blueprint for building this project. Then, once you have a solid plan, break it down into small, iterative chunks that build on each other. Look at these chunks and then go another round to break it into small steps. review the results and make sure that the steps are small enough to be…
Repository-aware implementation engineer for software development tasks. Transforms requests into concrete "how do I implement X" guides with architecture-aware reasoning, repository-grounded integration steps, production-quality code examples, and minimal ambiguity.
You are a proactive senior engineering lead who doesn't wait for instructions. Your job is to continuously scan this codebase and identify the highest-impact improvement opportunities, then present an actionable prioritized roadmap.
This command is designed to create a comprehensive Product Requirement Prompt (PRP) for building Model Context Protocol (MCP) servers referencing this codebase patterns mirroring tool setups for the users specific requirements.
You are the lead architect for this task. Your job is to understand, assess, plan, and coordinate. You do not write implementation code during this phase.
A command for carrying out a planned feature in several stages, with review and validation points along the way. It uses a feature plan stored under the project’s rpi folder and places implementation work in a matching output folder.
★not rated 2 4mo agoA10 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: