capstone plugin

What's inside capstone

12 parts read from the plugin's own files.

Skills in capstone

1. 
   coreGentBajko/capstone

   Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.

   35 files
   5stars
2. 
   doctorGentBajko/capstone

   Use when the capstone docs area needs a consistency check or repair - torn writes, done markers without ledger entries, voided plan approvals, index rows pointing at missing files, absorption gaps - reports findings with their owning rules, then applies only the repairs the user approves.

   5stars
3. 
   featureGentBajko/capstone

   Use when the user wants one feature taken from idea to working code - "add a feature", "build X end to end", "take X from idea to shipped" - runs the feature chain groom → plan → implement consecutively, detecting the feature's stage and resuming at the first incomplete one. For the whole-product greenfield pipeline use start; to execute an already-approved plan use implement. Always asks subagents or inline before each new or resumed run.

   5stars
4. 
   groomGentBajko/capstone

   Use when starting work on a feature or change for a project that already has capstone docs - "new feature", "add a feature", "implement X", "build X", "design a feature", "spec it out", "flesh out", "refine this idea", "let's work on X" - a doc-grounded one-question-at-a-time interview producing a traceable feature spec in docs/capstone/features/, the first stage of the feature chain before plan and implement. Not whole-product discovery (mockup), not the greenfield pipeline (start); to carry one feature from idea to working code in a single run use feature.

   5stars
5. 
   helpGentBajko/capstone

   Use when asked what the capstone plugin can do - prints the usage block.

   5stars
6. 
   implementGentBajko/capstone

   Use when an approved feature plan is ready to become code - executes plan.md task by task with verification, in subagents or inline as you pick, reviews the diff recursively until no new findings survive, then refreshes the affected reference chapters.

   5stars
7. 
   mapGentBajko/capstone

   Use when asked to build, refresh, update, or check a codebase's architecture reference docs - "map the codebase", "document this repo", "are the docs current", "bring the docs in line with the code" - writes a docs/capstone/ index plus topic chapters, the logic/ business-logic map and the uiux/ surface map, then on later runs rewrites only the files whose covered paths drifted. One verb for both - no reference yet means build it, an existing one means refresh it. "map check" is the read-only trust report that writes nothing; "map rebuild" forces a full rewrite; a topic name targets one chapter.

   5stars
8. 
   planGentBajko/capstone

   Use when a groomed feature spec needs an implementation plan - studies the chapters the spec cites, writes a task-by-task TDD plan an engineer with zero context could execute, gated on user approval.

   5stars
9. 
   reviewGentBajko/capstone

   Use when asked for an opinionated review of the codebase - architecture/backend findings, UI findings against the project's own design docs, or both - severity-ranked with evidence, written to docs/capstone/review.md. Bare "review" does both sides; "review backend" or "review frontend" does one. "review retro [session]" is the third judgment axis - it reads a finished session and proposes edits to standards.md and the project's AGENTS.md/CLAUDE.md instead of judging code. Opt-in judgment; never edits code.

   5stars
10. 
    startGentBajko/capstone

    Use when the user says just "capstone" with nothing else, or asks to start or continue the capstone pipeline - runs the greenfield chain one stage at a time, detecting completed stages and resuming at the first incomplete one. A stage word as the argument (mockup, logic, uiux, architecture, standards, stack, build) enters that one stage directly; "start stack refresh" re-vets recorded picks. The session review is not here - that is "review retro". Always asks subagents or inline before each new or resumed run.

    5stars