sdd:plan

Generate a lean implementation plan from a feature spec into plan.md.

2|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/alfredoperez/sdd --skill sdd-plan-alfredoperez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd:plan
Source: https://github.com/alfredoperez/sdd/tree/main/skills/plan
Command: npx skills add https://github.com/alfredoperez/sdd --skill sdd-plan-alfredoperez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of a lean implementation plan from a feature spec, helping teams move from idea to actionable tasks with clear scope.

Core Features & Use Cases

  • Generates a complete plan.md from a standard template, populating the feature name, identifiers, and optional sections such as Technical Context, Flow, Data Model, and Risks as needed.
  • Updates the per-feature context state and logs transitions to enable auditability and traceability of the planning process.
  • Supports both manual and auto workflow modes by aligning plan generation with the feature's configured lifecycle and next steps.

Quick Start

Provide a feature description and run /sdd:plan to generate the plan.

Frequently Asked Questions about sdd:plan

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

FAQPage Schema
How do I generate an implementation plan from a feature spec?

To generate an implementation plan from a feature spec, you provide the feature description and run the generation process, which populates a plan.md template with the feature name, identifiers, and optional Technical Context, Flow, Data Model, and Risks sections.

What is a lean feature plan and what should it include?

A lean feature plan is an actionable document outlining the implementation approach, files, and next steps from a standard template, including optional sections like Technical Context, Flow, Data Model, and Risks as needed.

Can I use spec-to-plan automation for varying feature sizes?

Yes, spec-to-plan automation applies during the spec-to-plan stage across varying feature sizes to outline the approach, files, and next steps, aligning plan generation with the feature's configured lifecycle and next steps.

What's the best way to track and audit feature planning transitions?

The best way to track feature planning transitions is to use a system that updates the per-feature context state and logs transitions in a context file, enabling auditability and traceability of the planning process.

Does plan generation support manual and auto workflow modes?

Yes, plan generation supports both manual and auto workflow modes by aligning plan generation with the feature's configured lifecycle and next steps, and triggering pre- and post-plan hooks as configured.