Skills catalog
Public orchestrators
Architect, Builder, Craftsman — three entrypoints. Pick the outcome you need.| Skill | What it does |
|---|---|
/architect-system-foundation | Propose a new system and scaffold it after you approve — or document what already exists. Rerun to keep docs in sync. |
/build-requested-spec | Turn a natural-language request into one spec that owns its requirements, then implement, prove, and ship. |
/craft-lasting-quality | Review quality, record technical debt, and repair one coherent slice through the same delivery flow. |
The private primitives
The steps those three 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 the records a delivery needs. |
| /rule-project | Extract each project's rules and the commands it actually runs. |
| /define-spec | Write one spec that owns its requirements, then pause for your approval. |
| /implement-project | Write the code and tests for one project, and check this spec's acceptance along the way. |
| /verify-behavior | The acceptance evidence. Green ships; red goes back for repair. |
| /review-implementation | An expert look at what linters miss. Findings become debt and do not block the release. |
| /scan-quality | A system-wide quality pass that refreshes the debt list. |
| /ship-spec | Version the product, update the changelog, and merge. |
Human checkpoints
You review at key moments. Everything else runs without asking — or skip stops with YOLO.|| Trigger | You check |
|---|---|
| During /architect-system-foundation | The proposed system, when the repo has no application source yet |
| During /build-requested-spec | The spec and its requirements — unless you include YOLO |
| During /craft-lasting-quality | Which coherent group of debt becomes the next repair, if any |
flowchart LR A[architect-system-foundation] --> B[build-requested-spec] Q[craft-lasting-quality] --> B B -->|you ✔️ spec| S[implement → verify → review → ship]