speckit-plan

Generate design artifacts from a plan template for spec-driven projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the SPECKIT planning stage by converting a plan template into actionable design artifacts, reducing manual toil and increasing consistency across projects.

Core Features & Use Cases

  • Automatic execution of the SPECKIT plan workflow to generate IMPL_PLAN and related artifacts such as research.md, data-model.md, and quickstart.md.
  • Extension hook awareness: checks and executes eligible before/after hooks to extend the planning process.
  • Guardrails and validation: enforces unknown resolution, gates evaluation, and keeps artifacts in project-referenced paths.

Quick Start

Run the speckit-plan skill on a project with a plan template to generate the IMPL_PLAN and all 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 automate planning workflows to generate design artifacts?

Automating planning workflows generates concrete design artifacts by loading a plan template and producing research, data models, and contracts. This enforces guardrails for unknowns and gates while writing outputs to your repository in specified paths.

What design artifacts are generated during spec-driven project planning?

Spec-driven project planning produces an IMPL_PLAN alongside research.md, data-model.md, and quickstart.md artifacts. It also generates an updated agent context to guide downstream implementation tasks.

How do I enforce guardrails and validation for unknowns in project planning?

Enforcing guardrails for unknowns requires validating gates and resolution checks during the planning process. The workflow evaluates extension hooks and ensures all unknowns are resolved before writing artifacts to project-referenced paths.

Can I use extension hooks to customize the planning workflow?

Extension hooks customize the planning workflow by checking and executing eligible before and after hooks. This extends the planning process to fit specific project requirements while maintaining artifact consistency.

Does spec-driven planning work with existing plan templates?

Spec-driven planning works with existing plan templates by loading the template and automatically converting it into actionable design artifacts. You need a project with a plan template to generate the IMPL_PLAN and related outputs.

Why does my automated planning workflow keep failing on unresolved unknowns?

Automated planning workflows fail on unresolved unknowns because guardrails enforce strict resolution before proceeding. The workflow validates gates and requires all unknowns to be cleared to ensure artifact consistency.