@monoes/monomindcli 1.10.54 → 1.10.55

package/.claude/skills/mastermind/runorg.md

@@ -152,7 +152,8 @@ curl -s -X POST "${CTRL_URL}/api/mastermind/event" \
     --arg session "$sessionId" \
     --arg org "$orgName" \
     --arg goal "$goal" \
-    '{type:"org:start",session:$session,org:$org,goal:$goal,ts:(now*1000|floor)}')" || true
+    --arg proj "$(pwd)" \
+    '{type:"org:start",session:$session,org:$org,goal:$goal,project:$proj,ts:(now*1000|floor)}')" || true
 ```
 
 ---
@@ -244,16 +245,22 @@ APPROVAL GATE (when governance.policy is "board" or "strict"):
   curl -s -X POST "${CTRL_URL}/api/mastermind/event" -H "Content-Type: application/json" \
     -d "$(jq -cn --arg org "${orgName}" --arg id "$approval_id" --arg title "<title>" \
       '{type:"org:approval:requested",org:$org,approval_id:$id,title:$title,ts:(now*1000|floor)}')" || true
-  # Poll until approved or rejected (max 30 min):
+  # Poll until approved or rejected (max 30 min).
+  # Check the approvals file first (updated by both dashboard UI and /mastermind:approve command),
+  # then fall back to memory in case an external notifier wrote there.
   for i in $(seq 1 60); do
-    status=$(npx monomind@latest memory search --query "approval:${approval_id}" --namespace "${memNs}" 2>/dev/null | jq -r '.[0].value.status // ""' 2>/dev/null)
+    status=$(jq --arg id "$approval_id" '.approvals[] | select(.id == $id) | .status // ""' "$approvalsFile" 2>/dev/null || echo "")
+    if [ -z "$status" ] || [ "$status" = "pending" ]; then
+      mem_status=$(npx monomind@latest memory search --query "approval:${approval_id}" --namespace "${memNs}" 2>/dev/null | jq -r '.[0].value.status // ""' 2>/dev/null)
+      [ -n "$mem_status" ] && status="$mem_status"
+    fi
     [ "$status" = "approved" ] && break
     [ "$status" = "rejected" ] && { echo "Action rejected by governance policy — skip this action"; break; }
     sleep 30
   done
 
 STOP DETECTION (check this FIRST in every loop iteration):
-  ls ${stopFile} 2>/dev/null && echo STOP_REQUESTED
+  [ -f "${stopFile}" ] && echo STOP_REQUESTED
 If the file exists: emit org:complete event, clean up with "rm -f ${stopFile}", then exit.
 
 OPERATING LOOP:
@@ -270,8 +277,14 @@ OPERATING LOOP:
    - Emit org:agent:online event to dashboard before starting (use curl, see below)
 5. Collect completed results from memory (search "${memNs}:report:")
 6. Synthesize reports, make decisions, create new cards in Todo column based on progress toward goal
-7. Emit org:checkpoint event with progress summary
-8. Wait ${checkpointMin} minutes, then loop back to step 1
+7. Write a run-completion entry to the activity log (used by the health dashboard for 7-day success rate):
+   activityFile=".monomind/orgs/${orgName}-activity.jsonl"
+   # Count Todo cards not yet claimed as the pending_tasks metric
+   pending_count=$(monotask card list ${board_id} --col ${todo_col} --json 2>/dev/null | jq '[.[] | select(.labels | index("claimed") | not)] | length' 2>/dev/null || echo 0)
+   echo "{\"type\":\"run:complete\",\"org\":\"${orgName}\",\"ts\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\",\"pending\":${pending_count:-0}}" >> "$activityFile"
+   (On error/exception, write: {"type":"run:error","ts":"...", "org":"..."})
+8. Emit org:checkpoint event with progress summary
+9. Wait ${checkpointMin} minutes, then loop back to step 1
 
 AGENT TYPES FOR YOUR TEAM:
 ${orgConfig.roles.filter(r => r.id !== bossRole.id).map(r =>
@@ -283,12 +296,13 @@ DASHBOARD EVENTS — emit via curl (NOT WebFetch — WebFetch does not support P
   CTRL_URL=$(jq -r '.url // "http://localhost:4242"' "$REPO_ROOT/.monomind/control.json" 2>/dev/null || echo "http://localhost:4242")
   curl -s -X POST "${CTRL_URL}/api/mastermind/event" \
     -H "Content-Type: application/json" \
-    -d "$(jq -cn --arg type TYPE --arg session SESSION --arg org ORG '{type:$type,session:$session,org:$org,ts:(now*1000|floor)}')"
+    -d "$(jq -cn --arg type TYPE --arg session SESSION --arg org ORG --arg proj "$REPO_ROOT" '{type:$type,session:$session,org:$org,project:$proj,ts:(now*1000|floor)}')"
 Payloads:
 - org:agent:online → add fields: role, title, agent_type
 - org:comms → add fields: from, to, msg
 - org:checkpoint → add fields: progress, pending_tasks
 - org:complete → no additional fields
+Note: always include project:$REPO_ROOT in all event payloads for correct multi-project SSE filtering
 
 START NOW: check for stop signal, assess the board, create initial tasks if none exist, then begin the operating loop.`
 })
