Skills catalog
Context
| Skill | What it does |
|---|---|
| /explore | Agent setup, system architecture, conceptual model, and PRD shell from the repo tree and guides. |
| /extract | Per-container architecture, schemas, and coding rules from source. |
| /scaffoldify | Materialize a confirmed, installable solution scaffold. |
Capture
| Skill | What it does |
|---|---|
| /specify | Write a functional or technical specification — kind named by the caller. |
| /scope-change | Discover affected specs and write a coordinated change manifest. |
Build
Prove
Ship
| Skill | What it does |
|---|---|
| /shipify | Version, changelog, reconciled docs, and tag after qualification. |
Meta
| Skill | What it does |
|---|---|
| /skillify | Create or update skills under .agents/skills/. |
Public orchestrators
Architect, Builder, Craftsman — three entrypoints that own outcomes and compose the delivery loop.| Orchestrator | What it does |
|---|---|
/architect-solution-foundation | Architect: map a brownfield solution or design a greenfield one, with optional scaffolding. |
/build-requested-change | Builder: turn a requirement into one or more specs, then implement, verify, qualify, and ship. |
/craft-lasting-quality | Craftsman: consolidate durable findings and ship behavior-preserving remediation. |
Human checkpoints
You review at key moments. Everything else runs without asking — or skip stops with YOLO.|| Trigger | You check |
|---|---|
| During /architect-solution-foundation | Brownfield or greenfield route when the choice is unclear |
| During /build-requested-change | Problem, outcomes, and acceptance criteria for each spec |
| During /craft-lasting-quality | Evidence-backed remediation scope before fixes run |
flowchart LR A[architect-solution-foundation] --> B[build-requested-change] B -->|you ✔️| S[verify → qualify → ship] C[craft-lasting-quality] -->|you ✔️| S