Loading...
Loading...
Found 54 Skills
Produces rigorous, unambiguous mathematical specifications using sets, functions, relations, invariants, and explicit edge-case handling. Use when requirements are ambiguous, systems have interacting constraints, or behavior/contracts must be precise and falsifiable.
Systematic three-phase approach to feature development using Requirements, Design, and Tasks phases. Transforms vague feature ideas into well-defined, implementable solutions that reduce ambiguity, improve quality, and enable effective AI collaboration.
Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Enforces strict Spec-Driven Development. Prevents direct coding and ensures spec → generate → review loops.
Specification-driven development with structured phases: Initialize, Plan, Tasks, Implement+Validate. Creates structured feature specs with traceability to requirements. Use when: starting projects, planning features, implementing with verification, or tracking decisions across sessions. Also use when the user wants to break a feature into tasks, plan before coding, track implementation progress, set up a new project structure, or organize work into specs and plans. Triggers on "map codebase", "initialize", "initialize project", "create feature", "plan", "tasks", "implement", "validate", "archive", "break this into tasks", "plan this feature", "start a new project".
Keeps implementation and specs in sync. Use when working on a feature that has a spec in .claude/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes.
Cancel and permanently delete an in-progress spec-driven change. Warns before deleting. Use this to abandon a change that will not be implemented.
Propose a new spec-driven change. Scaffolds proposal.md, design.md, tasks.md, and questions.md for a named change, populated with project context.
Archive a completed spec-driven change. Warns on incomplete tasks, moves change to archive/ with a date prefix.
Review the code quality of a spec-driven change. Checks readability, security, performance, and best practices before archiving.
Initialize a .spec-driven/ directory in a project. Creates config.yaml and specs/ scaffold, then guides the user to fill in project context.
Run the full spec-driven workflow automatically. Proposes, implements, verifies, reviews, and archives a change with one confirmation checkpoint.