speckit-plan

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

32|9|Updated Feb 2, 2024
One-click install
npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-plan-esri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/Esri/arcgis-gitops/tree/main/.github/skills/speckit-plan
Command: npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-plan-esri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires resolving technical unknowns, defining data models, and drafting interface 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. - Design Artifact Generation: Produces research.md, data-model.md, contracts/, and quickstart.md by resolving NEEDS CLARIFICATION items and extracting entities 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 in a spec-kit project, invoke this Skill to automatically research unknowns, design the data model, and produce a validated implementation plan on the feature branch. ## Quick Start Ask the agent to run the speckit plan workflow for the current feature branch to generate the implementation plan and design artifacts.

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 in 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 plan workflow produce?

The workflow produces research.md in Phase 0, then data-model.md, a contracts/ directory, and quickstart.md in Phase 1. It also updates the implementation plan file with Technical Context and Constitution Check sections.

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 the plan template. Without this structure the setup step cannot locate the feature spec and plan paths.

What happens when Technical Context contains NEEDS CLARIFICATION?

Each NEEDS CLARIFICATION item becomes a research task in Phase 0. The workflow dispatches research for each unknown and consolidates decisions, rationale, and alternatives into research.md before proceeding to design.

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 to the user with their command and prompt.