What roles do the subagents play?

Subagents simulate specialized roles like Backend Engineer, Security Specialist, DevOps, and QA to provide diverse perspectives and identify potential flaws in the initial plan.

Does this skill write implementation code?

No, this is a planning-only skill. It focuses exclusively on creating a high-quality technical specification and implementation plan in markdown format without modifying your source code.

Why use SDD instead of direct implementation?

Specification-Driven Development ensures that all edge cases, security concerns, and architectural tradeoffs are addressed upfront, leading to higher quality, more maintainable software.

Where are the technical specifications stored?

Specifications are stored in a dedicated 'ai-spec/' directory at the root of your repository, organized by date and task description for easy versioning and review.

SDD Planning Architect

Name: SDD Planning Architect
Author: kgadek

bykgadek

Productividad y Flujo de Trabajo

Facilitates high-quality software architecture through a multi-stage Specification-Driven Development (SDD) workflow and multi-agent feedback.

Acerca de

This skill implements a rigorous Specification-Driven Development (SDD) process within Claude Code, transforming vague user requests into comprehensive, battle-tested technical specifications. It leverages a structured workflow—including deep codebase exploration, initial design drafting, and a unique two-stage feedback loop from specialized virtual subagents (such as Security, DevOps, and QA)—to ensure every architectural decision is vetted for maintainability and edge cases before implementation begins.

Características Principales

Read-only codebase exploration to ensure plan accuracy
Positive-sum consensus building for complex architectural decisions
Multi-stage SDD workflow for robust technical planning
0 GitHub stars
Automated creation of structured 'ai-spec' documentation directories
Specialized subagent feedback from multiple engineering perspectives

Casos de Uso

Planning high-risk refactors of legacy systems
Standardizing technical documentation and implementation roadmaps
Designing complex new features requiring cross-functional alignment

Acerca de

Características Principales

Read-only codebase exploration to ensure plan accuracy
Positive-sum consensus building for complex architectural decisions
Multi-stage SDD workflow for robust technical planning
0 GitHub stars
Automated creation of structured 'ai-spec' documentation directories
Specialized subagent feedback from multiple engineering perspectives

Casos de Uso

Planning high-risk refactors of legacy systems
Standardizing technical documentation and implementation roadmaps
Designing complex new features requiring cross-functional alignment