speckit-plan

Generate branch-ready implementation plans and design artifacts from specification templates.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/misadecastro/imperial-soccer --skill speckit-plan-misadecastro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/misadecastro/imperial-soccer/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/misadecastro/imperial-soccer --skill speckit-plan-misadecastro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the conversion of feature specifications and templates into a structured, branch-ready implementation plan so teams can move from requirements to design artifacts without manual orchestration.

Core Features & Use Cases

  • Automated Planning Workflow: Runs repository setup scripts, loads feature spec context, and fills an implementation plan template through multi-phase orchestration.
  • Research and Design Artifacts: Produces research.md to resolve unknowns, data-model.md, interface contracts, quickstart guides, and updates agent-specific context files.
  • Extension Hook Integration: Detects and surfaces pre- and post-plan extension hooks defined in .specify/extensions.yml to allow optional or mandatory automated steps.
  • Use Case: A developer or engineering manager uses this Skill to generate a reproducible implementation plan with gating checks, research tasks, and artifact outputs tied to a feature branch.

Quick Start

Run the speckit-plan workflow to produce research.md, data-model.md, contracts, and a branch-ready implementation plan from your project's FEATURE_SPEC and IMPL_PLAN.

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 specification?

To generate an implementation plan from a feature specification, run the speckit-plan workflow to orchestrate repository setup scripts, load feature spec context, and fill an implementation plan template with phased design artifacts.

What design artifacts are produced when creating an implementation plan from specs?

Creating an implementation plan from specs produces research.md to resolve unknowns, data-model.md, interface contracts, quickstart guides, and branch-ready implementation plans with updated agent-specific context files.

Do I need a specific project structure to automate implementation planning?

Yes, automated implementation planning requires a spec-kit project structure containing a .specify directory, access to .specify scripts for setup and agent context updates, and optional extension hooks in .specify/extensions.yml.

Can I run custom automated steps during the implementation planning workflow?

Yes, you can run custom automated steps during implementation planning by defining pre-plan and post-plan extension hooks in the .specify/extensions.yml file, which the workflow detects and surfaces as optional or mandatory steps.

How does multi-phase orchestration work for software design and data modeling?

Multi-phase orchestration for software design and data modeling works by running repository setup scripts, loading feature spec context, and sequentially filling an implementation plan template to generate research, contracts, and data models.

What is the best way to convert requirements into branch-ready implementation plans?

The best way to convert requirements into branch-ready implementation plans is using a spec-kit workflow that automates multi-phase orchestration to produce gating checks, research tasks, and design artifacts tied directly to a feature branch.