sddl-plan

Generates staged execution plans with dependencies and validation strategy from design documents.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill sddl-plan-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sddl-plan
Source: https://github.com/nico0695/ai-tools/tree/main/sdd/sdd-lite/skills/sddl-plan
Command: npx skills add https://github.com/nico0695/ai-tools --skill sddl-plan-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a technical design into an actionable implementation sequence is error-prone: stages get missed, dependencies stay implicit, and approval boundaries blur. This Skill converts a design.md document into a compact, ordered plan.md that downstream executors and QA reviewers can consume without reinterpretation. ## Core Features & Use Cases - Staged Plan Generation: Produces plan.md with an ordered stage table, explicit dependencies, per-stage validation notes, and approval boundaries before code-touching work. - Open Question Surfacing: Carries unresolved design questions marked "Needed Before: execution" into the plan's Approval Notes so users see them before approving affected stages. - Planner and Macro-Plan Modes: Acts as the terminal stage for planner objectives (stopping at lifecycle_status planned) and supports approved macro-plan-first routes that decompose work into non-executable chunks. - Fix Stage Requests: Appends bounded fix stages scoped to confirmed review findings without rebuilding the whole plan. - Use Case: After finishing a design for a new API endpoint, run this stage to get a three-stage execution plan with validation checkpoints, then stop for approval before any code is written. ## Quick Start Ask the sddl orchestrator to run the planning stage on the current change's design.md to produce an executable staged plan for review.

Frequently Asked Questions about sddl-plan

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

FAQPage Schema
How do I turn a design document into an execution plan?▼

Run the sddl-plan stage after design: it reads design.md as the technical source of truth and writes plan.md with an ordered stage table, dependencies, per-stage validation notes, and approval boundaries. The output is directly executable by downstream executor stages.

What is a staged execution plan in spec-driven development?▼

A staged execution plan decomposes a change into ordered work units with explicit dependencies and validation expectations per stage. It keeps approval boundaries visible before code-touching work so users approve each risky stage before execution proceeds.

Can the planning stage handle unresolved design questions?▼

Yes. Design rows marked "Needed Before: execution" are recorded in the plan's Approval Notes with the stage they affect. Rows marked "Needed Before: design" that arrive still open cause the stage to return blocked rather than planning around an unmade decision.

When should I use planner mode versus full execution?▼

Use the planner objective when you only need a formalized plan without implementation: the stage stops with lifecycle_status planned and does not auto-route to execution. Full routes continue to executor approval after the plan checkpoint.

What are the limitations of automated execution planning?▼

The stage does not implement code, execute planned stages, or redefine scope and technical approach from earlier stages. It also cannot resolve open planning questions itself; material decisions are surfaced to the user instead of being guessed.