Verified:GitHub

speckit-plan

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

Updated Dec 12, 2024

Search Tags:#implementation planning #workflow automation #feature specification #data model #spec-kit #contracts #design artifacts

Ready to run

npx skills add https://github.com/kipariss1/czech_out_auto_bot --skill speckit-plan-kipariss1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/kipariss1/czech_out_auto_bot/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/kipariss1/czech_out_auto_bot --skill speckit-plan-kipariss1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires resolving technical unknowns, designing data models, and defining contracts, which is slow and inconsistent when done manually. ## Core Features & Use Cases - Automated Planning Workflow: Runs the spec-kit plan workflow to fill Technical Context, evaluate constitution gates, and mark unknowns as NEEDS CLARIFICATION. - Design Artifact Generation: Produces research.md, data-model.md, contracts/, and quickstart.md from the feature spec. - Extension Hook Support: Executes optional and mandatory before/after plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec in a spec-kit project, invoke this Skill to resolve open questions, design the data model, and generate a quickstart validation guide before implementation begins. ## 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 in a spec-kit project. It executes setup-plan.sh, loads the feature spec and constitution, fills the plan template, and produces research.md, data-model.md, contracts, and quickstart.md.

What artifacts does the spec-kit plan workflow produce?▼

The workflow produces research.md resolving all NEEDS CLARIFICATION items, data-model.md with entities and validation rules, a contracts/ directory for external interfaces, and quickstart.md with runnable validation scenarios.

Does speckit-plan require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory containing scripts/bash/setup-plan.sh, memory/constitution.md, and the plan template. Without this structure the setup step cannot run.

What are extension hooks in the spec-kit plan workflow?▼

Extension hooks are commands registered in .specify/extensions.yml under hooks.before_plan or hooks.after_plan. Mandatory hooks are executed automatically, while optional hooks are only suggested to the user.

What happens when the plan has unresolved clarifications?▼

Unknowns in the Technical Context are marked as NEEDS CLARIFICATION and converted into research tasks during Phase 0. The workflow errors on unresolved clarifications or constitution gate failures.