Skills catalog

Four commands open the doors. Private primitives do the steps underneath.

The commands

Architect, Builder, Craftsman. Four entrypoints. Pick the outcome you need.

Skill	What it does
`/architect-initial-foundation`	Start from a proved archetype, or document the code you already have. Run it again when the docs must match the code.
`/architect-requested-spec`	Turn a request into an approved draft. Build it later. A draft does not block a spec in progress.
`/build-requested-spec`	Turn a request, a draft, or a debt item into one spec, then implement, prove, and ship.
`/craft-lasting-quality`	Repair debt from urgent to small. Or ask it to upgrade the dependencies.

The steps those four commands use. Run one when you want a single step.

Skill	What it does
/outline-system	Map the system from the code: architecture, model, and schemas.
/rule-project	Write one project's rules and the commands it actually runs.
/define-spec	Turn one request into an approved spec, or a draft for later.
/implement-project	Write the code and the tests for one project. Check only what changed.
/verify-behavior	Acceptance is red or green. Green is the proof. Red goes back.
/review-implementation	What lint and tests cannot see. Findings become urgent debt and do not block the release.
/scan-quality	Refresh the debt list — structure first, then complexity and coverage.
/ship-spec	Prove the whole system, update the product record, and release.

You review at key moments. Everything else runs without asking — or skip stops with YOLO.|

Trigger	You check
During /architect-initial-foundation	The proposed system, when the repo has no application code yet
During /architect-requested-spec	The draft, before it waits for a later build
During /build-requested-spec	The spec and its requirements — unless you include YOLO
During /craft-lasting-quality	The urgent debt item, before it becomes a fix

Start, draft, and repair all meet at one build. You approve the spec, then the agents implement, verify, review, and ship.