claude-raid 0.2.7 → 0.2.9

package/template/.claude/skills/raid-teambuff/SKILL.md

@@ -21,14 +21,6 @@ The output is a structured report with binding rulings that the human approves.
 
 **Only the human.** No agent, not even the Wizard, can call a teambuff. The human says "teambuff" or invokes `/raid-teambuff` and it happens immediately.
 
-## Mode Behavior
-
-| Aspect | Full Raid | Skirmish | Scout |
-|--------|-----------|----------|-------|
-| Participants | Wizard + Warrior + Archer + Rogue | Wizard + 2 active agents | Wizard self-reflects alone |
-| Cross-criticism | All-vs-all, no one exempt | Between active agents + Wizard | N/A |
-| Rulings | Full synthesis from all reflections | Condensed synthesis | Wizard notes only |
-
 ## Process Flow
 
 ```dot
@@ -36,8 +28,8 @@ digraph teambuff {
   "Human triggers teambuff" -> "Wizard: HALT. Round table called.";
   "Wizard: HALT. Round table called." -> "Create teambuff-{NN}.md";
   "Create teambuff-{NN}.md" -> "Dispatch all agents: reflect";
-  "Dispatch all agents: reflect" -> "Agents write reflections (parallel)";
-  "Agents write reflections (parallel)" -> "Agents read each other's sections";
+  "Dispatch all agents: reflect" -> "Agents write reflections (sequential turns)";
+  "Agents write reflections (sequential turns)" -> "Agents read each other's sections";
   "Agents read each other's sections" -> "Agents write criticisms";
   "Agents write criticisms" -> "Wizard writes own reflection + criticism";
   "Wizard writes own reflection + criticism" -> "Wizard reads everything";
@@ -223,28 +215,18 @@ After any teambuff has occurred, the Wizard adds this to every round start:
 3. If current dispatch would violate a ruling, adjust before dispatching
 4. If an agent's work violates a ruling, flag it immediately
 
-## Skirmish Mode
-
-Same process, fewer agents. Only the active 2 agents + Wizard participate. Cross-criticism happens between whoever is present.
-
-## Scout Mode
-
-Wizard reflects alone. No dispatch, no cross-criticism. Wizard writes:
-- Own reflection (same structured sections)
-- Self-criticism
-- Proposed rulings (presented to human for approval)
 
 ## Known Dysfunction Patterns
 
 These are real patterns observed in production quests. When reflecting, look for these specifically — they are the most common sources of token waste and team friction.
 
-### 1. Ghost Rounds — Working After ROUND_COMPLETE
+### 1. Ghost Turns — Working After TURN_COMPLETE
 
-An agent signals `ROUND_COMPLETE:` but keeps working — cross-verifying, building on findings, challenging teammates. This burns tokens on work the Wizard didn't dispatch and creates confusion about what's "official" output vs unsanctioned noise.
+An agent signals `TURN_COMPLETE:` but keeps working — exploring tangents, building on findings, investigating further. This burns tokens on work the Wizard didn't dispatch and creates confusion about what's "official" output vs unsanctioned noise.
 
-**What to look for:** Did any agent produce work after their `ROUND_COMPLETE:` signal? Did agents treat ROUND_COMPLETE as "my initial research is done, now I'll cross-verify" instead of a full stop?
+**What to look for:** Did any agent produce work after their `TURN_COMPLETE:` signal? Did agents treat TURN_COMPLETE as "my initial research is done, now I'll keep going" instead of a full stop?
 
-**The fix:** `ROUND_COMPLETE:` means stop. Period. No "while I wait" tasks. The Wizard controls when the next round begins.
+**The fix:** `TURN_COMPLETE:` means stop. Period. No "while I wait" tasks. The Wizard controls when the next turn begins.
 
 ### 2. Wizard Presenting While Agents Are Active
 

package/template/.claude/skills/raid-verification/SKILL.md

@@ -19,12 +19,6 @@ NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
 
 If you haven't run the verification command THIS turn, you cannot claim it passes.
 
-## Mode Behavior
-
-- **Full Raid**: Triple verification — implementer + 2 challengers verify independently.
-- **Skirmish**: Double verification — implementer + 1 challenger.
-- **Scout**: Single verification + Wizard confirms.
-
 ## The Gate Function
 
 ```

package/template/.claude/skills/raid-wrap-up/SKILL.md

@@ -11,12 +11,6 @@ The quest ends. The bard sings the tale. The treasure is committed. The party re
 Do NOT write new code. This phase is about reporting, cleanup, PR creation, and archival. Agents are dismissed, not dispatched.
 </HARD-GATE>
 
-## Mode Behavior
-
-- **Full Raid**: Wizard writes full storyboard from all phase files. Full PR with narrative.
-- **Skirmish**: Wizard writes condensed storyboard. Standard PR.
-- **Scout**: Wizard writes brief summary. Quick PR.
-
 ## Process Flow
 
 ```dot
@@ -60,38 +54,45 @@ Create `{questDir}/phase-6-wrap-up.md` and write a phase-by-phase narrative:
 
 ```markdown
 # Phase 6: Wrap Up — Quest Storyboard
-## Quest: <quest name>
-## Mode: <mode>
+
+## Quest: [quest name]
+
+## References
+- PRD: `{questDir}/spoils/prd.md` (if exists)
+- Design: `{questDir}/spoils/design.md`
+- Design Evolution: `{questDir}/phases/phase-2-design.md`
+- Plan: `{questDir}/phases/phase-3-plan.md`
+- Tasks: `{questDir}/spoils/tasks/phase-3-plan-task-*.md`
+- Implementation: `{questDir}/phases/phase-4-implementation.md`
+- Review: `{questDir}/spoils/review.md` (if exists)
+- Review Evolution: `{questDir}/phases/phase-5-review.md` (if exists)
+
+---
 
 ### Phase 1: PRD — Forging the Scroll
-(if prd.md exists)
-- What requirements were established
-- Key decisions from research
+<!-- If prd.md exists. Summarize: what requirements were established,
+     key decisions, any surprising findings from exploration. 2-5 bullets. -->
 
 ### Phase 2: Design — Charting the Map
-- Architecture chosen and why
-- Key trade-offs resolved
-- Alternatives considered and rejected
+<!-- Who wrote the initial design (dice result). Key defend/concede moments.
+     Architecture chosen and main alternatives rejected.
+     Drift check result if PRD existed. 3-6 bullets. -->
 
-### Phase 3: Implementation Plan — Marshaling the Forces
-- Number of tasks, dependency structure
-- Risk areas identified
+### Phase 3: Plan — Marshaling the Forces
+<!-- Total task count, dependency structure highlights.
+     Key findings from plan review that changed the decomposition. 2-4 bullets. -->
 
 ### Phase 4: Implementation — Into the Fray
-- What was built
-- Challenges overcome
-- Test coverage highlights
+<!-- How tasks were divided (which agent, which domain).
+     Notable challenges overcome. Test count / coverage highlights. 3-5 bullets. -->
 
 ### Phase 5: Review — Inspecting the Treasure
-(if phase-5-review.md exists)
-- Findings pinned and resolved
-- Black cards (if any)
-- Fixes applied
-
-### Summary
-- Total phases completed
-- Key achievements
-- Known limitations
+<!-- If review ran. Findings count by severity.
+     Key fixes applied. Black cards if any. 2-5 bullets. -->
+
+### Quest Summary
+<!-- Total phases completed. Key achievements (what was built).
+     Known limitations (deferred items, accepted constraints). -->
 ```
 
 Read all prior phase files from the quest directory to build this narrative.