What problem does it solve?
MDCU guides software teams to avoid premature solutions by centering the user problem, using a six-phase flow that distills artifacts into a single SOAP at session end to capture decisions and rationale.
Core Features & Use Cases
- Structured six-phase MDCU workflow with transient artifacts and a final SOAP.
- Guardrails including ARCHITECTURE.md gating, RSOP SOAP, and a persistent RSOP registry to prevent looped cycles.
- Optional escalation via the mdcu-seg flow for security concerns during the cycle; suitable for projects needing re framing or pivoting.
- Use Case: start a new software project, reframe an existing problem, or pivot a current effort without leaping to code.
Quick Start
Run /mdcu to start an MDCU session and follow the six phases (F1–F6) to produce a SOAP with the final decisions, ensuring ARCHITECTURE.md exists before starting F1.