@sulhadin/orchestrator 3.0.0-beta.14 → 3.0.0-beta.15

package/README.md

@@ -62,6 +62,8 @@ PM challenges scope, creates M1-user-auth with 3 phases
 | `/orchestra start --auto` | Fully autonomous — warns once, then auto-push |
 | `/orchestra hotfix {desc}` | Ultra-fast fix: implement → verify → commit → push |
 | `/orchestra status` | Milestone status report (PM only) |
+| `/orchestra verifier [N]` | Verify milestones match PRD/RFC requirements (PM only) |
+| `/orchestra rewind [N]` | Review execution history: decisions, metrics, insights (PM only) |
 | `/orchestra blueprint {name}` | Generate milestones from template |
 | `/orchestra blueprint add` | Save current work as reusable template |
 | `/orchestra create-role` | Create a new role interactively (Orchestrator only) |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sulhadin/orchestrator",
-  "version": "3.0.0-beta.14",
+  "version": "3.0.0-beta.15",
   "description": "AI Team Orchestration System — multi-role coordination for Claude Code",
   "bin": "bin/index.js",
   "scripts": {

package/template/.claude/agents/conductor.md

@@ -221,13 +221,8 @@ Behavior after milestone completion depends on `pipeline.milestone_isolation`:
 ### Inline Mode (default)
 
 After push and retro:
-1. Clear context.md: remove `## Status`, `## Phases`, `## Decisions`, `## Metrics` sections, keep only `## Codebase Map`
-2. **STOP.** Print: "Milestone {id} complete and pushed. Run `/compact` then `/orchestra start` for next milestone."
-3. Do NOT loop to next milestone — user manages context manually.
-
-**Why stop?** Conductor accumulates ~5-8k tokens per milestone from phase
-results, review cycles, and commit logs. In inline mode, the user controls
-when to compact and restart, keeping quality high across milestones.
+1. **STOP.** Print: "Milestone {id} complete and pushed."
+2. Do NOT loop to next milestone.
 
 ### Agent Mode
 
@@ -367,7 +362,7 @@ pipeline: {quick | standard | full}
 - **Phase failed:** Set status to `failed`, add error summary and last-error
 - **Decisions:** Append key decisions from sub-agent's `notes` field — only non-obvious choices that affect later phases
 - **Metrics:** Record approximate phase duration and verification_retries from sub-agent result
-- **Milestone complete (inline mode):** Clear all sections except `## Codebase Map`
+- **Milestone complete:** Retro is written to knowledge.md (see Milestone Completion)
 
 ### On Resume
 

package/template/.claude/commands/orchestra/help.md

@@ -11,6 +11,8 @@ COMMANDS:
   /orchestra start --auto    Fully autonomous (warns once, then auto-push)
   /orchestra hotfix {desc}   Ultra-fast fix: implement → verify → commit → push
   /orchestra status          Milestone status report (PM only)
+  /orchestra verifier [N]    Verify milestones match requirements (PM only)
+  /orchestra rewind [N]      Review milestone execution history (PM only)
   /orchestra help            Show this help
   /orchestra blueprint {name}  Generate milestones from template (PM only)
   /orchestra blueprint add   Save current work as blueprint (PM only)

package/template/.claude/commands/orchestra/rewind.md

@@ -0,0 +1,60 @@
+Review milestone execution history for actionable insights. PM role only.
+
+**Usage:**
+- `/orchestra rewind` — rewind all `done` milestones
+- `/orchestra rewind 1,2,3` — rewind only specified milestone numbers
+
+1. Read `.orchestra/roles/product-manager.md` to activate PM.
+2. Scan `.orchestra/milestones/` — collect milestones to review:
+   - No arguments: all milestones with `status: done`
+   - With numbers: only milestones matching those numbers (e.g., `1` matches `M1-*`)
+3. For each milestone, read execution artifacts:
+   - `context.md` — structured sections:
+     - `## Decisions` — key choices made during implementation
+     - `## Metrics` — phase duration and verification retries
+     - `## Phases` — status, commits, errors per phase
+   - `knowledge.md` — retro entry for this milestone
+   - `grooming.md` — original scope vs what actually happened
+   - Review verdict and comments (from context.md or git log)
+4. Extract and present — focus on **what the user needs to know**, not execution mechanics:
+
+```
+## Rewind: M1-user-auth
+
+### Key Decisions Made During Execution
+- phase-1: Used Stripe SDK v4 instead of raw API (architect RFC recommendation)
+- phase-2: Split webhook handler into separate file for testability
+- phase-3: Chose CSS modules over Tailwind (frontend preference)
+
+### Performance
+- Total phases: 5 | Completed: 5 | Failed: 0
+- Longest phase: phase-3 (~12min) — complex UI with form validation
+- Verification retries: 3 total (phase-2: 2, phase-4: 1)
+- Stuck: No
+
+### Review Findings
+- Verdict: approved-with-comments
+- Comments:
+  - "Consider adding index on user_email for login query" (non-blocking)
+  - "Error messages expose internal details" (non-blocking, logged)
+
+### Scope Changes
+- Original grooming planned 4 phases, executed 5 (phase-3 was split during implementation)
+- phase-2 scope expanded: webhook handler was not in original PRD, added during RFC
+
+### Unresolved Items
+- 🔧 DB index on user_email — reviewer flagged, not addressed
+- 🔧 Error message sanitization — reviewer flagged, not addressed
+- 🔧 phase-2 workaround: hardcoded timeout — flagged as tech debt in Decisions
+
+### What We Learned
+- 📝 Webhook handler pattern — reusable for future integrations
+- ⏱️ Form validation phases consistently slow — consider a form-validation skill
+- 💡 Splitting phase-3 mid-execution worked well — complex UI benefits from smaller phases
+```
+
+5. After all milestones, present a cross-milestone summary:
+   - **Unresolved items** — review comments and flagged workarounds never addressed, across all milestones
+   - **Recurring patterns** — same review comments, same slow phase types, same failure modes
+   - **Skill gaps** — missing skills that would have helped
+   - **Strategic suggestions** — new skills to create, process improvements, items to fix in upcoming work

package/template/.claude/commands/orchestra/verifier.md

@@ -0,0 +1,52 @@
+Verify that implemented milestones match their requirements. PM role only.
+
+**Usage:**
+- `/orchestra verifier` — verify all `done` milestones
+- `/orchestra verifier 1,2,3` — verify only specified milestone numbers
+
+1. Read `.orchestra/roles/product-manager.md` to activate PM.
+2. Scan `.orchestra/milestones/` — collect milestones to verify:
+   - No arguments: all milestones with `status: done`
+   - With numbers: only milestones matching those numbers (e.g., `1` matches `M1-*`)
+3. For each milestone, read:
+   - `prd.md` — product requirements and acceptance criteria
+   - `rfc.md` — technical design decisions (if exists)
+   - `milestone.md` — summary and acceptance criteria
+   - `grooming.md` — scope decisions and phase breakdown
+   - All `phases/*.md` — phase acceptance criteria
+4. For each milestone, read execution context:
+   - `context.md` — `## Decisions` section (why specific approaches were chosen)
+   - `context.md` — `## Phases` section (which phases completed, which failed)
+5. For each milestone, read the actual implementation:
+   - Run `git log --oneline` filtered to commits from that milestone's phases
+   - Run `git diff` for those commits to see what changed
+   - Read the current state of modified files — diff shows changes, but current code shows completeness
+6. Compare requirements vs implementation. For each requirement/acceptance criterion:
+   - **met** — implementation satisfies the requirement
+   - **partial** — partially implemented, missing aspects noted
+   - **missed** — not implemented at all
+   - **deviated** — implemented differently than specified
+6. Report:
+
+```
+## Verification: M1-user-auth
+
+### Requirements Coverage
+- ✅ met: JWT authentication endpoint (phase-1, commit abc123)
+- ⚠️ partial: Rate limiting — implemented but no Redis backing (phase-2)
+- ❌ missed: Password reset flow — not in any commit
+- 🔀 deviated: Token refresh — RFC said rotating tokens, implemented static expiry
+
+### Summary
+4 requirements: 1 met, 1 partial, 1 missed, 1 deviated
+
+### Severity
+- 🔴 critical: Password reset flow missing (core auth feature)
+- 🟡 moderate: Rate limiting without Redis (works but won't scale)
+- 🟡 moderate: Token refresh deviation (security concern)
+```
+
+8. After reporting all milestones, if there are critical or moderate gaps:
+   - List gaps grouped by severity
+   - Suggest: "Use `/orchestra pm` to plan fix milestones for these gaps."
+   - Do NOT create milestones directly — PM decides scope and priority

package/template/.orchestra/README.md

@@ -386,7 +386,7 @@ sequenceDiagram
     C->>C: reviewer → approved
     C->>C: Push → M1 done
 
-    Note over C: STOP. "Run /compact then /orchestra start"
+    Note over C: STOP. "Run /compact or /clear then /orchestra start"
 ```
 
 ### 3. Conductor Execution Loop (Agent Mode)