speckit-plan

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

Updated May 19, 2026
One-click install
npx skills add https://github.com/Nasalciuc/ATS-HERO --skill speckit-plan-nasalciuc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/Nasalciuc/ATS-HERO/tree/main/.cursor/skills/speckit-plan
Command: npx skills add https://github.com/Nasalciuc/ATS-HERO --skill speckit-plan-nasalciuc

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 time-consuming when done manually. ## Core Features & Use Cases - Plan Workflow Execution: Runs the spec-kit planning workflow via setup-plan.ps1, filling the Technical Context and Constitution Check sections of the plan template. - Research Generation: Dispatches research tasks for every NEEDS CLARIFICATION item and consolidates decisions, rationale, and alternatives into research.md. - Design Artifact Generation: Produces data-model.md, interface contracts, and quickstart.md validation guides from the feature spec. - Extension Hooks: Executes optional and mandatory before_plan and after_plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec with spec-kit, run this Skill to automatically produce research.md, data-model.md, contracts, and a quickstart guide on the feature branch. ## Quick Start Run the speckit-plan skill to generate the implementation plan and design artifacts for my current feature specification.

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 workflow, which 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 plan workflow produce?▼

The workflow produces research.md with decisions and rationale in Phase 0, then data-model.md, interface contracts under /contracts/, and a quickstart.md validation guide in Phase 1.

Does speckit-plan require a specific project structure?▼

Yes, it requires a spec-kit project structure with a .specify directory containing scripts, memory/constitution.md, and templates. It also optionally reads .specify/extensions.yml for hooks.

What happens when Technical Context has unresolved items?▼

Each NEEDS CLARIFICATION item becomes a research task in Phase 0. The workflow dispatches research for unknowns and best practices, then consolidates findings in research.md before proceeding to design.

How do extension hooks work in the planning workflow?▼

Hooks are defined under hooks.before_plan and hooks.after_plan in .specify/extensions.yml. Mandatory hooks are executed automatically and the workflow waits for them, while optional hooks are only suggested to the user.