speckit-plan

Generate design artifacts from a plan template for spec-kit projects.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/fly-eng/yzh --skill speckit-plan-fly-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/fly-eng/yzh/tree/main/.kimi/skills/speckit-plan
Command: npx skills add https://github.com/fly-eng/yzh --skill speckit-plan-fly-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the implementation planning workflow by orchestrating a plan template to produce design artifacts for software projects, reducing manual coordination and boosting consistency.

Core Features & Use Cases

  • Automated planning: executes a structured outline from the plan template.
  • Context loading and constitution checks: ensures requirements and constraints are considered early.
  • Multi-phase output: generates artifacts like research.md, data-model.md, contracts, and quickstart guides, then updates agent context.

Quick Start

Run the speckit-plan workflow from the repository root to generate the full set of design artifacts and plan output.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
What is automated design artifact generation for software projects?

Automated design artifact generation orchestrates a plan template to produce structured outputs like research.md, data-model.md, and contracts. It reduces manual coordination by loading project context and executing a multi-phase planning process automatically.

Do I need a .specify/ directory to run the speckit-plan workflow?

Yes, the speckit-plan workflow requires a .specify/ directory in your repository root. It loads the FEATURE_SPEC and .specify/memory/constitution.md files to guide the planning process and ensure project constraints are considered early.

How do I generate research.md and data-model.md from a plan template?

Run the workflow from the repository root to generate design artifacts from a plan template. It executes a structured multi-phase outline that automatically produces research.md, data-model.md, contracts, and quickstart guides.

Can I add custom extension hooks before or after the planning phases?

Yes, the workflow supports extension hooks executed before and after planning. This allows you to customize the automated workflow by injecting specific logic or checks at the start and end of the design artifact generation process.

What's the best way to maintain consistency across implementation planning workflows?

Using an automated planning workflow that applies a structured plan template ensures consistency across projects. By loading a constitution.md file for checks, it enforces requirements and constraints early, reducing manual coordination errors.