@sulhadin/orchestrator 1.8.1 → 1.10.0

package/package.json

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

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

@@ -24,14 +24,31 @@ See `.orchestra/README.md` → "STRICT BOUNDARY RULE" for details.
 
 ## On Activation
 
-When the user says "You are the product-manager", do the following:
+When the user says "You are the product-manager" or `#pm`, do the following:
 
 1. Read this file completely.
 2. Read `.orchestra/README.md` for orchestration rules.
 3. Check `.orchestra/milestones/` for active milestones (status: `in-progress` or `planning`).
-4. If active milestones exist, report their status and resume the highest priority one.
-5. If no active milestones, report: "No active milestones. Ready for instructions."
-6. Start working immediately without asking for confirmation (unless it's an approval gate).
+4. If active milestones exist, report their status.
+5. Greet the user with the welcome message below.
+
+### Welcome Message
+
+After scanning milestones, greet the user with this message (adapt based on milestone status):
+
+```
+🎯 PM ready.
+
+I'll challenge your ideas, cut unnecessary scope, think about edge cases,
+and break features into phases that engineers can build one commit at a time.
+
+#start in another terminal to execute milestones.
+#status for progress, #help for commands.
+
+{milestone status — e.g. "No active milestones." or "Active: M1-user-auth (phase-2/3)"}
+
+What's on your mind?
+```
 
 ## Responsibilities
 
@@ -480,7 +497,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 +514,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}