speckit-plan

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

10|3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/raphaelfh/newsweep --skill speckit-plan-raphaelfh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/raphaelfh/newsweep/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/raphaelfh/newsweep --skill speckit-plan-raphaelfh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-plan automates implementation planning by applying a standardized plan template to generate design artifacts, reducing manual coordination and errors.

Core Features & Use Cases

  • Automates a multi-phase planning workflow from a plan template to produce artifacts like research.md, data-model.md, contracts/, and quickstart.md.
  • Validates and executes extension hooks before and after planning, distinguishing between optional and mandatory hooks.
  • Updates agent context and checks constitution gates to ensure plan viability and traceability in SPEC-kit projects.

Quick Start

Initiate speckit-plan on your SPEC-kit project to generate the full implementation plan and 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 generate design artifacts like data models and contracts from a project plan?

To generate design artifacts, apply a plan template to your project workflow to automatically produce research.md, data-model.md, contracts/, and quickstart.md. This standardizes generation and reduces manual coordination errors.

What is a plan template workflow for automating implementation planning?

A plan template workflow automates multi-phase implementation planning by reading the constitution and IMPL_PLAN to enforce gates, resolve clarifications, and validate extension hooks for deterministic planning results.

Does automated planning work with the .specify directory structure?

Automated planning works specifically with projects following the .specify directory structure. It reads the constitution and IMPL_PLAN to validate extension hooks and update agent context for deterministic outputs.

How do I validate extension hooks before and after project planning?

To validate extension hooks, the planning workflow distinguishes between optional and mandatory hooks, executing and checking them before and after the planning phases to ensure plan viability and traceability.

Why does implementation planning fail when constitution gates are not checked?

Implementation planning fails without checking constitution gates because they ensure plan viability and traceability. The workflow enforces these gates while updating agent context to prevent invalid planning states.