sdd-planning_skill

Overview

This skill transforms specifications into clear, actionable technical plans. It produces structured architecture, technology choices, implementation phases, risk assessments, and test strategies tailored to the spec and project constraints.

How this skill works

The skill reads the provided specification and research artifacts, extracts functional and non-functional requirements, then designs an architecture and component breakdown. It selects technology options with rationale, sequences implementation phases with estimates, and produces a markdown plan that can be exported as tasks for implementation.

When to use it

• You have a spec but no implementation plan
• Designing system architecture or component responsibilities
• Breaking features into phased, implementable tasks
• Preparing for development handoff or sprint planning
• After research is complete and tradeoffs need to be recorded

Best practices

• Start by confirming acceptance criteria and non-functional requirements from the spec
• Prefer existing platform stack when it meets requirements to reduce risk
• Break work into phases (Setup → Core → Integration → Polish) with clear dependencies
• Document technology tradeoffs and assumptions explicitly
• Include measurable performance and security targets to guide implementation

Example use cases

• Convert a product spec into a technical plan with components, APIs, and data models
• Design an architecture for a new microservice and estimate implementation effort
• Create phased implementation and testing strategy for a feature rollout
• Produce risk register and mitigation steps before development kickoff
• Generate task-ready output to feed into a /tasks pipeline for execution