Where does this skill save the design documents?

Documents are saved to the 'docs/design-plans/' directory using a standardized 'YYYY-MM-DD-topic.md' naming convention for easy tracking in git.

What is the difference between a design plan and an implementation plan?

Design plans are directional and archival, focusing on architecture and contracts (the 'what'). Implementation plans are tactical and just-in-time, focusing on executable code and step-by-step tasks (the 'how').

Can I include implementation code in these design plans?

Design plans should exclude implementation logic like function bodies. However, they should include 'contracts' such as TypeScript interfaces, API request/response shapes, and database schemas.

Why is there a limit of 8 phases per design plan?

The 8-phase limit is a deliberate constraint to ensure implementation plans remain scoped and manageable. If a design requires more phases, it encourages the user to split the project into smaller, more focused units.

Structured Design Planner

Name: Structured Design Planner
Author: ed3dai

byed3dai

•

Productividad y Flujo de Trabajo

Converts brainstorming sessions into permanent, structured technical design documentation with discrete implementation phases.

The Structured Design Planner skill bridges the gap between creative brainstorming and technical execution by generating high-quality design plans. It automates the creation of architectural documentation, defining clear system boundaries, API contracts, and 'Definitions of Done.' By organizing projects into manageable implementation phases (limited to eight for focus), it ensures that complex features are documented for posterity in your repository before a single line of application logic is written. This skill is essential for maintaining a clean research-plan-implement workflow and ensuring that architectural decisions are archival and directional.

Características Principales

01Automated 'Legibility Headers' including Summary, Glossary, and DoD

02Standardized Markdown documentation generation in docs/design-plans/

0345 GitHub stars

04Discrete implementation phase mapping with success criteria

05Integration of existing codebase patterns into new designs

06Contract-first specification for interfaces and API endpoints

Casos de Uso

01Formalizing architectural decisions after a research or brainstorming session

02Maintaining a permanent, version-controlled history of technical designs

03Creating multi-phase implementation roadmaps for complex features

Características Principales

01Automated 'Legibility Headers' including Summary, Glossary, and DoD

02Standardized Markdown documentation generation in docs/design-plans/

0345 GitHub stars

04Discrete implementation phase mapping with success criteria

05Integration of existing codebase patterns into new designs

06Contract-first specification for interfaces and API endpoints

Casos de Uso

01Formalizing architectural decisions after a research or brainstorming session

02Maintaining a permanent, version-controlled history of technical designs

03Creating multi-phase implementation roadmaps for complex features