sdd-plan1

Coordinate subagent feedback to produce a structured SPEC document.

Updated Jan 19, 2026

Search Tags:#workflow #planning #architecture #spec #sdd #ai-coordination #specification-driven-development

Ready to run

npx skills add https://github.com/kgadek/kgadek-claude-plugin --skill sdd-plan1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-plan1
Source: https://github.com/kgadek/kgadek-claude-plugin/tree/main/plugins/kg/skills/sdd-plan1
Command: npx skills add https://github.com/kgadek/kgadek-claude-plugin --skill sdd-plan1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates a complex planning workflow to produce a robust Specification-Driven Development plan by guiding collaboration among specialized subagents and generating a repeatable SPEC artefact.

Core Features & Use Cases

Orchestrates subagents (architect, backend-eng, dx-eng, security, qa-eng, etc.) to gather diverse planning perspectives.
Produces a structured ai-spec directory including an initial plan and iterative feedback artifacts.
Finalizes a consolidated spec.md that can be handed to development teams for implementation.

Quick Start

Provide a user request and let the Skill orchestrate the SDD planning process to produce a complete ai-spec folder with an initial plan and final spec.

Frequently Asked Questions about sdd-plan1

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

FAQPage Schema

How do I coordinate specification-driven development planning across multiple engineering roles?▼

Specification-driven development planning is coordinated by orchestrating subagents like architect, backend, security, and QA to gather diverse perspectives, producing a structured ai-spec directory with iterative feedback artifacts.

What is the best way to generate a comprehensive software architecture SPEC from multi-round feedback?▼

Generating a comprehensive software architecture SPEC requires guiding an initial plan through multi-round subagent feedback, assessing risks, and finalizing the deliverables into a consolidated spec.md document for development teams.

Can I use this workflow to capture requirements and assess risks for cross-team software projects?▼

Yes, this SDD planning workflow applies to software architecture projects across teams, ensuring requirements capture, risk assessment, and deliverables are thoroughly documented in a repeatable planning process.

How do I structure an ai-spec directory for a new software planning workflow?▼

You structure an ai-spec directory by generating an initial plan, running iterative feedback rounds with specialized engineering subagents, and finalizing the results into a consolidated spec.md file.

Does specification-driven development require any specific framework dependencies to run the planning workflow?▼

No specific framework dependencies are required to run this specification-driven development planning workflow, which orchestrates subagents to produce a final SPEC artifact without needing external components.

When should I not use an orchestrated subagent workflow for software architecture planning?▼

You should avoid an orchestrated subagent workflow for software architecture planning when a project is too small to require multi-round feedback from specialized engineering roles or when a single, unstructured planning document is sufficient.