Executes an implementation plan created by the makeplan skill. Use when the user says "execplan", "run the plan", "execute the plan", "implement the plan in plans/ ", or "continue the plan for ". Accepts a feature name and an optional commit-mode flag: --ask-commit (default, ask after each verified task), --no-commit…
Relentlessly interrogate a design to eliminate ambiguity before any planning, requirements, or implementation work begins. Use for "grill me", "grillme", "disambiguate", "deep-dive", or "interview me about this". Runs a structured, branch-by-branch interview: maps the design tree of major decision branches, walks each…
Creates a detailed, multi-document implementation plan for a software feature or task before any code is written. Use when the user wants to "make a plan", types "makeplan", or asks to "plan this feature", "create an implementation plan", "plan out this work", or "write a spec/plan" for something to be built. Drives a…
Gather and document requirements, turn an idea into formal requirement documents (RDs). Use for "makerequirements" (full discovery: brain dump or bare idea into a structured requirements/ set), "addrequirement" (add one new RD to an existing set), and "reviewrequirements" (health check / gap analysis on an existing…
Runs a rigorous multi-dimensional quality audit of a plan, requirements, or any artifact, grounded in the actual codebase. Use for "preflight", "quality audit", "review gate", "audit this plan", "audit these requirements", or "review my plan/requirements before I build it". An adversarial review gate that hunts for…
Reverse-engineer an existing codebase into structured requirements. Use for "retrorequirements", "reverse requirements", "reconstruct requirements from code", "requirements archaeology", or "reverse-engineer this codebase". Trigger when the user wants to reconstruct requirements from an existing, undocumented, or…
Tracks features across their lifecycle in a live, per-repo roadmap — every RD, plan, and task and the lifecycle stage each is in. Layout-aware: a single plans/00-roadmap.md in flat layout, or a two-tier per-feature + portfolio roadmap under codeops/ in nested layout. Use when the user says "roadmap", "makeroadmap"…
Sets up the CodeOps nested codeops/ layout in the current git repo — scaffolds a fresh skeleton or auto-migrates an existing flat-layout repo (requirements/ + plans/) into it. Use when the user says "setupcodeops", "/setupcodeops", "set up codeops", "initialize codeops", "migrate to the nested layout", "convert my…
Configures per-project model and effort routing so Opus + high/xhigh thinking is spent only where it changes output quality and high-volume mechanical work runs on Sonnet. Use when the user says "setuprouting", "/setuprouting", "set up model routing", "configure model routing", "route tasks by model", or "make this…
Creates and maintains VitePress-compatible technical architecture documentation and architecture decision records (ADRs). Use when the user says "maketechdocs", "reviewtechdocs", "techdocs", "document the architecture", "create architecture docs", "write ADRs", or "architecture decision records". Covers two modes…
Upgrades an outdated plan or requirements set to current CodeOps standards. Use when the user says "upgradeplan", "upgraderequirements", "upgrade my plan", "upgrade my requirements", "bring my plan up to date", "bring my requirements up to date", or asks for a "version upgrade" of a plan/requirements set. ONE skill…