speckit-plan

Generates implementation plans and design artifacts from feature specifications using spec-kit templates.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-plan-omkar-code-mur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/Omkar-code-mur/Job-Radar/tree/main/Spec-it_job-Radar/.github/skills/speckit-plan
Command: npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-plan-omkar-code-mur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires resolving technical unknowns, designing data models, and defining contracts, which is slow and inconsistent when done manually. ## Core Features & Use Cases - Plan Workflow Execution: Runs the spec-kit planning workflow via setup-plan.ps1, filling Technical Context and Constitution Check sections in the plan template. - Research and Design Artifacts: Generates research.md to resolve NEEDS CLARIFICATION items, then produces data-model.md, contracts/, and quickstart.md. - Extension Hooks: Evaluates .specify/extensions.yml before and after planning to run optional or mandatory hook commands. - Use Case: After writing a feature spec in a spec-kit project, invoke this Skill to produce a complete Phase 0/Phase 1 design package with research decisions, entity models, API contracts, and a validation quickstart. ## Quick Start Run the speckit-plan skill 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?

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

What artifacts does the spec-kit planning workflow produce?

The workflow produces research.md with decisions and rationales, data-model.md with entities and validation rules, a contracts directory for external interfaces, and quickstart.md with runnable validation scenarios.

Does speckit-plan require a specific project structure?

Yes, it requires a spec-kit project with a .specify directory containing scripts/powershell/setup-plan.ps1, memory/constitution.md, and plan templates. Without this structure the setup step cannot resolve spec and plan paths.

What are extension hooks in the spec-kit plan workflow?

Extension hooks are commands defined in .specify/extensions.yml under hooks.before_plan and hooks.after_plan. Mandatory hooks are executed automatically, while optional hooks are only suggested, and hooks with conditions are skipped.

What happens when Technical Context contains NEEDS CLARIFICATION items?

Each NEEDS CLARIFICATION entry becomes a research task in Phase 0. The findings are consolidated in research.md with a decision, rationale, and alternatives considered, and all items must be resolved before Phase 1 design begins.