speckit-plan

Generate implementation plans with research, data model, contracts, and quickstart documentation.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/chuanyue98/prompt-gallery --skill speckit-plan-chuanyue98
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/chuanyue98/prompt-gallery/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/chuanyue98/prompt-gallery --skill speckit-plan-chuanyue98

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an existing spec-kit project into a structured implementation plan, reducing ambiguity and aligning engineering work with the required constitution checks and artifacts.

Core Features & Use Cases

  • Phase-based planning: Produces research output first, then designs and contract artifacts in later phases.
  • Unknown clarification workflow: Converts NEEDS CLARIFICATION items into research tasks and ensures they are resolved before proceeding.
  • Design artifacts generation: Creates data-model.md, contracts (when applicable), and quickstart.md, then updates agent context references.
  • Guardrails and re-checks: Runs constitution checks and fails on gate violations or unresolved clarifications to keep the plan consistent.
  • Extension hook support: Executes optional or mandatory before_plan/after_plan hooks when configured via .specify/extensions.yml.

Quick Start

Run the speckit-plan workflow from your spec-kit project root so it generates research.md, data-model.md, any needed contracts, quickstart.md, and updates the agent context.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
How do I generate implementation plans and contracts for a spec-kit project?

To generate implementation plans and contracts for a spec-kit project, run the planning workflow from your project root to resolve technical unknowns, produce design artifacts like data-model.md, and enforce constitution checks.

How does the spec-kit planning workflow handle NEEDS CLARIFICATION items?

The spec-kit planning workflow converts NEEDS CLARIFICATION items into research tasks, ensuring they are fully resolved before proceeding and enforcing gate failures to maintain plan consistency.

What design artifacts are created when planning a spec-kit feature specification?

Planning a spec-kit feature specification creates research.md, data-model.md, applicable contracts, and quickstart.md, while automatically updating agent context references like AGENTS.md markers.

Can I run before_plan and after_plan extension hooks during the planning phase?

Yes, you can run optional or mandatory before_plan and after_plan extension hooks during the planning phase by configuring them via the .specify/extensions.yml file in your project.

What happens if constitution checks fail or clarifications are unresolved in spec-kit planning?

If constitution checks fail or clarifications remain unresolved during spec-kit planning, the workflow enforces gate failures to halt progress and prevent inconsistent design artifacts from being generated.

Do I need a spec-kit project root to generate data models and quickstart documentation?

Yes, you need an existing spec-kit project root because the workflow loads constitution files and templates, executes phase outputs, and updates agent context references within that directory structure.