speckit-plan

Generate design artifacts from a predefined template in spec-kit projects.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/gherrerz/deepwiki --skill speckit-plan-gherrerz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/gherrerz/deepwiki/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/gherrerz/deepwiki --skill speckit-plan-gherrerz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the implementation planning workflow, allowing users to generate design artifacts using a predefined template.

Core Features & Use Cases

  • Implementation Planning: Execute the planning workflow using the plan template.
  • Design Artifacts Generation: Generate design artifacts such as research.md, data-model.md, contracts/, and quickstart.md.
  • Compatibility: Requires a spec-kit project structure with a .specify/ directory.
  • Use Case: Ideal for software development teams looking to streamline the planning phase of their projects.

Quick Start

Run the speckit-plan skill with the following command: /speckit-plan --argument "Optional guidance for the planning phase"

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 software development planning?

You can generate design artifacts by running the speckit-plan skill, which automates implementation planning to produce research.md, data-model.md, contracts/, and quickstart.md using a predefined template within a spec-kit project structure.

What is implementation planning automation for a spec-kit project?

Implementation planning for a spec-kit project uses a predefined plan template to automatically generate structured design artifacts, streamlining the software development planning phase and reducing manual documentation effort.

Do I need a spec-kit directory structure to generate design artifacts?

Yes, generating design artifacts requires an existing spec-kit project structure containing a .specify/ directory to ensure the planning workflow templates are correctly applied and artifacts are properly organized.

Can I pass custom guidance into the implementation planning workflow?

Yes, you can pass custom guidance into the implementation planning workflow using the optional argument hint, allowing you to direct the generation of design artifacts like contracts and quickstart.md.

What design artifacts are created during the spec-kit planning phase?

The spec-kit planning phase generates design artifacts including research.md, data-model.md, contracts/, and quickstart.md, providing a structured foundation for subsequent software development tasks.

Are there limitations when using templates for implementation planning?

A limitation of template-based implementation planning is the strict dependency on an existing spec-kit project structure with a .specify/ directory, making it unsuitable for software development projects lacking this specific setup.