speckit-plan

Automate speckit implementation planning from feature specs to design artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-plan executes the implementation planning workflow using the plan template to generate design artifacts, enabling teams to quickly move from spec to a concrete plan.

Core Features & Use Cases

  • Orchestrates the planning phases (Outline, Research, Design & Contracts) and outputs artifacts such as research.md, data-model.md, and contracts/.
  • Supports pre- and post-execution extension hooks, conditional handling, and command synthesis from hook names.
  • Updates agent context and ensures consistent planning references across the spec-kit workflow.

Quick Start

Run the speckit-plan workflow to produce a full implementation plan from the project 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 to generate design artifacts from a spec?

Automating implementation planning generates design artifacts by orchestrating multi-phase workflows including Outline, Research, and Design. It processes feature specs to produce structured artifacts like research.md, data-model.md, and quickstart.md from a plan template.

What is the best way to orchestrate a multi-phase planning workflow for software projects?

Orchestrating a multi-phase planning workflow involves sequencing phases like Outline, Research, and Design & Contracts. This approach enforces strict input handling, evaluates gates between phases, and processes extension hooks to ensure consistent planning references across the project.

Can I use custom extension hooks during the planning and design artifact generation process?

Custom extension hooks are supported during the planning process for both pre- and post-execution phases. The system enables conditional handling and command synthesis from hook names, allowing you to customize the workflow while generating path-resolved artifacts with absolute references.

Does spec-driven planning work without external dependencies or components?

Spec-driven planning works without external dependencies or components. The workflow operates independently using a plan template to automate the end-to-end implementation process, applying strict input handling and gate evaluation to produce design artifacts like contracts and data models.

Why use a structured plan template for feature-spec driven work instead of manual planning?

Using a structured plan template for feature-spec driven work ensures consistent artifact generation and updates agent context across the workflow. It moves teams quickly from spec to concrete plan by enforcing gate evaluation and producing path-resolved outputs like research.md and data-model.md.