sdd-plan

Automates Spec-Driven Development planning and outputs a complete .sdd/{change-name}/plan.md file.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/davidarce/devrune-starter-catalog --skill sdd-plan-davidarce
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-plan
Source: https://github.com/davidarce/devrune-starter-catalog/tree/main/workflows/sdd/sdd-plan
Command: npx skills add https://github.com/davidarce/devrune-starter-catalog --skill sdd-plan-davidarce

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the end-to-end Spec-Driven Development (SDD) planning workflow, transforming exploration context into a formal, actionable plan.

Core Features & Use Cases

  • Generates a complete .sdd/{change-name}/plan.md with detailed tasks, contract specs, and a batch execution table.
  • Records clarifications from deep interviews and supports multiple planning iterations, including guidance integration.
  • Supports re-entry via guidance prompts and engram persistence to maintain continuity across sessions.

Quick Start

Provide a change name and instructions to generate a complete SDD plan for that change.

Frequently Asked Questions about sdd-plan

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

FAQPage Schema
What is spec-driven development planning and how does it structure software changes?▼

Spec-driven development (SDD) planning translates exploration context into a formal implementation plan. It structures software changes by generating detailed tasks, contract specs, and a batch execution table within a dedicated plan file.

How do I automate the end-to-end planning workflow for spec-driven development?▼

Automate SDD planning workflows by providing a change name and instructions. The system analyzes exploration context, records deep interview clarifications, and outputs a complete plan with contract specs and a batch table.

Can I maintain planning context across multiple sessions for an architecture change?▼

Yes, planning context can be maintained across multiple sessions using guidance prompts and engram persistence. This supports re-entry into the planning workflow and preserves continuity for iterative architecture changes.

What is the best way to generate a complete plan with tasks and contract specs from exploration context?▼

The best way to generate a complete plan from exploration context is using an automated SDD planning workflow. It transforms initial context and interview outcomes into a detailed plan file containing actionable tasks, contract specs, and a batch execution table.

Does SDD planning support multiple iterations and guidance integration during the workflow?▼

Yes, SDD planning supports multiple planning iterations and guidance integration. It records clarifications from deep interviews and allows guidance prompts to refine the plan throughout the orchestration workflow.