Loading...
Loading...
Found 16 Skills
Enforces strict Spec-Driven Development. Prevents direct coding and ensures spec → generate → review loops.
Gather external knowledge the spec needs and distill it into §R — the durable research log — so build grounds in facts instead of hallucinating library behavior. Each finding cites a source; unsourced claims are flagged, never written as fact. Triggers when a spec decision hinges on a library/API/best practice the agent is unsure of, when the user says "research this", "what's the best lib for…", "check current best practice", or invokes /ck:research. Defers the §R write to the spec skill.
Task Breakdown - generates an implementation plan with tracked tasks based on requirements and design documents. Use when breaking down a design into actionable work items.
Spec Status - displays pipeline progress dashboard for a single specification showing document statuses, blockers, and next action.