speckit-plan

Execute implementation planning workflows from feature specifications into design artifacts.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-plan-d0whc3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.trae/skills/speckit-plan
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-plan-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash.

What problem does it solve?

This Skill helps teams convert an existing feature specification into an implementation plan and supporting design artifacts, reducing ambiguity and rework during planning.

Core Features & Use Cases

  • Executes the planning workflow end-to-end: sets up the plan environment, loads the feature spec and constitution, and follows the provided IMPL_PLAN template structure.
  • Resolves uncertainties systematically: extracts NEEDS CLARIFICATION items and drives research until all clarifications are resolved in generated outputs.
  • Produces design artifacts and contracts: generates research.md, data-model.md, contracts (when applicable), and quickstart.md, then updates agent context for the project’s plan.
  • Supports extensibility via hooks: runs pre-plan and post-plan extension hooks defined in .specify/extensions.yml when present.
  • Guardrails for correctness: marks unknowns as NEEDS CLARIFICATION, errors on gate failures, and verifies constitution compliance after design generation.

Quick Start

Run the speckit-plan skill from your repo root with your plan arguments so it generates research.md, data-model.md, contracts/, quickstart.md, and any agent context updates.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
How do I turn a feature specification into an implementation plan?

To turn a feature specification into an implementation plan, you run an end-to-end workflow that loads your spec, resolves unknowns through research, and generates design artifacts like research.md and data-model.md.

What is the best way to resolve unknowns and dependencies during planning?

The best way to resolve unknowns and dependencies during planning is to extract NEEDS CLARIFICATION items from the feature spec and systematically drive research until all technical context gaps are resolved.

How does spec-kit handle constitution compliance checks after design generation?

Spec-kit handles constitution compliance by verifying your generated design artifacts against constitution.md, explicitly erroring on gate failures and marking unresolved technical context as NEEDS CLARIFICATION.

How do I run pre-plan and post-plan hooks in a specification workflow?

To run pre-plan and post-plan hooks in a specification workflow, execute the setup script and process extension hooks defined in .specify/extensions.yml with enabled filtering and non-evaluated hook conditions.

Do I need bash to generate research and design artifacts from my feature spec?

Yes, you need bash to execute the setup-plan.sh and update-agent-context.sh scripts required to generate research.md, data-model.md, contracts/, and quickstart.md artifacts from your feature spec.

What design artifacts are generated when converting specs to implementation-ready plans?

When converting specs to implementation-ready plans, the workflow generates research.md, data-model.md, contracts when applicable, quickstart.md, and updates the project's agent context.