speckit-plan

Transform feature specifications into design artifacts and resolved research decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a feature specification into a structured implementation plan with resolved research questions, clear design artifacts, and gate checks so you can move forward confidently.

Core Features & Use Cases

  • Pre- and post-extension hook support: Runs configurable hooks from .specify/extensions.yml before and after the planning workflow.
  • Artifact-driven planning workflow: Produces research.md, data-model.md, contracts/, and quickstart.md while following the plan template structure.
  • Guardrails via constitution checks: Performs constitution-based validation and halts on gate failures or unresolved clarifications.

Quick Start

Run the planning workflow for your spec-kit project so it generates research.md, data-model.md, contracts, and quickstart.md using your feature specification and constitution.

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 specification?

To generate an implementation plan, this Skill transforms a feature specification into design artifacts and resolved research decisions. It produces research.md, data-model.md, contracts, and quickstart.md by executing Phase 0 research and Phase 1 generation workflows.

What does a spec-kit constitution check do during implementation planning?

A constitution check validates your implementation plan against predefined guardrails, halting the workflow on gate failures or unresolved clarifications. It ensures your design artifacts comply with project rules before you proceed to development.

How do I resolve NEEDS CLARIFICATION items in my spec-kit project?

To resolve NEEDS CLARIFICATION items, the workflow captures these open questions and resolves them into a research.md file. This ensures all research decisions are documented and clarified before data-model and contract generation begins.

Can I use this implementation planning workflow without running setup-plan first?

No, you must run the setup-plan PowerShell step before using this workflow. It prepares the required .specify/ directory structure, loads constitution context, and updates agent context to ensure the planning workflow executes correctly.

What design artifacts are produced by an artifact-driven planning workflow?

An artifact-driven planning workflow produces research.md, data-model.md, contracts/, and quickstart.md. These artifacts provide the structured design documents and resolved decisions needed to achieve full implementation readiness.

Why does my implementation plan halt before generating contracts?

Your implementation plan halts because the workflow enforces constitution gate checks and stops if it encounters unresolved clarifications. You must resolve all open research questions to pass the validation and continue generating contracts.