speckit-plan

Generate technical implementation plans from feature specifications in spec-kit projects.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill speckit-plan-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/speckit-plan
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill speckit-plan-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete technical plan requires deciding architecture, tech stack, data models, and contracts, which is time-consuming and error-prone when done ad hoc. This Skill automates that transition inside spec-kit projects, producing a structured plan.md plus research, data model, and contract artifacts. ## Core Features & Use Cases - Automated Plan Generation: Runs the spec-kit setup script, loads the feature spec and project constitution, and fills the implementation plan template with technical context and constitution checks. - Research & Design Phases: Phase 0 resolves all NEEDS CLARIFICATION items into research.md; Phase 1 produces data-model.md, contracts/, quickstart.md, and updates the agent context file. - Gate Enforcement: Evaluates constitution gates and stops with an error on unjustified violations or unresolved clarifications. - Use Case: After writing a feature spec with spec-kit, invoke this Skill to generate the full technical design package—research decisions, entity models, API contracts, and a quickstart guide—before any code is written. ## Quick Start Generate an implementation plan from my current feature specification using the speckit plan workflow.

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 after creating a feature specification. It executes .specify/scripts/bash/setup-plan.sh, loads the spec and constitution, then fills the plan template with technical context, research, data models, and contracts.

What artifacts does the spec-kit plan phase produce?

The plan phase produces plan.md as the main output, plus research.md resolving 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 work without a .specify directory?

No, it requires a spec-kit project structure with a .specify/ directory containing the setup and agent context scripts, plus a memory/constitution.md file. Without these, the setup step cannot locate the feature spec or plan paths.

What happens when the constitution check fails during planning?

The workflow evaluates constitution gates before and after design. If violations are found and not justified in the plan, it stops with an ERROR rather than proceeding to later phases.

When should I skip contract generation in a technical plan?

Skip the contracts/ output when the project is purely internal, such as build scripts or one-off tools with no external interfaces. Contracts are meant for public APIs, CLI schemas, web endpoints, grammars, or UI contracts.