@sulhadin/orchestrator 1.15.2 → 1.15.4

package/package.json

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

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

@@ -27,10 +27,13 @@ When the user types `#start` or `#start --auto`:
    - At each phase: read `.orchestra/roles/{role-from-phase}.md` for the active role only
    - When switching roles between phases: read the new role file, previous role context is no longer needed
    - Also read `.orchestra/knowledge.md` once at milestone start (if it exists)
-4. Scan `.orchestra/milestones/` for work:
+4. Scan `.orchestra/milestones/` for work — **you MUST list ALL directories** using `ls` or glob:
+   - Run `ls .orchestra/milestones/` to get every milestone directory (do NOT rely on memory)
+   - Read `milestone.md` in EACH directory to check its `Status` field
    - Find milestones with `status: in-progress` → resume from last incomplete phase
-   - If none, find milestones with `status: planning` → start from the beginning
-   - If none, report: "✅ All milestones complete. Waiting for new work from PM."
+   - If none in-progress, find milestones with `status: planning` → start from the beginning
+   - Only if ALL milestones are `status: done`, report: "✅ All milestones complete. Waiting for new work from PM."
+   - **NEVER assume you know all milestones** — always list the directory fresh. PM may have created new ones.
 5. Begin the execution loop
 
 ## Execution Loop

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

@@ -330,6 +330,15 @@ When approved, create a milestone directory:
     └── ...
 ```
 
+**Pre-flight checklist — BEFORE telling user the milestone is ready:**
+1. Every phase has `role:` set → correct?
+2. Every phase has `skills:` reviewed → not left empty by default? (`#help skills` if unsure)
+3. Every phase has clear acceptance criteria → testable, not vague?
+4. `milestone.md` has `Complexity:` set → quick/standard/full?
+5. Phase order makes sense → backend before frontend, dependencies respected?
+
+Do NOT announce the milestone as ready until all 5 checks pass.
+
 **Before grooming phases**, check `.orchestra/knowledge.md` (if it exists):
 - Read **Active Knowledge** for recent lessons and patterns
 - Read **Archive** for broader historical context when planning similar features
@@ -388,7 +397,7 @@ Choose based on **risk**, not effort:
 role: backend-engineer | frontend-engineer | architect
 status: pending | in-progress | done | failed
 order: 1
-skills: []          # optional — e.g. [auth-setup, crud-api, deployment]
+skills: []          # REVIEW THIS — run #help skills, assign relevant ones. Empty only if none apply.
 depends_on: []      # optional — e.g. [phase-1] — empty = no dependency, can run in parallel
 ---