sdd-plan

Document selected design plans with alternatives and rollback strategies.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/rodacato/kwik-e-dev --skill sdd-plan-rodacato
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-plan
Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/lifecycle/skills/sdd-plan
Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill sdd-plan-rodacato

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When multiple viable implementations exist for a change, teams need a structured way to select and document a design approach to ensure alignment and traceability.

Core Features & Use Cases

  • Generate a formal design plan with at least two alternatives.
  • Document architecture, module/file changes, risks, and rollback strategies.
  • Ensure spec acceptance and provide a clear path to docs/sdd/<change-name>/plan.md.

Quick Start

Draft the plan for the selected change by listing at least two alternatives and save it to docs/sdd/<change-name>/plan.md once the spec is accepted.

Frequently Asked Questions about sdd-plan

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

FAQPage Schema
How do I document a design plan when multiple implementation options exist for a change?▼

To document a design plan with multiple options, generate a formal plan file that lists at least two alternatives, includes an architecture section, risk analyses, and rollback strategies, then save it to docs/sdd/<change-name>/plan.md.

What is the best way to evaluate architecture alternatives before implementation?▼

Evaluating architecture alternatives requires producing a formal design plan that compares viable options, documents risk analyses and rollback strategies, and confirms the chosen approach in a structured plan.md file.

Do I need an accepted spec before creating a design plan for change management?▼

Yes, an accepted spec is required before creating a design plan. The planning workflow mandates spec acceptance to ensure the documented alternatives and architecture decisions align with approved change requirements.

What should be included in a formal design plan for software architecture changes?▼

A formal design plan must include at least two alternatives, an architecture section, change files documentation, risk analyses, and a rollback strategy to ensure traceability and alignment before implementation.

Can I use this planning approach for changes without multiple viable alternatives?▼

This planning approach specifically applies when multiple viable alternatives must be evaluated. If only one implementation path exists, the formal alternative comparison and risk analysis workflow is not required.