speckit-plan

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

1|Updated Apr 17, 2026

Search Tags:#workflow #planning #research #spec-kit #contracts #artifact-generation

Ready to run

npx skills add https://github.com/anishakode/Boring_AI --skill speckit-plan-anishakode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/anishakode/Boring_AI/tree/main/.cursor/skills/speckit-plan
Command: npx skills add https://github.com/anishakode/Boring_AI --skill speckit-plan-anishakode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the implementation planning workflow within a spec-kit project, generating design artifacts from a plan template and guiding multi-phase execution.

Core Features & Use Cases

Orchestrates plan-driven workflows to produce research.md, data-model.md, contracts/, and quickstart.md from a single plan template.
Enforces pre- and post-execution checks, handles extension hooks, and validates gates to ensure design constraints are met.
Useful for teams building spec-driven tooling that require repeatable, auditable planning cycles with clear artifact outputs.

Quick Start

Invoke speckit-plan to drive the implementation planning workflow from a plan template and generate the initial design artifacts.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema

How do I automate spec-kit planning and artifact generation from a plan template?▼

Automating spec-kit planning requires orchestrating a workflow that reads a plan template and generates design artifacts. This process automatically produces research.md, data-model.md, contracts, and quickstart.md while enforcing pre- and post-execution hook checks.

What is a spec-kit planning workflow and when do I need automated artifact output?▼

A spec-kit planning workflow is a structured, multi-phase process for generating design artifacts within a .specify directory. You need it when building spec-driven tooling that requires repeatable, auditable planning cycles with clear artifact outputs and gate validation.

Can I use this planning orchestration if my project does not follow a .specify directory structure?▼

You cannot use this orchestration without the .specify directory structure. The workflow explicitly applies to spec-kit projects that follow this directory layout to manage automated planning, agent-context updates, and structured outputs across multiple execution phases.

How do I enforce pre-execution checks and gate evaluation during implementation planning?▼

Enforcing pre-execution checks and gate evaluation is handled automatically by the orchestration workflow. It validates gates to ensure design constraints are met, handles unknowns, performs constitution checks, and processes extension hooks before generating final artifacts.

Does spec-kit plan handle constitution checks and unknowns during multi-phase execution?▼

Yes, handling unknowns and performing constitution checks are built-in features of the multi-phase execution workflow. These structural validations run alongside gate evaluations to ensure all design constraints are met before producing the final structured outputs.