speckit-plan

Generate design artifacts from implementation plans using a plan template.

4|11|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-plan-obsidian-owl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/Obsidian-Owl/floe/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-plan-obsidian-owl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and documents implementation planning by using a plan template to generate design artifacts, enabling consistent architecture decisions and artifact creation.

Core Features & Use Cases

  • Structured planning workflow that transforms ideas into executable plans.
  • Generates artifacts such as research.md, data-model.md, contracts/, and quickstart.md.
  • Applies to feature development projects requiring governance, design reviews, and architecture decisions.

Quick Start

Create a new plan for your feature by running the speckit-plan workflow against the feature repository and review the generated 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 design artifacts for feature architecture and integration planning?

To generate design artifacts for feature planning, use a structured workflow that applies a plan template against your repository, producing research.md, data-model.md, contracts/, and quickstart.md outputs for architecture decisions.

What is the best way to document implementation workflows and data models for a new feature?

Documenting implementation workflows requires a structured planning process that enforces project principles through a remembered constitution, outputting data-model.md and contract definitions to coordinate consistent architecture decisions and artifact creation.

Do I need a plan template and project constitution before starting feature architecture planning?

Yes, feature architecture planning requires an existing plan template and a remembered constitution to enforce project principles, ensuring generated design artifacts align with governance and integration design standards.

Can I use structured plan templates for design reviews and architecture decisions in feature development?

Structured plan templates support feature development by coordinating architecture decisions and design reviews, transforming ideas into executable plans while generating standardized artifacts like research.md and quickstart.md.

What design artifacts are generated during end-to-end feature planning and integration design?

End-to-end feature planning generates research.md, data-model.md, contracts/, and quickstart.md artifacts, covering architecture decisions, integration design, and structured phases of artifact generation for the implementation workflow.