mkdecision-frameworklisted

# Decision Framework Builder Structures expert judgment into repeatable, auditable decision systems for recurring high-stakes choices. ## When to Use Activate when: - User asks "how should we handle X cases?" or "build triage system" - Designing escalation protocols or case management workflows - Billing ops, support, returns, incident response, compliance decisions - Any domain with classified decision types and routing rules ## Phase Anchor **Phase: 1 (Plan)** — Produces a decision framework document. **Handoff:** Developer agent implements the decision logic in code. ## Failure Handling - **Domain unclear:** Ask user for 3 example cases. Derive taxonomy from examples. - **No domain expert available:** Flag output as `needs-expert-input`. Mark uncertain classifications explicitly. ## Process (7 Steps) ### Step 1: Identify Decision Type Clarify the recurring decision being structured. What is decided? Who decides? How often? ### Step 2: Build Classification Taxonomy Load `references/decision-tree-template.md`. Map every case type into mutually exclusive categories. Aim for 3-7 top-level buckets — too few collapses distinct cases, too many creates lookup overhead. ### Step 3: Define Sequential Decision Rules Order rules by: **Safety > Compliance > Economics > Speed**. Never let speed override safety. Document the reasoning for each rule's position in the sequence. ### Step 4: Create Weighted Scoring Load `references/weighted-scoring-guide.md`. Define 3-5 factors w