speckit-plan

Convert feature specifications into structured plan.md technical designs.

2|Updated Jan 29, 2026

Search Tags:#automation #planning #architecture #templates #specifications #phases #technical-design

Ready to run

npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-plan-pradeepmouli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-plan
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-plan-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams translate feature specifications into concrete, actionable implementation plans. It outputs key architectural decisions, technology choices, and a phased rollout strategy to guide development.

Core Features & Use Cases

Architecture planning: Define system components, interactions, and deployment considerations from a spec.
Tech stack guidance: Recommend libraries, frameworks, and tooling aligned with the spec.
Phased implementation: Outline milestones and tasks for design, prototyping, and production rollout.
Output artifacts: Produce plan.md with a structured technical design document.

Quick Start

Provide a feature specification and run Speckit Plan to generate a detailed implementation plan.

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 design document from feature specifications?▼

To generate a technical design document from feature specifications, provide your spec to an automated planning tool that outputs a structured plan. This process translates feature requirements into concrete architectural decisions, recommended tech stacks, and a phased implementation roadmap.

What is the best way to define architecture and tech choices from a project spec?▼

Defining architecture and tech choices from a project spec is best handled by generating a structured implementation plan. This approach systematically evaluates your feature specifications to output key system components, library recommendations, and deployment interactions.

How do I create a phased implementation roadmap for a new software feature?▼

You create a phased implementation roadmap by processing your feature specification through an architecture planning workflow. This evaluates the spec to outline specific milestones and tasks required for design, prototyping, and final production rollout.

Can I get automated recommendations for a tech stack from a feature specification?▼

Yes, you can get automated tech stack recommendations directly from a feature specification. Automated planning tools analyze your spec to suggest aligned libraries, frameworks, and tooling, which are then compiled into a structured plan document.

Does architecture planning work for converting complex specs into rollout phases?▼

Architecture planning works effectively for converting complex specs into rollout phases by systematically breaking down requirements. It evaluates system interactions and deployment considerations to define structured milestones spanning from initial design to production rollout.

What format does the implementation plan output use for technical designs?▼

The implementation plan output uses a structured markdown format, specifically producing a plan.md file. This document captures your architectural decisions, recommended tech stack, and the complete phased implementation roadmap.