speckit-plan

Automate implementation planning to generate design artifacts from plan templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The speckit-plan skill orchestrates a structured implementation planning workflow by applying a plan template to produce design artifacts, enabling teams to move from abstract ideas to concrete plans with minimal manual orchestration.

Core Features & Use Cases

  • Orchestrates pre-execution checks and hook handling to ensure project readiness.
  • Guides outline generation, research, and design artifact creation (data-model.md, contracts/, quickstart.md) from a plan template.
  • Supports post-plan extension hooks and artifact reporting to keep stakeholders aligned.

Quick Start

Run the speckit-plan skill to trigger the end-to-end planning workflow using the project's plan template and IMPL_PLAN to generate artifacts and update the agent context.

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?

Automated implementation planning applies a plan template to generate design artifacts like data models and contracts. It orchestrates pre-execution checks and hook handling to ensure project readiness before producing design outputs.

What are design artifacts generated during implementation planning?

Design artifacts produced during implementation planning include data-model.md, contracts directories, and quickstart.md. These artifacts are generated from a plan template to guide development and keep stakeholders aligned.

Do I need .specify/ directories to generate implementation plans?

Projects using .specify/ directories and IMPL_PLAN templates are required for artifact generation. The planning workflow applies these templates to enforce pre and post-execution checks while producing ready-to-ship plans.

How does pre-execution hook handling work for implementation planning?

Pre-execution hook handling enforces explicit checks and unknown resolution before generating artifacts. It ensures project readiness through strict gate evaluations before the plan template produces design outputs.

What is the best way to keep stakeholders aligned after generating a plan?

Post-plan extension hooks and artifact reporting keep stakeholders aligned after generating plans. These hooks trigger reporting actions once design artifacts are created, ensuring downstream visibility into the implementation plan.

Can I use this planning workflow without strict gate evaluations?

Strict gate evaluations are enforced during implementation planning to produce ready-to-ship plans. Bypassing these gates is not supported, as they validate unknown resolution and ensure project readiness before artifact generation.