GentBajko/capstone / skills/core
core
VerifiedInternal 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.
references/dispatcher.md
View on GitHub# Capstone dispatcher - one entry point, many protocols
Read by harnesses whose entry point is a single context file
(GEMINI.md imports this file). Claude-family harnesses route via the
individual wrapper skills instead; both paths land on the same
protocol files.
1. Read `core.md` (same directory) first: hard rules, voice, and
user config. Then `core-authoring.md`, unless the route below lands
on `start` or `feature`, which route rather than write.
2. Route on the first argument. Ten command words are the whole
surface: `map`, `edges`, `doctor`, `review`, `groom`, `plan`,
`implement`, `feature`, `start`, `help`. Every other protocol is a
stage one of them runs, reached as that command's second word.
The reserved subcommand words - the commands
`map`, `edges`, `doctor`, `review`,
`groom`, `plan`, `implement`, `feature`, `start`, under
`start` the stage words `mockup`,
`logic`, `uiux`, `architecture`, `standards`, `stack`, `build`,
and under `review` the word `retro` -
each route to `protocols/<name>.md`: execute that one protocol
exactly; behaviors live there, not here.
3. A subcommand word is reachable only after its command: `start
mockup` runs `protocols/mockup.md` and `review retro` runs
`protocols/retro.md`, while a bare `mockup` or `retro` is not a
command and routes to `start` like any other unrecognized argument.
`retro` is the one subcommand that is not a stage: it reads a
finished session rather than the code, and it sits under `review`
because a session ends under every command, not just the pipeline.
4. Exception: when invoked as `map`, topic names win over
stage words: `map architecture` regenerates
`01-architecture.md` and never starts the architecture interview.
`start architecture` is the interview.
5. `help`: run `../scripts/help.sh` via bash and output its stdout
verbatim; nothing else.
6. No argument at all → `protocols/start.md`, the bare-"capstone"
entry.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |