speckit-plan

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/alidotcom2000/RSSFeedReader --skill speckit-plan-alidotcom2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/alidotcom2000/RSSFeedReader/tree/main/.github/skills/speckit-plan
Command: npx skills add https://github.com/alidotcom2000/RSSFeedReader --skill speckit-plan-alidotcom2000

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 Technical Context and Constitution Check sections in the plan template. - Research & Design Artifacts: Generates research.md, data-model.md, contracts/, and quickstart.md through structured Phase 0 and Phase 1 workflows. - 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 produce a complete implementation plan with resolved technical decisions, entity models, and API contracts ready for task breakdown. ## Quick Start Run the speckit-plan skill to generate an implementation plan and design artifacts from 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 your feature spec and plan template, then fills Technical Context, resolves unknowns in Phase 0 research, and produces design artifacts in Phase 1.

What artifacts does the spec-kit plan workflow generate?

The workflow generates research.md with resolved technical decisions, 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 project with a .specify/ directory containing scripts/powershell/setup-plan.ps1 and memory/constitution.md. Without this structure, the setup step cannot locate the feature spec and plan template.

How do extension hooks work in the plan workflow?

Hooks are defined in .specify/extensions.yml under hooks.before_plan and hooks.after_plan. Mandatory hooks (optional: false) are executed automatically, while optional hooks are presented for manual invocation.

What happens when Technical Context has unresolved unknowns?

Unknowns marked as NEEDS CLARIFICATION become research tasks in Phase 0. Each is investigated and consolidated into research.md with a decision, rationale, and alternatives considered before design proceeds.