speckit-plan

Generates implementation plans and design artifacts from feature specifications using spec-kit templates.

Updated Jan 28, 2024
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/KrockSide --skill speckit-plan-thiago-cruz-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/Thiago-Cruz-eng/KrockSide/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/Thiago-Cruz-eng/KrockSide --skill speckit-plan-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires resolving technical unknowns, defining data models, and documenting contracts, which is time-consuming and error-prone when done manually. ## Core Features & Use Cases - Automated Planning Workflow: Runs the spec-kit setup script, loads the feature spec and project constitution, and fills the plan template with technical context. - Research and Design Artifacts: Generates research.md to resolve open questions, plus data-model.md, contracts/, and quickstart.md during the design phase. - Constitution Gate Checks: Evaluates the plan against the project's constitution and errors on unjustified violations. - Use Case: After writing a feature spec with spec-kit, invoke this Skill to produce a complete implementation plan with resolved technical decisions and interface contracts ready for task breakdown. ## Quick Start Ask the assistant to run the speckit plan workflow for the current feature branch to generate the implementation plan and design artifacts.

Frequently Asked Questions about speckit-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an implementation plan from a feature spec?▼

Run the speckit plan workflow, which executes the setup-plan PowerShell script, loads your feature spec and constitution, and fills the plan template. It produces research.md, data-model.md, contracts, and quickstart.md automatically.

What artifacts does the spec-kit planning phase produce?▼

The planning phase produces research.md resolving all open questions, data-model.md with entities and validation rules, a contracts directory for external interfaces, quickstart.md, and an updated agent context file.

Does speckit-plan require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory containing the memory constitution, PowerShell scripts, and a feature specification. Without this structure the setup step cannot locate the required files.

What happens when the plan violates the project constitution?▼

The workflow evaluates constitution gates during planning and again after design. It stops with an error if violations are found without documented justification, preventing non-compliant plans from proceeding.

How are extension hooks handled during planning?▼

If .specify/extensions.yml exists, hooks registered under before_plan and after_plan are checked. Mandatory hooks execute automatically, optional hooks are suggested, and hooks with conditions are skipped for the HookExecutor to evaluate.