@sulhadin/orchestrator 1.8.0 → 1.9.0

package/package.json

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

package/template/.orchestra/README.md

@@ -158,6 +158,7 @@ Rules:
 - Breaking changes add `!` after type
 - Body explains WHY, not WHAT
 - Subject line ≤ 72 characters
+- **No `Co-Authored-By` trailers** — never add co-author lines to commit messages
 
 ---
 

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

@@ -47,11 +47,13 @@ For each milestone (in order: in-progress first, then planning):
 ⚙️ #backend ✅ phase-1 done (feat(db): add auth tables)
 
 ⚙️ #backend ▶ phase-2: API endpoints + tests...
-   ...
+   Read phase-2.md, implement, test, commit
+   Update phase-2.md result + context.md
 ⚙️ #backend ✅ phase-2 done (feat(auth): add login endpoint)
 
 🎨 #frontend ▶ phase-3: Login UI...
-   ...
+   Read phase-3.md, implement, test, commit
+   Update phase-3.md result + context.md
 🎨 #frontend ✅ phase-3 done (feat(auth): add login page)
 
 🔍 #reviewer ▶ reviewing unpushed commits...

package/template/.orchestra/roles/architect.md

@@ -354,7 +354,9 @@ After architecture is complete:
 
 2. **Update the milestone** — write architecture results into the `rfc.md` file in the relevant milestone directory.
 
-3. **Return result to PM** — in autonomous mode, the PM awaits the architect's result. The updated `rfc.md` serves as the handoff artifact.
+3. **Update `context.md`** — append what was done, decisions made, files touched.
+
+4. **Return result to PM** — in autonomous mode, the PM awaits the architect's result. The updated `rfc.md` serves as the handoff artifact.
 
 ---
 

package/template/.orchestra/roles/backend-engineer.md

@@ -171,6 +171,7 @@ Plan your commits by logical unit — NOT one giant commit.
 ### Step 6: Result & Handoff
 - Update the phase file's `## Result` section with what was implemented
 - Set the phase status to `done`
+- Update `context.md` — append what was done, decisions made, files touched
 - Return result to PM (PM awaits the result in autonomous mode)
 
 ---

package/template/.orchestra/roles/frontend-engineer.md

@@ -361,6 +361,7 @@ Write tests alongside implementation.
 ### Step 7: Complete Phase & Handoff
 - Update the phase file's `## Result` section with your implementation summary
 - Set the phase status to `done`
+- Update `context.md` — append what was done, decisions made, files touched
 - Return result to PM — PM will dispatch the next role (e.g., code reviewer)
 
 ---

package/template/.orchestra/roles/product-manager.md

@@ -480,7 +480,8 @@ variation, you MUST scan `.orchestra/milestones/` and produce the following repo
 2. Read each `milestone.md` for status and acceptance criteria
 3. Read `context.md` if exists — shows what the worker has completed and key decisions
 4. Read phase files for individual phase statuses
-5. Check git status for unpushed commits
+5. For each phase file, run `wc -c` to get character count, divide by 4 to estimate tokens
+6. Check git status for unpushed commits
 
 **Report format:**
 
@@ -496,11 +497,11 @@ variation, you MUST scan `.orchestra/milestones/` and produce the following repo
 
 ## Phase Details: {active milestone}
 
-| # | Role | Description | Status |
-|---|------|-------------|--------|
-| 1 | backend | DB schema + migrations | done |
-| 2 | backend | API endpoints + tests | in-progress |
-| 3 | frontend | Dashboard UI | pending |
+| # | Role | Description | Status | Tokens |
+|---|------|-------------|--------|--------|
+| 1 | backend | DB schema + migrations | done | ~{wc -c / 4} |
+| 2 | backend | API endpoints + tests | in-progress | ~{wc -c / 4} |
+| 3 | frontend | Dashboard UI | pending | ~{wc -c / 4} |
 
 ## Git Status
 - Branch: {current branch}