speckit-plan

Generates implementation plans and design artifacts from feature specifications using the spec-kit planning workflow.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-plan-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-plan-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete technical plan requires resolving unknowns, designing data models, and defining contracts — work that is often skipped or done inconsistently. This Skill automates that planning workflow so every feature gets research, design artifacts, and constitution checks before any code is written. ## Core Features & Use Cases - Phased Plan Generation: Runs Phase 0 research (resolving NEEDS CLARIFICATION items into research.md) and Phase 1 design (data-model.md, contracts/, quickstart.md) from the plan template. - Constitution Gate Evaluation: Checks the plan against the project's constitution.md and errors on unjustified violations, both before and after design. - Extension Hook Support: Executes mandatory and optional before_plan/after_plan hooks declared in .specify/extensions.yml. - Use Case: After writing a feature spec with spec-kit, invoke this Skill to produce a complete plan.md plus research, data model, API contracts, and a quickstart validation guide for the feature branch. ## Quick Start Run the speckit-plan skill with optional planning guidance to generate the implementation plan and design artifacts for the current feature branch.

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?

Invoke the speckit-plan skill inside a spec-kit project. It runs setup-plan.sh to locate the feature spec and plan template, then fills Technical Context, resolves unknowns into research.md, and produces data-model.md, contracts, and quickstart.md.

What artifacts does the spec-kit planning workflow produce?

The workflow produces plan.md as the main artifact, plus research.md with resolved clarifications, data-model.md with entities and validation rules, a contracts/ directory for external interfaces, and quickstart.md with validation scenarios.

Does speckit-plan require a specific project structure?

Yes, it requires a spec-kit initialized project with a .specify/ directory containing scripts/bash/setup-plan.sh, memory/constitution.md, and the plan template. Without this structure the setup step cannot locate the feature spec and plan paths.

What happens when the plan violates the project constitution?

The skill evaluates the Constitution Check section against .specify/memory/constitution.md and raises an ERROR on gate failures or unjustified violations, both during initial planning and again after the design phase completes.

Can I run custom hooks before or after planning?

Yes, hooks declared under hooks.before_plan and hooks.after_plan in .specify/extensions.yml are executed. Mandatory hooks run automatically, optional hooks are presented for manual invocation, and hooks with enabled: false are skipped.