speckit.plan

Generate design artifacts from a FEATURE_SPEC using a formal plan template.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates the implementation planning workflow by applying a plan template to generate design artifacts, reducing manual planning time and ensuring consistency across projects.

Core Features & Use Cases

  • Template-driven planning: Applies a predefined IMPL_PLAN template to produce artifacts such as research.md, data-model.md, contracts, and quickstart documentation.
  • Phase-driven workflow: Guides users through Phase 0 (Outline & Research) and Phase 1 (Design & Contracts) with explicit steps and gates.
  • Automatic context updates: Updates agent context and validates inputs from FEATURE_SPEC to ensure accurate planning outputs.

Quick Start

Run the setup-plan script from the repository root to initialize the speckit.plan workflow and generate planning artifacts from your feature specification.

Frequently Asked Questions about speckit.plan

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

FAQPage Schema
How do I generate design artifacts and contracts from a feature specification?▼

To generate design artifacts from a feature specification, apply a formal plan template to orchestrate Phase 0 and Phase 1 workflows, producing research.md, data-model.md, contracts, and quickstart.md outputs.

What is a phase-driven implementation planning workflow?▼

A phase-driven implementation planning workflow guides projects through Phase 0 for outline and research, then Phase 1 for design and contracts, using explicit steps and gates to ensure consistent design artifact generation.

How do I set up the repository environment for template-driven planning?▼

Template-driven planning requires a repository layout containing .specify scripts for setup and gates, where running the setup-plan script initializes the workflow and validates inputs from your FEATURE_SPEC.

Can I automate context updates during the design artifact generation process?▼

Yes, the planning workflow automatically updates agent context and validates inputs from the provided FEATURE_SPEC during artifact generation to ensure accurate planning outputs across phases.

What is the best way to structure feature research and data modeling before writing contracts?▼

The best way to structure feature research and data modeling is using a template-driven plan that separates Phase 0 research.md generation from Phase 1 data-model.md and contract creation, ensuring validated design outputs.

When should I not use a template-driven workflow for implementation planning?▼

You should avoid template-driven implementation planning if your repository lacks the required .specify scripts for setup and gates, or if your project does not follow a structured FEATURE_SPEC input format.