@sulhadin/orchestrator 1.7.0 → 1.8.0

package/package.json

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

package/template/.orchestra/README.md

@@ -85,11 +85,11 @@ PM discusses feature with user
   → PM plans scope, phases, acceptance criteria
   → [USER APPROVAL GATE: Milestone creation]
   → PM creates milestone (status: planning)
-  → PM dispatches architect: write RFC + validate grooming (phase breakdown, dependencies, scope)
+  → Worker activates #architect: writes RFC + validates grooming
   → [USER APPROVAL GATE: RFC + grooming validation → Implementation]
-  → PM dispatches backend phases (sequential, each → commit)
-  → PM dispatches frontend phases (sequential, each → commit)
-  → PM dispatches reviewer (reviews unpushed commits)
+  → Worker executes backend phases (sequential, each → commit)
+  → Worker executes frontend phases (sequential, each → commit)
+  → Worker activates #reviewer (reviews unpushed commits)
   → FIX cycle if changes-requested (one round, no re-review)
   → [USER APPROVAL GATE: Push to origin]
   → PM pushes, verifies acceptance criteria, closes milestone
@@ -177,7 +177,7 @@ All other transitions are automatic.
 Reviewer no longer needs task files. Review is based on **unpushed commits**.
 
 ```
-PM dispatches #reviewer via worker agent
+Worker activates #reviewer
   → Reviewer runs: git log origin/{branch}..HEAD
   → Reviewer runs: git diff origin/{branch}...HEAD
   → Reviewer applies full checklist (backend or frontend mode)
@@ -186,7 +186,7 @@ PM dispatches #reviewer via worker agent
 
 **If approved** → PM proceeds to push gate.
 
-**If changes-requested** → PM dispatches FIX to relevant role. Worker fixes
+**If changes-requested** → Worker switches to the relevant role, fixes
 and commits. Pipeline proceeds — **no re-review** (single review round).
 
 ---

package/template/.orchestra/agents/worker.md

@@ -76,9 +76,20 @@ For each milestone (in order: in-progress first, then planning):
    ✅ All milestones complete. Waiting for new work from PM.
 ```
 
-## Role Switching
+## Role Switching — Automatic, Based on Phase File
 
-Each phase file specifies a `role:` field. Activate that role for the phase:
+You switch roles **automatically** based on the `role:` field in each phase file.
+Nobody tells you which role to use — you read it from the phase file and activate
+the corresponding role, its rules, its ownership scope, and its engineering principles.
+
+```
+phase-1.md → role: backend-engineer  → you become #backend
+phase-2.md → role: backend-engineer  → you stay #backend
+phase-3.md → role: frontend-engineer → you switch to #frontend
+review     → always #reviewer
+```
+
+Role mapping:
 
 | Role prefix | Role | Icon |
 |-------------|------|------|
@@ -103,8 +114,20 @@ as a CONCERN in context.md and continue.
 
 ## Context Persistence — `context.md`
 
-**After every phase completion**, update `context.md` in the milestone directory.
-This file allows you to resume if the terminal is closed and reopened.
+Update `context.md` in the milestone directory at these moments:
+
+| When | What to write |
+|------|---------------|
+| **Phase starts** | Current phase name, objective, plan |
+| **Key decision made** | What was decided and why (e.g. "chose argon2 over bcrypt") |
+| **Files created/modified** | Which files were touched and why |
+| **Phase completes** | Commit message, result summary |
+| **Error occurs** | What failed, why, current state |
+| **User gives instruction** | What the user asked to change mid-phase |
+
+This ensures that if the terminal closes at ANY point — even mid-phase — the
+next `#start` can resume with full context. Don't wait until phase completion
+to update; write incrementally as you work.
 
 ### context.md Format
 
@@ -146,9 +169,9 @@ When `#start` is called and a milestone has `status: in-progress`:
 
 For each phase:
 
-1. **Print start status** — `{icon} #role ▶ phase-N: description...`
-2. **Read the phase file** — understand objective, scope, acceptance criteria
-3. **Activate the role** — follow its rules, principles, ownership scope
+1. **Read the phase file** — check `role:` field, objective, scope, acceptance criteria
+2. **Activate the role from `role:` field** — read the corresponding role file in `.orchestra/roles/`, follow its rules, principles, ownership scope
+3. **Print start status** — `{icon} #role ▶ phase-N: description...`
 4. **Implement** — write code, tests, following the role's engineering standards
 5. **Verify** — `npx tsc --noEmit`, run tests (if applicable)
 6. **Commit** — one conventional commit per phase on current branch

package/template/.orchestra/roles/code-reviewer.md

@@ -25,7 +25,7 @@ When the user says "You are the code-reviewer", do the following:
 1. Read this file completely.
 2. Read `.orchestra/README.md` for orchestration rules.
 3. Determine activation mode:
-   - **Autonomous mode:** PM dispatches reviewer via worker agent with context (milestone, branch, RFC). No queue to check — start reviewing immediately with the provided context.
+   - **Autonomous mode (#start):** Worker activates you automatically after all phases complete. Start reviewing immediately — context is already available from the milestone.
    - **Manual mode:** Check if there are unpushed commits on the current branch using `git log origin/{branch}..HEAD`. If commits exist, review them. If no unpushed commits, report: "No unpushed commits to review. Ready for instructions."
 4. Read the milestone's RFC for context on what was intended.
 5. Start reviewing immediately without asking for confirmation.

package/template/.orchestra/roles/owner.md

@@ -117,7 +117,7 @@ Fix:      Reviewer → changes-requested → Engineer fixes → proceed (no re-r
 - Current library versions only
 - No workarounds, no unused code, no `any` types
 - SOLID, KISS, YAGNI, DRY — enforced by reviewer
-- PM dispatches a single worker agent (all roles loaded, await-based)
+- Worker (#start) reads milestones, switches roles automatically per phase
 - Each phase → one commit, milestone done → push to origin
 
 ### Commands