cat .forgewright/polymath/handoff/context-package.md 2>/dev/null
cat .forgewright/product-manager/BRD/brd.md 2>/dev/null
cat .forgewright/business-analyst/handoff/ba-package.md 2>/dev/null

digraph ba_flow {
    rankdir=TB;

    "Client Request" [shape=doublecircle];
    "Phase 1: Stakeholder Discovery" [shape=box];
    "Phase 2: Structured Elicitation" [shape=box];
    "Phase 3: Critical Evaluation" [shape=box];
    "Information Complete?" [shape=diamond];
    "Phase 4: Information Gate" [shape=box];
    "Escalate gaps to client" [shape=box];
    "Hand off to PM" [shape=box];

    "Client Request" -> "Phase 1: Stakeholder Discovery";
    "Phase 1: Stakeholder Discovery" -> "Phase 2: Structured Elicitation";
    "Phase 2: Structured Elicitation" -> "Phase 3: Critical Evaluation";
    "Phase 3: Critical Evaluation" -> "Information Complete?";
    "Information Complete?" -> "Phase 4: Information Gate" [label="yes"];
    "Information Complete?" -> "Escalate gaps to client" [label="no"];
    "Escalate gaps to client" -> "Phase 2: Structured Elicitation" [label="new info"];
    "Phase 4: Information Gate" -> "Hand off to PM";
}

notify_user:
  "Who needs to be considered in this project?"
  Options:
  > "Just me — I'm the decision maker and user (Recommended)"
  > "I decide, but others will use it"
  > "Multiple stakeholders — let me explain roles"
  > "Chat about this"

notify_user:
  "Let's map who's involved. For each person/role, I need to understand their
   decision power and how much this affects them."
  Options:
  > "I'll describe the stakeholders (Recommended)"
  > "It's mainly internal — team and leadership"
  > "External clients + internal team"
  > "Complex organization — multiple departments"
  > "Chat about this"

undefined

---

notify_user:
  "Before we proceed, I need to validate a few things about your request.
   [Summarize what's already clear from the user's message]
   
   What I still need from you: [list the 6W1H gaps detected]"
  Options:
  > "Here's the missing info: [fill in template] (Recommended)"
  > "Let me explain the full context"
  > "Chat about this"

notify_user:
  "Let me understand the current situation before we design a solution.
   How does this process work TODAY (before any software)?"
  Options:
  > "I'll walk you through the current process (Recommended)"
  > "There is no current process — this is entirely new"
  > "We have a system but it doesn't do [specific thing]"
  > "Chat about this"

notify_user:
  "What is absolutely critical for the FIRST version?
   (I need to separate must-haves from nice-to-haves)"
  Options:
  > "These are the must-haves: [list] (Recommended)"
  > "Everything I described is critical"
  > "Let me prioritize — show me a framework"
  > "Chat about this"

notify_user:
  "I understand everything feels important. But if we had to launch with
   only 50% of features next week, which 50% would you choose?
   This helps me identify actual priorities vs. aspirations."
  Options:
  > "OK, let me rank them (Recommended)"
  > "We cannot cut anything — all features are blockers"
  > "Help me think through what to prioritize"
  > "Chat about this"

notify_user:
  "I need to map your current process step by step.
   Starting from the trigger event — what kicks off this process?"
  Options:
  > "It starts when [trigger event] (Recommended)"
  > "Let me describe the full workflow"
  > "There's no formal process — people handle it ad hoc"
  > "Chat about this"

notify_user:
  "Now let's stress-test. What happens when things go wrong?"
  Options:
  > "Here are the common failure scenarios (Recommended)"
  > "Things rarely go wrong — happy path is enough"
  > "Let me think about edge cases"
  > "Chat about this"

notify_user:
  "In my experience, 80% of development time goes to handling the 20% of
   cases that 'rarely happen.' Let me suggest some:
   
   - What if [data is invalid/missing]?
   - What if [the user makes a mistake]?
   - What if [the volume is 10x normal]?
   - What if [an external system is down]?"
  Options:
  > "Good points — let me address each (Recommended)"
  > "Those scenarios don't apply to us"
  > "Handle errors with sensible defaults"
  > "Chat about this"

