Verified:GitHub

speckit-plan

Generate implementation planning artifacts from feature specs with constitution checks.

Updated Apr 6, 2026

Search Tags:#research #implementation planning #workflow orchestration #data model #spec-kit #contracts #constitution checks

Ready to run

npx skills add https://github.com/Congtrinhh/sholy-be --skill speckit-plan-congtrinhh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/Congtrinhh/sholy-be/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/Congtrinhh/sholy-be --skill speckit-plan-congtrinhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-plan helps teams turn a feature specification into a concrete implementation plan by orchestrating setup, context loading, gate checks, and phased artifact generation.

Core Features & Use Cases

Extension-aware pre/post hooks: Reads optional before_plan and after_plan hooks from .specify/extensions.yml and runs or reports them according to their optional/mandatory behavior.
Phased artifact production: Generates research.md, data-model.md, contracts/, and quickstart.md in Phase 0 and Phase 1, with constitution re-checking after design.
Guardrails and clarification handling: Resolves NEEDS CLARIFICATION items via research tasks and enforces ERROR on gate failures or unresolved clarifications.

Quick Start

Run speckit-plan with your feature context arguments so it creates research.md, data-model.md, contracts/, and quickstart.md according to the IMPL_PLAN workflow.

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

Implementation planning artifacts are produced by running a phased research-and-design workflow that generates research.md, data-model.md, contracts, and quickstart.md files. This workflow includes constitution re-checking after design and strict failure on unresolved clarifications.

How do I handle unresolved clarifications during implementation planning?▼

Unresolved clarifications are handled by resolving NEEDS CLARIFICATION items via research tasks. The workflow enforces an ERROR state on gate failures or if any clarifications remain unresolved, ensuring no incomplete plans proceed.

Can I run custom hooks before and after generating a design workflow?▼

Yes, you can run custom hooks before and after generating a design workflow by defining optional before_plan and after_plan hooks in your extensions configuration file. The workflow reads these hooks and runs or reports them according to their optional or mandatory behavior.

What artifacts are generated during spec-kit implementation planning?▼

Spec-kit implementation planning generates research.md, data-model.md, contracts directories, and quickstart.md artifacts across Phase 0 and Phase 1. These artifacts are created after context loading and gate validation checks are successfully completed.

Does implementation planning support JSON-based setup-plan parsing?▼

Yes, implementation planning supports JSON-based setup-plan parsing to orchestrate the workflow. It also satisfies requirements for optional extension hooks and enforces strict failure when gate validation encounters unresolved clarifications.