Interactive spec-driven development workflow with phase-by-phase confirmation. Each phase waits for user confirmation before proceeding. Trigger phrases include "spec-flow", "spec mode", "need a...
Create a specification for non-trivial changes. Creates GitHub issue + spec file in a dedicated directory.
GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow. Triggers: "spec-kit", "speckit", "constitution", "specify", ".specify/", "θ§ζ Όι©±ε¨εΌε", "ιζ±θ§ζ Ό".
Create a build-ready spec + design doc pack (low-fi diagram, user flows/states, prototype brief, acceptance criteria) for a feature or UX change. Use for spec, design doc, feature spec, technical...
Spec creation with pattern references, acceptance criteria, and demo scripts. Use when creating implementation specs, defining acceptance criteria, or breaking down user stories.
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and...
Use when building anything non-trivial. Enforces a spec β plan β execute β verify loop that prevents "looks right" failures. Creates spec.md, todo.md, and decisions.md before writing code.
Manage protocol/standard specifications that define what a system must do. Use to create, import, or update the contract that TASKs implement against.
|
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
An "AI-Spec-Driven" workflow for complex tasks, triggered ONLY when explicitly requested. It aligns agent execution with rigorous planning (Spec -> Implementation -> Task Tracking) to mimic...
Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress...
Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress...
Validate spec completeness and implementation compliance. Use before approval (--pre) or before completion (--post).
High-level orchestrator for the spec-driven lifecycle. Use this when starting a new specification, planning, or implementation.
Create Technical Specifications (SPEC) - Layer 10 artifact using YAML format for implementation-ready specifications
Annotate a Spec/PRD with Feature IDs and generate a Coverage Index. Use when user wants to add spec tags to a vision document, create F-nnn identifiers, set up traceability, or initialize a PRD...
Generate complete specification documents from simple ideas. Use this Skill when the user wants to create a spec, needs a project specification, wants to document requirements, or asks to generate...
Plan-first development workflow with review gates. Use when implementing features, refactoring, or any task requiring structured planning, iterative implementation with reviews, and clean commits....
Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.