FOR each requirement in requirements_register:
  score = count(6W1H elements answered)
  IF score < 6:
    → This requirement is INCOMPLETE
    → Formulate a targeted follow-up question for the missing elements
    → Ask the client via notify_user
  IF score >= 6 AND no ambiguous terms:
    → This requirement is READY

REPEAT until ALL critical requirements score >= 6/7

notify_user:
  "I want to make sure I capture this precisely.
   You mentioned '[vague answer]'. Can you be more specific?
   
   For example, does this mean:"
  Options:
  > "[Specific interpretation A] (Recommended — based on context)"
  > "[Specific interpretation B]"
  > "[Specific interpretation C] — something else entirely"
  > "Chat about this"

notify_user:
  "I appreciate the trust, but I need YOUR decision here —
   I don't want to guess and build the wrong thing.
   
   Here are the options as I see them:"
  Options:
  > "[Option A — with trade-offs explained]"
  > "[Option B — with trade-offs explained]"
  > "[Option C — with trade-offs explained]"
  > "Chat about this"

undefined

Score = number of 6W1H answered with CONFIRMED information (not guessed) out of 7.
- Score ≥ 6 = **Ready** — can proceed to PM
- Score 4-5 = **Incomplete** — needs more elicitation (loop back)
- Score ≤ 3 = **Blocked** — fundamental information missing, escalate to client

---

notify_user:
  "I found some terms that could mean different things.
   Let me verify what you mean:
   
   '[ambiguous term]' — which of these do you mean?"
  Options:
  > "[Specific meaning A] (Recommended — based on context)"
  > "[Specific meaning B]"
  > "[Specific meaning C]"
  > "Chat about this"

notify_user:
  "Feasibility Assessment Summary:
   
   ✅ Highly feasible: [N] requirements
   ⚠️ Feasible with risks: [N] requirements  
   ❌ Not feasible as described: [N] requirements
   
   [Details for ❌ items]"
  Options:
  > "Review the risky items (Recommended)"
  > "Adjust scope to remove infeasible items"
  > "Proceed anyway — I accept the risks"
  > "Chat about this"

notify_user:
  "Interesting — it sounds like the real problem is [root cause],
   and [stated requirement] is one way to solve it.
   
   There might be simpler alternatives:"
  Options:
  > "Explore alternative solutions (Recommended)"
  > "No, I specifically need [original requirement]"
  > "You're right — let me restate the requirement"
  > "Chat about this"

notify_user:
  "Information Gate Assessment:
   
   ✅ Required checks: [N/8] passed
   📋 Recommended checks: [N/2] passed
   
   Here is a summary of what I've validated:
   [Brief summary of all confirmed requirements — restate key points]
   
   Is this complete and accurate?"
  Options:
  > "Yes, this is correct — hand off to PM (Recommended)"
  > "I need to correct something"
  > "Chat about this"

notify_user:
  "⚠️ Information Gate — BLOCKED
   
   Required checks: [N/8] passed — [list failed checks]
   
   I cannot hand off to PM yet because:
   [Specific list of what's missing or unconfirmed]
   
   These gaps would cause the BRD to be built on guesses,
   which leads to rework or building the wrong thing."
  Options:
  > "Let me provide the missing information (Recommended)"
  > "I understand the risk — override and proceed anyway"
  > "Chat about this"

undefined

**Persist to mem0 (mandatory after handoff file exists):**

```bash
python3 scripts/mem0-cli.py add "BA complete: [project/feature] | completeness [N]/7 | themes: [≤3 short phrases]" --category project

.forgewright/business-analyst/
├── stakeholder-analysis.md          # Power/Interest matrix, communication plan
├── elicitation/
│   ├── interview-notes-{date}.md    # Structured interview notes per round
│   ├── process-map-as-is.md         # Current business process (Mermaid)
│   ├── process-map-to-be.md         # Desired business process (Mermaid)
│   └── requirements-register.md     # All requirements with 6W1H scores
├── evaluation/
│   ├── critical-review.md           # Red team findings
│   ├── conflict-register.md         # Contradictions and resolutions
│   └── feasibility-assessment.md    # 4-dimension feasibility matrix
└── handoff/
    └── ba-package.md                # Validated package for PM handoff