router
Classify intent, select the right module. Does not do the work itself.
The problem
Agents fail in predictable ways
They edit before understanding the repo
They treat a plan as proof
They debug by guessing
They review while changing files
They ship without evidence
Keystone makes each of these structurally impossible.
How it works
A building with one front door and many private rooms
You invoke /keystone with whatever you need. Keystone classifies the work, routes to exactly one module, applies that module's contract, loads gates only when needed, and hands off cleanly when the task changes shape.
Receive
User sends a request
Route
Router selects one primary module
Contract
Module controls what's allowed
Gate
Evidence before transitions
Result
Report or hand off
Modules
Nine rooms, each with a clear job
Each module has an intent, allowed mutations, hard boundaries, and an exit gate. Internal modules stay internal — you use one public skill.
research
Inspect, summarize, gather evidence, compare options. Never edits or presents guesses as facts.
shape
Draft prose, shape product direction, UX, visual direction, and scope. Does not implement.
breakdown
Convert approved direction into ordered, verifiable tasks. Not named plan — intentionally.
build
Mutate scoped files. Must pass isolation before the first edit.
debug
Reproduce and isolate a bug from evidence. Does not guess fixes.
review
Critique work without changing it. Read-only: no fixes, no commits, no shipping.
ship
Finalize completed work. Only runs after proof and review are satisfied.
health
Scan repo, tooling, and package health. Does not silently fix issues.
Common workflows
The routes agents actually travel
Feature work
research
shape
breakdown
build
review
ship
Existing plan
breakdown
build
review
ship
Bug fix
debug
build
proof
review
ship
Health finding
health
build
or
review
Gates
Deliberately boring checkpoints
Their job is to stop common mistakes, not to be clever.
Checkpoint
Make the next module or prompt explicit before stopping
Isolation
Confirm branch, worktree, and scope before the first mutation
Red
Establish a failing check or reproduction when practical
Proof
Verify claims with evidence before success reports
Review
Confirm required review has no blockers
Ship
Confirm verified, reviewed work is ready for handoff
Get started
Add Keystone to your agent
skills.sh / Agent Skills
npx skills add static-var/keystone --skill keystonePi
pi install npm:@static-var/keystoneClaude Code
/plugin marketplace add static-var/Keystone
/plugin install keystone@keystoneCodex
codex plugin marketplace add static-var/Keystone --ref main
codex plugin add keystone --marketplace keystoneThen invoke:
/keystone your task here
Claude Code: /keystone:keystone your task here
Keystone is not trying to make agents more autonomous by removing structure. It makes agents safer by giving each phase a name, a boundary, and a proof requirement.