Loading...
Loading...
Found 97 Skills
Cancel and permanently delete an in-progress spec-driven change. Warns before deleting. Use this to abandon a change that will not be implemented.
Retrofit or repair spec frontmatter mappings between specs, implementation files, and test files.
Spec-Driven Development (SDD) methodology based on GitHub's SpecKit. Use for structured AI-assisted development with constitutional governance, phased workflows, and multi-agent coordination. Implements 7-phase process from constitution to implementation.
Propose a new spec-driven change. Scaffolds proposal.md, design.md, tasks.md, and questions.md for a named change, populated with project context.
Review the code quality of a spec-driven change. Checks readability, security, performance, and best practices before archiving.
Verify a spec-driven change is complete and correctly implemented. Checks task completion, implementation evidence, and spec alignment.
Spec-driven development pipeline with 6 phases: Explore, Requirements, Design, Task Plan, Implementation, Review. Enforces human approval gates between phases. Use when user wants structured feature development, spec-first approach, or says "I want to add feature X", "new feature", "implement", "build". Keywords: spec, requirements, design document, TDD plan, task plan, implementation, code review, pipeline, approval gates, WHEN/SHALL.
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".
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".
Archive a completed spec-driven change. Warns on incomplete tasks, moves change to archive/ with a date prefix.
Enforces strict Spec-Driven Development. Prevents direct coding and ensures spec → generate → review loops.
Execute a lightweight ad-hoc task (debugging, documentation, small adjustments) without the full change lifecycle. Assesses spec impact afterward.