speckit-plan

Generate technical implementation plans from feature specifications using project structure.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of detailed technical implementation plans from feature specifications, ensuring all architectural and technical aspects are considered before development begins.

Core Features & Use Cases

  • Automated Planning: Generates a comprehensive plan including architecture, tech stack, and phased implementation.
  • Contextual Research: Identifies and researches unknowns and dependencies to inform the plan.
  • Use Case: After defining a new feature in a spec.md file, use this Skill to generate a plan.md that outlines the necessary technical steps, data models, and contracts.

Quick Start

Use the speckit-plan skill to generate a technical implementation plan for the feature described in the attached file 'new-user-auth.md'.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
How do I generate a technical implementation plan from feature specifications?

Generating a technical implementation plan from feature specifications involves parsing your project structure and feature input to outline architecture, tech stack, data models, and phased implementation strategies.

What is the process for automating architectural design and technology stack selection?

Automating architectural design and technology stack selection is achieved by applying a predefined implementation plan template to your feature specifications, ensuring all technical aspects are considered before development begins.

Do I need a specific directory structure to generate implementation plans?

Yes, you need a `.specify/` directory in your project to provide context, and a `spec.md` file defining the feature, which the Skill uses to output a `plan.md` with the required technical steps.

How to create a phased implementation strategy from a specification file?

To create a phased implementation strategy from a specification file, attach the feature file to the Skill, which will then research unknowns, identify dependencies, and generate a structured plan document.

Does this planning approach identify technical dependencies and unknowns before development?

Yes, this planning approach identifies and researches unknowns and dependencies to inform the final plan, ensuring all architectural and technical aspects are considered before development begins.

When should I not use automated technical design generation for software development?

You should not use automated technical design generation when your project lacks a `.specify/` directory or predefined feature specifications, as the Skill requires these inputs to parse project context and apply the planning template.