speckit-plan

Generate implementation artifacts from a formal plan template.

3|Updated Mar 24, 2026

Search Tags:#workflow #planning #spec-kit #artifact-generation #planning-automation #extension-hooks

Ready to run

npx skills add https://github.com/ldilov/harness-forge --skill speckit-plan-ldilov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/ldilov/harness-forge --skill speckit-plan-ldilov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-plan automates the implementation planning workflow by turning a plan template into design artifacts and governance artifacts for software projects.

Core Features & Use Cases

Generates an implementation plan from a plan/template, including phases and artifacts such as research.md, data-model.md, contracts/, quickstart.md.
Handles pre/post-execution extension hooks via .specify/extensions.yml, supporting mandatory and optional hooks with clear execution prompts.
Integrates with constitution checks and agent context updates during the planning phases to ensure alignment with project constraints.

Quick Start

Run the speckit-plan to generate the initial implementation artifacts from the plan template.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema

How do I automate implementation planning from a plan template?▼

Automating implementation planning uses a formal plan template to generate design artifacts like research.md, data-model.md, and contracts/. This enables deterministic project bootstrapping by executing structured gates and producing phase-driven outputs automatically.

What is a .specify/ workflow for artifact generation?▼

A .specify/ workflow organizes projects using extension hooks and phase-driven artifact generation. It loads IMPL_PLAN templates, executes structured governance gates, and produces artifacts such as research.md, data-model.md, contracts/, and quickstart.md.

How do I execute pre and post extension hooks during planning automation?▼

Extension hooks execute during planning automation via .specify/extensions.yml, supporting mandatory and optional hooks with clear execution prompts. This integrates constitution checks and agent context updates to ensure alignment with project constraints.

Do I need a specific project structure for phase-driven artifact generation?▼

Phase-driven artifact generation requires projects organized with a .specify/ workflow, extension hooks, and formal IMPL_PLAN templates. This structure enables deterministic governance gates and ensures the proper generation of design artifacts.

What artifacts are generated from an implementation plan template?▼

Implementation plan templates generate artifacts including research.md, data-model.md, contracts/, and quickstart.md. These outputs are produced through structured gates and phase-driven execution, enabling deterministic project bootstrapping and governance.

Can I integrate constitution checks into my implementation planning workflow?▼

Constitution checks integrate into implementation planning during phase execution to ensure alignment with project constraints. The workflow updates agent context and executes governance gates alongside mandatory and optional extension hooks.