sdd-planning

Generate implementation plans with data models, API contracts, and test scenarios.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aseesy/DEMO --skill sdd-planning-aseesy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-planning
Source: https://github.com/aseesy/DEMO/tree/main/.claude/skills/sdd-workflow/sdd-planning
Command: npx skills add https://github.com/aseesy/DEMO --skill sdd-planning-aseesy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill orchestrates the creation of comprehensive implementation plans from a complete feature specification using Specification-Driven Development (SDD). It generates artifacts such as research notes, data models, API contracts, and test scenarios, while validating constitutional compliance to ensure reusable, testable, and contract-first design.

Core Features & Use Cases

  • Research & artifact generation: Creates research notes, data-model definitions, contracts, and quickstart tests.
  • Constitutional validation: Enforces 14 constitutional principles (Library-First, Test-First, Contract-First, etc.) and tracks dependencies.
  • Execution readiness: Produces plan artifacts and prepares for the /tasks step.

Quick Start

Use the sdd-planning skill after you have a completed feature spec. Run the plan template to generate research.md, data-model.md, contracts/, and quickstart.md for downstream task generation.

Frequently Asked Questions about sdd-planning

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

FAQPage Schema
How do I create an implementation plan from a feature specification?

Specification-Driven Development (SDD) generates comprehensive implementation plans directly from complete feature specs. The sdd-planning skill orchestrates a nine-phase workflow that produces research notes, data models, API contracts, and test scenarios, ensuring your plan is architecturally sound and ready for execution.

What artifacts does an SDD planning workflow produce?

SDD planning generates research.md documenting findings, data-model.md defining database schemas, contracts/ containing API specifications, and quickstart.md with initial test cases. These artifacts enforce contract-first and test-first design principles while tracking dependencies across your implementation.

How does specification-driven development validate design before implementation?

SDD applies 14 constitutional principles including Library-First, Test-First, and Contract-First to validate your design. Constitutional checks ensure reusability, testability, and compliance before you move to task generation, catching architectural issues early.

Can I use SDD planning for APIs, data models, and test scenarios together?

Yes. SDD planning generates all three in one workflow: API contracts define endpoints and schemas, data models specify database structure, and quickstart tests validate both. This integrated approach ensures contracts and tests stay synchronized with your data design.

What do I need before running the planning step?

You need a completed feature specification that captures requirements, scope, and acceptance criteria. The sdd-planning skill then transforms that spec into research notes, architecture decisions, data models, and contracts ready for the next implementation phase.