Skills

Core skills

The baseline ships 36 skills across nine categories. Each runs in main context, where conversational visibility is preserved. The single subagent is a separate mechanism.

§ I

Artifact drafting (4)

Each ships a template.md that the skill fills in. Artifact skills produce the durable workflow documents that downstream phases consume.

intake. Phase 1. Captures a new request: problem, desired outcome, constraints, testable acceptance criteria.
brd. Cross-functional Business Requirements Document, written when intake is not enough.
spec. Phase 4. Diagram-driven technical spec with C4, UML, and a dependency graph in PlantUML.
rca. Out-of-band postmortem for incidents and outages. Often precedes a bugfix intake.

§ II

Workflow phases (10)

Auto-invocable. The orchestrator chains them in order, yielding at consent gates.

triage. Picks the workflow entry phase and writes workflow.json.
scout. Phase 2. Maps the relevant slice of the codebase.
research. Phase 3. Surfaces 2 to 4 candidate solution approaches with concrete tradeoffs.
tdd. Phase 6 (solo). Decides scenario recipe and implementation contract; runs scenario then implement then verify then drift-check. Drift-check compares numbered ACs and Design calls rows in the approved spec against the implementation diff and yields the workflow if any item is unresolved (no auto-loop).
simplify. Phase 7. Mechanical cleanup pass over the branch diff.
security. Phase 8. OWASP-aligned review of pending changes.
integrate. Phase 9. Runs the full test suite and stamps the binding verify verdict.
document. Phase 10. Routes technical writing through the documentation, technical-tutorials, and prose skills.
archive. Phase 10.5. Moves slug artifacts to docs/archive/<date>/<slug>/.
changelog. Phase 11.5. The ship-pair sub-step between /grant-commit and /commit. Reads the staged commit history; classifies each commit into a keepachangelog 1.0.0 section (Added, Changed, Fixed, and so on); appends entries under ## [Unreleased] in CHANGELOG.md. The same commit_consent token authorizes both this step and /commit; no new gate. Supports --preview-only for ad-hoc projected-version lookups outside a workflow.
commit. Phase 11. Stages and creates the commit, gated by /grant-commit. After the commit lands, if workflow.json declares source_backlog_keys, the commit step invokes sweep.py stamp-closure to mark each named backlog entry status: picked-up with superseded-at: <today>; the next /memory-flush auto-close sweep deletes the stamped blocks. Pushes to protected branches need /grant-push (Article VII).

§ III

Phase workers (5)

Execute pre-decided recipes. Each mandatorily invokes a sub-skill so the engineering rules travel with every code-generation step.

scenario. Writes failing tests from a recipe. Invokes code-structure.
implement. Writes production code that turns scenarios green. Invokes code-structure; uses context7 for any third-party API.
verify. Mechanical worker. Runs the test command and stamps the official PASS or FAIL verdict.
prose. Drafts or revises English prose for any brief. Always invokes humanizer; conditionally copywriting, documentation, or technical-tutorials.
design-ui. Orchestrates impeccable for UI design tasks: classifies intent, picks an impeccable recipe, runs it under a 3-iteration loop cap, persists state at .claude/state/design/<slug>.json. Writes no product code itself. Per Article X.2, every design task in a workflow phase routes through this skill.

§ IV

Spec helpers (4)

Validate the spec artifact before approval and render its diagrams for review.

spec-lint. Preflight check before save. Validates PlantUML syntax, required diagram presence, AC-to-sequence traceability.
spec-render. User-only. Renders PlantUML diagrams to PNG.
spec-diagram-review. Cross-consistency review. Verifies C4 components appear in the dependency graph and so on.
spec-traceability-review. Verifies every spec AC traces to an upstream AC in the intake or BRD.

§ V

Orchestration (3)

Drive the workflow end-to-end, plan the swarm path, and dispatch the worker waves.

harness. User-only. Drives the workflow end-to-end, yielding at consent gates.
swarm-plan. Decomposes an approved spec into a dependency-ordered swarm plan.
swarm-dispatch. Executes a swarm plan wave by wave with worktree isolation.

§ VI

Memory (1)

One curation skill bridges the auto-extracted inbox and the canonical files.

memory-flush. Reviews auto-extracted candidates in _pending.md and commits keepers to canonical files.

§ VII

Shared globals (7)

Vendored or globally available. Available to any phase that needs them.

claude-automation-recommender. Vendored under Apache 2.0. Recommends Claude Code automations for a codebase.
code-structure. Mandatory on every code-generation step. Enforces orchestration / domain / foundation layering.
humanizer. Removes signs of AI-generated writing. Mandatorily invoked by prose.
documentation. Reference docs, READMEs, runbooks.
technical-tutorials. Step-by-step tutorials, quickstarts, code walkthroughs.
copywriting. Persuasive register: landing pages, marketing copy.
impeccable. Frontend design and iteration. Mandatorily invoked by design-ui.

§ VIII

Audit (1)

One drift defender keeps the implementation honest against seed.md and the constitution.

audit-baseline. Drift check between this constitution plus seed.md and the implementation. Read-only.

§ IX

Alternate tracks (1)

A stripped-down pipeline for tasks that need no failing-test-driven code change.

chore. Stripped-down workflow for tasks with no failing-test-driven code change: documentation edits, governance count bumps, formatting, dependency bumps. Skips scenario and implement; runs edits directly. Verify, archive, grant-commit, and commit remain mandatory.