speckit-plan

Execute the implementation planning workflow to generate design artifacts.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/omerkllm/edris-antigravity --skill speckit-plan-omerkllm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/omerkllm/edris-antigravity/tree/main/.cursor/skills/speckit-plan
Command: npx skills add https://github.com/omerkllm/edris-antigravity --skill speckit-plan-omerkllm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute the implementation planning workflow using the plan template to generate design artifacts, reducing manual planning effort and enabling fast iteration.

Core Features & Use Cases

  • Pre-execution checks and extension hook support to conditionally execute extra steps.
  • Stepwise outline and phase-driven generation of artifacts such as research.md, data-model.md, contracts/, and quickstart.md.
  • Automated context updates and artifact wiring to keep the plan aligned with project requirements.

Quick Start

Provide your plan template and run the speckit-plan workflow to generate research.md, data-model.md, contracts/, and quickstart.md.

Frequently Asked Questions about speckit-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate generation of design artifacts like data models and contracts from a project plan template?

You can automate design artifact generation by running the speckit-plan workflow, which identifies your project plan template and outputs research.md, data-model.md, contracts/, and quickstart.md through a phase-driven process.

What design documentation files are generated when executing an automated planning workflow?

The automated planning workflow generates research.md for context, data-model.md for structure, contracts/ for API definitions, and quickstart.md for onboarding, keeping all documentation paths relative to the project root.

Can I run custom pre-execution and post-execution steps during the design artifact generation process?

Yes, you can conditionally execute custom pre- and post-plan actions by defining hooks in the .specify/extensions.yml file, which the planning workflow supports alongside standard prerequisite validation.

Why does my planning workflow halt before generating all the design artifacts?

The planning workflow halts on gate validation failures or when prerequisite checks detect unresolved clarifications, stopping the generation of artifacts like research.md and data-model.md until issues are resolved.

Does the design artifact generation process require absolute or relative file paths for documentation?

The process requires absolute file paths for filesystem operations and relative file paths for documentation, ensuring artifacts like contracts/ and quickstart.md are correctly wired and aligned with project requirements.