speckit-plan

Generate implementation plans and artifacts from a feature spec.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/EmpoweredHouse/accrete --skill speckit-plan-empoweredhouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/EmpoweredHouse/accrete/tree/main/skills/speckit-plan
Command: npx skills add https://github.com/EmpoweredHouse/accrete --skill speckit-plan-empoweredhouse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the implementation planning process by translating a ready feature spec into an actionable plan and artifacts, enabling faster, consistent delivery.

Core Features & Use Cases

  • Generates research, data-model, contracts, quickstart and plan artifacts from a feature spec.
  • Orchestrates Phase 0-2 planning workflow and validates outputs.
  • Applies when a spec is ready and a deterministic plan is required for engineering teams.

Quick Start

Run speckit-plan from the repository root to generate the implementation plan using specs.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
How do I generate an implementation plan from a feature spec?

Feature implementation planning translates a ready feature spec into an actionable plan and structured design artifacts. This process produces research, data models, contracts, and quickstart materials, enabling engineering teams to achieve faster and consistent delivery.

What's the best way to automate data model and contract generation for engineering planning?

Automating data model and contract generation requires a planning workflow that applies templates to a ready feature spec. This approach orchestrates Phase 0-2 planning, validates outputs, and emits structured design artifacts to spec paths for consistent engineering delivery.

When do I need to use a structured planning workflow for feature implementation?

A structured planning workflow for feature implementation is needed when a feature spec is ready and a deterministic plan is required. It validates outputs and generates research, data models, contracts, and quickstart artifacts to ensure consistent engineering delivery.

How do I validate design artifacts and implementation gates during feature planning?

Validating design artifacts and implementation gates during feature planning involves orchestrating a Phase 0-2 workflow that validates outputs against spec requirements. This ensures emitted data models, contracts, and quickstart materials meet deterministic delivery standards before engineering begins.

Does automated feature planning work without a completed feature spec?

Automated feature planning requires a completed feature spec to function correctly. The workflow applies when a feature spec is ready, loading necessary context from the spec to generate deterministic implementation plans, data models, contracts, and quickstart materials.

Why does feature implementation planning require emitting artifacts to spec paths?

Emitting artifacts to spec paths during feature implementation planning ensures structured design outputs like data models and contracts are stored deterministically. This validates implementation gates and maintains consistent artifact accessibility for engineering teams.