What problem does it solve?
Designing complex systems often starts with an outcome but lacks the defined parts, interfaces, and failure paths needed for reliable implementation. This skill provides a structured, phase-driven approach to move from concept to a fully defined design across four system classes: UI, code architecture, business process, and automation pipeline.
Core Features & Use Cases
- Five-phase design workflow (Pre-Design Scan through Hand-Off) to surface scope, parts, interfaces, failure modes, and hand-off artifacts.
- Layered knowledge model: immediate frontmatter context, phase-specific instructions, and optional deep-dives via references and templates.
- Rich design outputs: scalable design documents (templates/design-document.md) and a repeatable hand-off process for developers and stakeholders.
- Open integration with existing skills and components to reference known parts, reuse templates, and promote design-to-build transitions.
Use cases include designing a non-trivial system from a user outcome, refining an abstract concept into a concrete design, and preparing hand-off documentation for a build team.
Quick Start
State the desired system outcome and boundary to begin the five-phase design process.
