speckit.plan

Name: speckit.plan
Availability: InStock
Author: antigravityos187-sketch

Automate implementation planning workflows to generate design artifacts and documentation.

Updated Jun 3, 2026

Search Tags:#workflow #planning #code generation #implementation #design documentation

Ready to run

npx skills add https://github.com/antigravityos187-sketch/universal-or-strategy --skill speckit-plan-antigravityos187-sketch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit.plan
Source: https://github.com/antigravityos187-sketch/universal-or-strategy/tree/main/.bob/skills/speckit.plan
Command: npx skills add https://github.com/antigravityos187-sketch/universal-or-strategy --skill speckit-plan-antigravityos187-sketch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires , and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the implementation planning workflow to generate design artifacts, streamlining the creation of research and documentation files.

Core Features & Use Cases

Plan Execution Automation: Execute the planning workflow with a plan template, generating technical context and documentation artifacts.
User Input Consideration: Incorporates user input for informed planning decisions.
Pre-Execution Checks: Verifies extension hook configurations for execution flow management.
Multi-Phase Execution: Manages the outline and research phase, followed by design and contracts generation, ensuring a structured and comprehensive process.
Post-Execution Verification: Performs mandatory and optional hooks for post-processing and verification tasks.

Quick Start

Execute the implementation planning workflow for 'Feature A' by using the command: /speckit:plan Feature A

Frequently Asked Questions about speckit.plan

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

FAQPage Schema

How do I automate implementation planning for large-scale software design documentation?▼

Implementation planning for large-scale software projects is automated by executing structured workflow phases that generate technical context, design artifacts, and research documentation files from a plan template.

What's the best way to generate design contracts and technical context from a plan template?▼

Generating design contracts and technical context is handled through a multi-phase execution workflow that manages outline and research phases, followed by design and contracts generation for comprehensive documentation artifacts.

Does the planning workflow incorporate user input for code generation decisions?▼

Yes, the planning workflow incorporates user input during execution to inform planning decisions, ensuring generated design documentation and implementation artifacts align with specific project requirements.

How do pre-execution checks verify extension hook configurations during the planning workflow?▼

Pre-execution checks verify extension hook configurations to manage execution flow, while post-execution verification performs mandatory and optional hooks for post-processing and validation tasks.

Can I use this planning workflow for feature-level implementation tasks in software engineering?▼

Yes, you can execute the planning workflow for specific features using the command format, which triggers research, design documentation, and implementation artifact generation optimized for software engineering tasks.

What are the limitations when executing multi-phase planning workflows for design artifacts?▼

The planning workflow requires user input for informed decisions and depends on conditional hooks for execution flow management, meaning incomplete user input or missing hook configurations may impact artifact generation.