mdcu

Automate user-centered problem framing and decision documentation via MDCU's six-phase workflow.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/iago-leal/skills --skill mdcu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mdcu
Source: https://github.com/iago-leal/skills/tree/main/mdcu-framework/mdcu
Command: npx skills add https://github.com/iago-leal/skills --skill mdcu

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about mdcu

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

FAQPage Schema
What is user-centered software problem framing and when do I need it?

User-centered software problem framing distills project artifacts into a single SOAP to capture decisions and rationale. You need it during project initiation, problem reframing, or mid-course pivots to prevent leaping to premature code solutions.

How do I document software development decisions using a SOAP format?

You document software development decisions by running a structured six-phase workflow that processes transient artifacts into a final SOAP. This RSOP SOAP finalization captures your final decisions and rationale at the session end.

Do I need an ARCHITECTURE.md file to start the MDCU workflow?

Yes, you need an existing ARCHITECTURE.md file before starting the first workflow phase. ARCHITECTURE.md gating acts as a guardrail to ensure structural context is present before you begin the F1 phase.

Can I pivot an existing software project without rewriting code?

Yes, you can pivot an existing software project by applying the problem reenvisioning flow. This process recenters the user problem and produces a new SOAP with updated decisions, avoiding unnecessary code rewrites.

How does risk management work during the MDCU workflow cycle?

Risk management is handled through an optional escalation flow that addresses security concerns during the cycle. A persistent RSOP registry also prevents looped cycles by tracking previous decisions.

What are the limitations of using a structured workflow for problem reframing?

A limitation is that this structured workflow requires strict adherence to its six-phase flow and ARCHITECTURE.md gating. You should not use it if you need to bypass decision documentation or immediately generate code without problem delimitation.