A repo that already has code
/capstone:map
Eight chapters, every claim cited file:line. Re-runs rewrite only what drifted.
Architecture docs for your coding agent
Your agent, on rails.
Every rule decided before a line is written. Every doc read before a token is spent.
$npx skills add GentBajko/capstone
Take all skills — core carries the shared rules every command reads. Update with npx skills update.
$/plugin marketplace add GentBajko/capstone
$/plugin install capstone@capstone-marketplace
/capstone:help is answered by a hook before the model is invoked, so usage costs zero tokens.
$gh skill install GentBajko/capstone --all --agent github-copilot
Copilot's own marketplace format works too. Update with gh skill update capstone.
$gemini extensions install https://github.com/GentBajko/capstone
One context file, so a dispatcher routes the first argument to the same protocols.
$agy plugin install https://github.com/GentBajko/capstone
Commands come out namespaced: /capstone:map.
opencode.json
{ "plugin": ["capstone@git+https://github.com/GentBajko/capstone.git"] }
Every script is bash, so Windows needs Git Bash.
It reads before it acts.
Every file records the commit it came from and the globs it covers. A refresh diffs those and rewrites only what moved.
Facts, not advice.
Chapters state what the code does, with file:line pointers. Opinion lives in one command, review, and only when you ask.
You approve before it writes.
Every stage gates on you. It pushes back at most twice, with a citation. Then your answer stands.
Three entry points
1
Screens, journeys, what still has to be decided
mockup/
2
Exact rules, branches, unhappy paths
logic/
3
How it looks and how it behaves
uiux/
4
Layers, models, data flow
01 – 08
5
How code must be written here
standards.md
6
Real options, licences, prices; you pick
05-dependencies.md
7
Plan, your approval, then code
source
Between 6 and 7 a reconciles all six outputs. No stage can be skipped, and a bare resumes at the first unfinished one.
No index on disk → full build. Index there → refresh what drifted.Index, 8 chapters, logic/, uiux/
One chapterThat file
Full rewrite, forcedEverything
Read-only trust report, verdict line for CINothing
Repair the docs area itselfOnly what you approve
The one command allowed opinionsreview.md, gitignored
One verb, because the branch is readable off disk. Chapters written by flip from intent to observation once the code exists.
Interviewed against the docs, so every requirement traces to a recorded decision.
spec.md
spec gate
Task-by-task TDD. Edit the spec afterwards and the approval is void.
plan.md
plan gate
One commit per task, then reviews its own diff until two rounds find nothing new.
source · changelog entry
When implement finishes it absorbs the behaviour back into the docs and deletes the feature folder — which is why the ledger is always committed.
A product that doesn't exist yet
/capstone:start
Seven interviews, mockup through build. Every answer hits disk before the next question.
One change to a mapped project
/capstone:feature
Spec, TDD plan, code. Two approval gates. Absorbed back into the docs.
How it decides what gets built
The same ladder runs in every stage that decides something will exist, not just the ones that write code.
TDD + YAGNI — stop at the first rung that holds
1Does this need to exist at all?Speculative need is skipped, in one line.
2Is it already in this codebase?Reuse the helper, type or pattern that already lives here.
3Does the standard library do it?Then use it.
4Does the platform cover it?CSS over JS. A database constraint over application code.
5Does a dependency you already have?Never add one for what a few lines can do.
6Can it be one line?Then it is one line.
7Only then: the minimum code that works.Written test-first — failing test, minimum code to green, commit.
The docs are the source of truth.
Once a stage formalizes, its output file is what every later command reads — and done is marked only after those files are on disk, so a crash can never strand a marker over missing files. Interviews stay as resume state and are never cited.
Your decisions outrank the ladder.
standards.md wins, but only by a rule that names what it overrides. A silent conflict resolves to the ladder, and the ladder is never a veto: two rounds of pushback, then it builds what you asked for.
Never lazy about.
Understanding the problem first. Validation at trust boundaries. Error handling that prevents data loss. Security, accessibility, typing. A branch, a parser or a money path always leaves its failing-then-green test behind; a one-liner gets none.
Proof of work
One day. One shot.
Slopify researches a topic, writes the article, narrates it, generates the imagery and cuts an mp4. Capstone interviewed the design out on 2 September. Claude Code wrote the whole thing the next day, in one shot — first commit 00:03, last 22:26.
Beside this is its real docs/capstone/, file for file. Open anything to see what capstone stamped on it.
50doc files · 372 KB
204source files
134test files
49,266lines written
slopify · docs/capstone/
This explorer needs JavaScript. The same tree is in the repository under docs/capstone/.
expertise
Not technical? Still yours.
Set expertise: 1 and it asks how many people might use the thing rather than what your p99 budget is, then derives the targets itself. The docs stay rigorous either way.
ci
Stale docs fail the PR.
One workflow file, one secret. map check runs on every pull request and CI greps the verdict:
MAP CHECK: current
MAP CHECK: stale (3 findings)
MAP CHECK: stale (3 findings)
Free, and it stays free.
Built and maintained by Gent Bajko. Nothing is gated and there is no paid tier waiting behind the next release. If it saves you an afternoon, this is how it gets more of them.