Loading...
Loading...
Found 97 Skills
Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.
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. Triggers on "map codebase", "initialize", "initialize project", "create feature", "plan", "tasks", "implement", "validate", "archive".
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.
Run the full spec-driven workflow automatically. Proposes, implements, verifies, reviews, and archives a change with one confirmation checkpoint.
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.
Implement the tasks in a spec-driven change. Works through incomplete tasks one by one, marking each complete as it goes.
Create or restructure a persistent milestone-based roadmap under .spec-driven/roadmap/.
Use when implementing features from a spec or requirements document, doing multi-phase work, or when you need structured Analyze-Plan-Ask-Execute-Review cycles to prevent ad-hoc coding and ensure spec-aligned, pattern-consistent implementations
Route spec content into the correct delta spec file. Reads .spec-driven/specs/INDEX.md first, then decides whether to update an existing spec file, create a new spec file, create a new category, modify requirements, or remove specific requirements.
Archive a completed spec-driven change. Requires completed tasks, merges delta specs into main specs, then moves the change to archive/ with a date prefix.
Spec-driven development framework for ecommerce features. Orchestrates from intent to implementation via structured specs and task breakdown. Triggers on "/spec.plan", "/spec.refine", "/spec.clarify", "/spec.tasks", "/spec.run", "I want to build", "I want to add", "create spec", "feature spec", "new feature", "implement feature".
Retrofit or repair spec frontmatter mappings between specs, implementation files, and test files.