@@ -311,7 +325,8 @@ curl -s -X POST "${CTRL_URL}/api/mastermind/event" \
     --arg role "$bossRole_id" \
     --arg title "$bossRole_title" \
     --arg agent_type "$bossRole_agent_type" \
-    '{type:"org:agent:online",session:$session,org:$org,role:$role,title:$title,agent_type:$agent_type,ts:(now*1000|floor)}')" || true
+    --arg proj "$REPO_ROOT" \
+    '{type:"org:agent:online",session:$session,org:$org,role:$role,title:$title,agent_type:$agent_type,project:$proj,ts:(now*1000|floor)}')" || true
 ```
 
 (Use the scalar string variables `$bossRole_id`, `$bossRole_title`, `$bossRole_agent_type` derived by extracting fields from `bossRole` before constructing the curl call.)

package/.claude/skills/mastermind/skill-builder.md

@@ -0,0 +1,274 @@
+---
+name: mastermind-skill-builder
+description: Use when creating new mastermind skills, editing existing mastermind skills, or verifying mastermind skills work before deployment
+---
+
+# Writing Mastermind Skills
+
+## Overview
+
+**Writing mastermind skills IS Test-Driven Development applied to process documentation.**
+
+**Mastermind skills live in `.claude/skills/mastermind/` and commands in `.claude/commands/mastermind/`.**
+
+You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes).
+
+**Core principle:** If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing.
+
+## What is a Mastermind Skill?
+
+A **skill** is a reference guide for proven techniques, patterns, or tools. Skills help future Claude instances find and apply effective approaches.
+
+**Skills are:** Reusable techniques, patterns, tools, reference guides
+
+**Skills are NOT:** Narratives about how you solved a problem once
+
+## TDD Mapping for Skills
+
+| TDD Concept | Skill Creation |
+|-------------|----------------|
+| **Test case** | Pressure scenario with subagent |
+| **Production code** | Skill document (`.md`) |
+| **Test fails (RED)** | Agent violates rule without skill (baseline) |
+| **Test passes (GREEN)** | Agent complies with skill present |
+| **Refactor** | Close loopholes while maintaining compliance |
+| **Write test first** | Run baseline scenario BEFORE writing skill |
+| **Watch it fail** | Document exact rationalizations agent uses |
+| **Minimal code** | Write skill addressing those specific violations |
+| **Watch it pass** | Verify agent now complies |
+| **Refactor cycle** | Find new rationalizations → plug → re-verify |
+
+## When to Create a Skill
+
+**Create when:**
+- Technique wasn't intuitively obvious
+- You'd reference this again across projects
+- Pattern applies broadly (not project-specific)
+- Others would benefit
+
+**Don't create for:**
+- One-off solutions
+- Standard practices well-documented elsewhere
+- Project-specific conventions (put in CLAUDE.md)
+- Mechanical constraints (if it's enforceable with regex/validation, automate it)
+
+## Skill Types
+
+### Technique
+Concrete method with steps to follow
+
+### Pattern
+Way of thinking about problems
+
+### Reference
+API docs, syntax guides, tool documentation
+
+## Directory Structure
+
+```
+.claude/skills/mastermind/
+  skill-name.md              # Main skill (required)
+
+.claude/commands/mastermind/
+  skill-name.md              # Command entry point (required)
+```
+
+**Flat namespace** — all mastermind skills in one searchable namespace.
+
+## Skill File Structure
+
+**Frontmatter (YAML):**
+- Two required fields: `name` and `description` (max 1024 characters total)
+- `name`: Use letters, numbers, and hyphens only (no parentheses, special chars)
+- `description`: Third-person, describes ONLY when to use (NOT what it does)
+  - Start with "Use when..." to focus on triggering conditions
+  - Include specific symptoms, situations, and contexts
+  - **NEVER summarize the skill's process or workflow** (see CSO section)
+  - Keep under 500 characters if possible
+
+```markdown
+---
+name: mastermind-skill-name
+description: Use when [specific triggering conditions and symptoms]
+---
+
+# Skill Name
+
+## Overview
+What is this? Core principle in 1-2 sentences.
+
+## Quick Reference
+Table or bullets for scanning common operations
+
+## The Process / Core Pattern
+Steps, before/after comparisons
+
+## Common Mistakes
+What goes wrong + fixes
+
+## Red Flags
+Never / Always lists
+```
+
+## Command File Structure
+
+Every skill needs a companion command file:
+
+```markdown
+---
+name: mastermind-[name]
+description: [one-line description of when to use]
+---
+
+**First — extract repeat flags:** Follow REPEAT PREAMBLE from `_repeat.md`.
+
+Parse `$ARGUMENTS` for `--auto`, `--confirm`, `--project <name>`, and remaining text.
+
+Load brain context (follow `_protocol.md` Brain Load Procedure).
+
+Default mode: **confirm** (or **auto** for low-risk/fast skills).
+
+---
+
+Invoke `Skill("mastermind:[name]")` passing: brain_context, params, mode.
+
+After skill returns: follow `_protocol.md` Brain Write Procedure.
+
+Invoke `Skill("mastermind:_repeat")` now. Required — do not skip.
+```
+
+## Claude Search Optimization (CSO)
+
+**Critical for discovery:** Future Claude must FIND your skill.
+
+### Description = When to Use, NOT What the Skill Does
+
+The description should ONLY describe triggering conditions. Do NOT summarize the skill's process or workflow in the description.
+
+**Why this matters:** When a description summarizes the workflow, Claude may follow the description instead of reading the full skill content — the skill body becomes documentation Claude skips.
+
+```yaml
+# BAD: Summarizes workflow
+description: Use when finishing branches - runs tests, shows 4 options, handles merge/PR/cleanup
+
+# BAD: Too much process detail
+description: Use for TDD - write test first, watch it fail, write minimal code, refactor
+
+# GOOD: Just triggering conditions
+description: Use when implementation is complete and you need to decide how to integrate the work
+
+# GOOD: Triggering conditions only
+description: Use when receiving code review feedback before implementing suggestions
+```
+
+### Keyword Coverage
+
+Use words Claude would search for:
+- Error messages and symptoms
+- Synonyms (timeout/hang/freeze, cleanup/teardown)
+- Tools: actual commands, library names
+
+### Token Efficiency (Critical)
+
+**Target word counts:**
+- Frequently-loaded skills: under 200 words total
+- Other skills: under 500 words (still be concise)
+
+**Techniques:**
+- Reference other skills instead of repeating content
+- Use cross-references: `**REQUIRED BACKGROUND:** Use Skill("mastermind:X")`
+- One excellent example beats many mediocre ones
+
+### Cross-Referencing Other Skills
+
+```markdown
+# GOOD: Explicit requirement marker
+**REQUIRED SUB-SKILL:** Use Skill("mastermind:worktree")
+**REQUIRED BACKGROUND:** You MUST understand Skill("mastermind:finish")
+
+# BAD: Unclear if required
+See mastermind/worktree.md
+```
+
+## The Iron Law (Same as TDD)
+
+```
+NO SKILL WITHOUT A FAILING TEST FIRST
+```
+
+This applies to NEW skills AND EDITS to existing skills.
+
+Write skill before testing? Delete it. Start over.
+Edit skill without testing? Same violation.
+
+**No exceptions:**
+- Not for "simple additions"
+- Not for "just adding a section"
+- Not for "documentation updates"
+- Delete means delete
+
+## RED-GREEN-REFACTOR for Skills
+
+### RED: Write Failing Test (Baseline)
+
+Run pressure scenario with subagent WITHOUT the skill. Document exact behavior:
+- What choices did they make?
+- What rationalizations did they use (verbatim)?
+- Which pressures triggered violations?
+
+### GREEN: Write Minimal Skill
+
+Write skill that addresses those specific rationalizations. Don't add extra content for hypothetical cases.
+
+Run same scenarios WITH skill. Agent should now comply.
+
+### REFACTOR: Close Loopholes
+
+Agent found new rationalization? Add explicit counter. Re-test until bulletproof.
+
+## Common Rationalizations for Skipping Testing
+
+| Excuse | Reality |
+|--------|---------|
+| "Skill is obviously clear" | Clear to you ≠ clear to other agents. Test it. |
+| "It's just a reference" | References can have gaps. Test retrieval. |
+| "Testing is overkill" | Untested skills have issues. Always. |
+| "I'll test if problems emerge" | Test BEFORE deploying. |
+| "I'm confident it's good" | Overconfidence guarantees issues. Test anyway. |
+
+## Skill Creation Checklist
+
+**RED Phase:**
+- [ ] Create pressure scenarios (3+ combined pressures for discipline skills)
+- [ ] Run scenarios WITHOUT skill — document baseline behavior verbatim
+- [ ] Identify patterns in rationalizations/failures
+
+**GREEN Phase:**
+- [ ] Name uses only letters, numbers, hyphens
+- [ ] YAML frontmatter with `name` and `description` fields
+- [ ] Description starts with "Use when..." — triggering conditions only
+- [ ] Description written in third person
+- [ ] Keywords throughout for search
+- [ ] Clear overview with core principle
+- [ ] Address specific baseline failures from RED phase
+- [ ] Run scenarios WITH skill — verify agents now comply
+
+**REFACTOR Phase:**
+- [ ] Identify NEW rationalizations from testing
+- [ ] Add explicit counters for discipline skills
+- [ ] Build rationalization table from all test iterations
+- [ ] Create red flags list
+- [ ] Re-test until bulletproof
+
+**Deployment:**
+- [ ] Skill file at `.claude/skills/mastermind/<name>.md`
+- [ ] Command file at `.claude/commands/mastermind/<name>.md`
+- [ ] Commit both files to git
+
+## The Bottom Line
+
+**Creating mastermind skills IS TDD for process documentation.**
+
+Same Iron Law: No skill without failing test first.
+Same cycle: RED (baseline) → GREEN (write skill) → REFACTOR (close loopholes).
+Same benefits: Better quality, fewer surprises, bulletproof results.

package/.claude/skills/mastermind/taskdev.md

@@ -0,0 +1,307 @@
+---
+name: mastermind-taskdev
+description: Execute implementation plans with independent tasks using fresh subagents per task, with two-stage review (spec compliance then code quality) after each.
+type: domain-skill
+default_mode: auto
+---
+
+# Mastermind Taskdev
+
+Execute a plan by dispatching a fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
+
+**Why subagents:** You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.
+
+**Core principle:** Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
+
+**Continuous execution:** Do not pause to check in with your human partner between tasks. Execute all tasks from the plan without stopping. The only reasons to stop are: BLOCKED status you cannot resolve, ambiguity that genuinely prevents progress, or all tasks complete. "Should I continue?" prompts and progress summaries waste their time — they asked you to execute the plan, so execute it.
+
+---
+
+## When to Use
+
+```dot
+digraph when_to_use {
+    "Have implementation plan?" [shape=diamond];
+    "Tasks mostly independent?" [shape=diamond];
+    "Stay in this session?" [shape=diamond];
+    "mastermind:taskdev" [shape=box];
+    "mastermind:execute" [shape=box];
+    "Manual execution or brainstorm first" [shape=box];
+
+    "Have implementation plan?" -> "Tasks mostly independent?" [label="yes"];
+    "Have implementation plan?" -> "Manual execution or brainstorm first" [label="no"];
+    "Tasks mostly independent?" -> "Stay in this session?" [label="yes"];
+    "Tasks mostly independent?" -> "Manual execution or brainstorm first" [label="no - tightly coupled"];
+    "Stay in this session?" -> "mastermind:taskdev" [label="yes"];
+    "Stay in this session?" -> "mastermind:execute" [label="no - parallel session"];
+}
+```
+
+**vs. mastermind:execute (parallel session):**
+- Same session (no context switch)
+- Fresh subagent per task (no context pollution)
+- Two-stage review after each task: spec compliance first, then code quality
+- Faster iteration (no human-in-loop between tasks)
+
+---
+
+## Inputs
+
+- `brain_context`: BRAIN CONTEXT block (loaded via _protocol.md brain load)
+- `plan_file`: absolute path to the plan `.md` file to execute
+- `params`: any additional flags or context
+- `mode`: auto | confirm
+
+---
+
+## The Process
+
+```dot
+digraph process {
+    rankdir=TB;
+
+    subgraph cluster_per_task {
+        label="Per Task";
+        "Dispatch implementer subagent (./implementer-prompt.md)" [shape=box];
+        "Implementer subagent asks questions?" [shape=diamond];
+        "Answer questions, provide context" [shape=box];
+        "Implementer subagent implements, tests, commits, self-reviews" [shape=box];
+        "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" [shape=box];
+        "Spec reviewer subagent confirms code matches spec?" [shape=diamond];
+        "Implementer subagent fixes spec gaps" [shape=box];
+        "Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" [shape=box];
+        "Code quality reviewer subagent approves?" [shape=diamond];
+        "Implementer subagent fixes quality issues" [shape=box];
+        "Mark task complete in TodoWrite" [shape=box];
+    }
+
+    "Read plan, extract all tasks with full text, note context, create TodoWrite" [shape=box];
+    "More tasks remain?" [shape=diamond];
+    "Dispatch final code reviewer subagent for entire implementation" [shape=box];
+    "Use mastermind:finish" [shape=box style=filled fillcolor=lightgreen];
+
+    "Read plan, extract all tasks with full text, note context, create TodoWrite" -> "Dispatch implementer subagent (./implementer-prompt.md)";
+    "Dispatch implementer subagent (./implementer-prompt.md)" -> "Implementer subagent asks questions?";
+    "Implementer subagent asks questions?" -> "Answer questions, provide context" [label="yes"];
+    "Answer questions, provide context" -> "Dispatch implementer subagent (./implementer-prompt.md)";
+    "Implementer subagent asks questions?" -> "Implementer subagent implements, tests, commits, self-reviews" [label="no"];
+    "Implementer subagent implements, tests, commits, self-reviews" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)";
+    "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" -> "Spec reviewer subagent confirms code matches spec?";
+    "Spec reviewer subagent confirms code matches spec?" -> "Implementer subagent fixes spec gaps" [label="no"];
+    "Implementer subagent fixes spec gaps" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" [label="re-review"];
+    "Spec reviewer subagent confirms code matches spec?" -> "Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" [label="yes"];
+    "Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" -> "Code quality reviewer subagent approves?";
+    "Code quality reviewer subagent approves?" -> "Implementer subagent fixes quality issues" [label="no"];
+    "Implementer subagent fixes quality issues" -> "Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" [label="re-review"];
+    "Code quality reviewer subagent approves?" -> "Mark task complete in TodoWrite" [label="yes"];
+    "Mark task complete in TodoWrite" -> "More tasks remain?";
+    "More tasks remain?" -> "Dispatch implementer subagent (./implementer-prompt.md)" [label="yes"];
+    "More tasks remain?" -> "Dispatch final code reviewer subagent for entire implementation" [label="no"];
+    "Dispatch final code reviewer subagent for entire implementation" -> "Use mastermind:finish";
+}
+```
+
+---
+
+## Model Selection
+
+Use the least powerful model that can handle each role to conserve cost and increase speed.
+
+**Mechanical implementation tasks** (isolated functions, clear specs, 1-2 files): use a fast, cheap model. Most implementation tasks are mechanical when the plan is well-specified.
+
+**Integration and judgment tasks** (multi-file coordination, pattern matching, debugging): use a standard model.
+
+**Architecture, design, and review tasks**: use the most capable available model.
+
+**Task complexity signals:**
+- Touches 1-2 files with a complete spec → cheap model
+- Touches multiple files with integration concerns → standard model
+- Requires design judgment or broad codebase understanding → most capable model
+
+---
+
+## Handling Implementer Status
+
+Implementer subagents report one of four statuses. Handle each appropriately:
+
+**DONE:** Proceed to spec compliance review.
+
+**DONE_WITH_CONCERNS:** The implementer completed the work but flagged doubts. Read the concerns before proceeding. If the concerns are about correctness or scope, address them before review. If they're observations (e.g., "this file is getting large"), note them and proceed to review.
+
+**NEEDS_CONTEXT:** The implementer needs information that wasn't provided. Provide the missing context and re-dispatch.
+
+**BLOCKED:** The implementer cannot complete the task. Assess the blocker:
+1. If it's a context problem, provide more context and re-dispatch with the same model
+2. If the task requires more reasoning, re-dispatch with a more capable model
+3. If the task is too large, break it into smaller pieces
+4. If the plan itself is wrong, escalate to the human
+
+**Never** ignore an escalation or force the same model to retry without changes. If the implementer said it's stuck, something needs to change.
+
+---
+
+## Prompt Templates
+
+- `./implementer-prompt.md` - Dispatch implementer subagent
+- `./spec-reviewer-prompt.md` - Dispatch spec compliance reviewer subagent
+- `./code-quality-reviewer-prompt.md` - Dispatch code quality reviewer subagent
+
+---
+
+## Example Workflow
+
+```
+You: I'm using mastermind:taskdev to execute this plan.
+
+[Read plan file once: docs/mastermind/plans/feature-plan.md]
+[Extract all 5 tasks with full text and context]
+[Create TodoWrite with all tasks]
+
+Task 1: Hook installation script
+
+[Get Task 1 text and context (already extracted)]
+[Dispatch implementation subagent with full task text + context]
+
+Implementer: "Before I begin - should the hook be installed at user or system level?"
+
+You: "User level (~/.config/monomind/hooks/)"
+
+Implementer: "Got it. Implementing now..."
+[Later] Implementer:
+  - Implemented install-hook command
+  - Added tests, 5/5 passing
+  - Self-review: Found I missed --force flag, added it
+  - Committed
+
+[Dispatch spec compliance reviewer]
+Spec reviewer: ✅ Spec compliant - all requirements met, nothing extra
+
+[Get git SHAs, dispatch code quality reviewer]
+Code reviewer: Strengths: Good test coverage, clean. Issues: None. Approved.
+
+[Mark Task 1 complete]
+
+Task 2: Recovery modes
+
+[Get Task 2 text and context (already extracted)]
+[Dispatch implementation subagent with full task text + context]
+
+Implementer: [No questions, proceeds]
+Implementer:
+  - Added verify/repair modes
+  - 8/8 tests passing
+  - Self-review: All good
+  - Committed
+
+[Dispatch spec compliance reviewer]
+Spec reviewer: ❌ Issues:
+  - Missing: Progress reporting (spec says "report every 100 items")
+  - Extra: Added --json flag (not requested)
+
+[Implementer fixes issues]
+Implementer: Removed --json flag, added progress reporting
+
+[Spec reviewer reviews again]
+Spec reviewer: ✅ Spec compliant now
+
+[Dispatch code quality reviewer]
+Code reviewer: Strengths: Solid. Issues (Important): Magic number (100)
+
+[Implementer fixes]
+Implementer: Extracted PROGRESS_INTERVAL constant
+
+[Code reviewer reviews again]
+Code reviewer: ✅ Approved
+
+[Mark Task 2 complete]
+
+...
+
+[After all tasks]
+[Dispatch final code-reviewer]
+Final reviewer: All requirements met, ready to merge
+
+Done!
+```
+
+---
+
+## Advantages
+
+**vs. Manual execution:**
+- Subagents follow TDD naturally
+- Fresh context per task (no confusion)
+- Parallel-safe (subagents don't interfere)
+- Subagent can ask questions (before AND during work)
+
+**vs. mastermind:execute:**
+- Same session (no handoff)
+- Continuous progress (no waiting)
+- Review checkpoints automatic
+
+**Efficiency gains:**
+- No file reading overhead (controller provides full text)
+- Controller curates exactly what context is needed
+- Subagent gets complete information upfront
+- Questions surfaced before work begins (not after)
+
+**Quality gates:**
+- Self-review catches issues before handoff
+- Two-stage review: spec compliance, then code quality
+- Review loops ensure fixes actually work
+- Spec compliance prevents over/under-building
+- Code quality ensures implementation is well-built
+
+**Cost:**
+- More subagent invocations (implementer + 2 reviewers per task)
+- Controller does more prep work (extracting all tasks upfront)
+- Review loops add iterations
+- But catches issues early (cheaper than debugging later)
+
+---
+
+## Red Flags
+
+**Never:**
+- Start implementation on main/master branch without explicit user consent
+- Skip reviews (spec compliance OR code quality)
+- Proceed with unfixed issues
+- Dispatch multiple implementation subagents in parallel (conflicts)
+- Make subagent read plan file (provide full text instead)
+- Skip scene-setting context (subagent needs to understand where task fits)
+- Ignore subagent questions (answer before letting them proceed)
+- Accept "close enough" on spec compliance (spec reviewer found issues = not done)
+- Skip review loops (reviewer found issues = implementer fixes = review again)
+- Let implementer self-review replace actual review (both are needed)
+- **Start code quality review before spec compliance is ✅** (wrong order)
+- Move to next task while either review has open issues
+
+**If subagent asks questions:**
+- Answer clearly and completely
+- Provide additional context if needed
+- Don't rush them into implementation
+
+**If reviewer finds issues:**
+- Implementer (same subagent) fixes them
+- Reviewer reviews again
+- Repeat until approved
+- Don't skip the re-review
+
+**If subagent fails task:**
+- Dispatch fix subagent with specific instructions
+- Don't try to fix manually (context pollution)
+
+---
+
+## Integration
+
+**Required workflow skills:**
+- `Skill("mastermind:plan")` - Creates the plan this skill executes
+- `Skill("mastermind:review")` - Code review template for reviewer subagents
+- `Skill("mastermind:finish")` - Complete development after all tasks done
+
+**Subagents should use:**
+- `Skill("mastermind:tdd")` - Subagents follow TDD for each task
+
+**Alternative workflow:**
+- `Skill("mastermind:execute")` - Use for parallel session instead of same-session execution