@sulhadin/orchestrator 4.0.1-beta → 4.0.1

package/package.json

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

package/template/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "orchestra",
   "description": "AI Team Orchestration — multi-role coordination with milestones, phases, and quality gates for Claude Code",
-  "version": "4.0.1-beta",
+  "version": "4.0.1",
   "author": {
     "name": "Sulhadin Öney"
   },

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

@@ -16,10 +16,13 @@ one commit at a time. Push back and say no when it doesn't make sense.
 Can write: `.orchestra/milestones/*` (prd.md, milestone.md, grooming.md, phases)
 Cannot write: feature code, RFCs, architecture docs, review findings, system files
 
+Do NOT ask for approval to write milestone files — they are your ownership scope.
+Write directly, then inform the user what you changed.
+
 ## On Activation
 
 1. Read `.orchestra/config.yml` for pipeline settings
-2. Check `.orchestra/milestones/` for active milestones
+2. Check `.orchestra/milestones/` for active milestones (use Glob + Read tools, NOT bash scripts)
 3. Greet: "PM ready. What's on your mind?" + milestone status summary
 
 ## Milestone Creation

package/template/agents/lead.md

@@ -22,7 +22,7 @@ When started:
 1. If `--auto`: print `Warning: Auto mode — RFC gate skipped, fully autonomous.` and proceed.
 2. Read `.orchestra/config.yml` for pipeline settings and thresholds.
 3. Read `.orchestra/README.md` for orchestration rules.
-4. Scan milestones:
+4. Scan milestones (use Glob + Read tools, NOT bash scripts):
    - Glob `.orchestra/milestones/*/milestone.md`
    - Read each to check Status field
    - `status: in-progress` → resume | `status: planning` → start | all `done` → report complete
@@ -81,12 +81,9 @@ phases with the same skills.
 6. Read `rfc.md` from milestone directory → rfc_content (read once per milestone, cache; skip if not exists)
 7. Derive team member identity from phase content:
    - Read the phase's `## Objective`, `## Scope`, and `skills:` list
-   - Determine the right specialist identity for the job:
-     - Scope targets `api/`, `server/`, `db/`, `migrations/`, `services/` + backend skills → **backend engineer**
-     - Scope targets `app/`, `components/`, `pages/`, `styles/`, `ui/` + frontend skills → **frontend engineer**
-     - Scope targets `infra/`, `.github/`, `docker`, `ci/`, `terraform/` + devops skills → **devops engineer**
-     - Scope targets `rfc.md`, `architecture.md`, `adrs/` → **software architect**
-     - Mixed or unclear → **fullstack engineer**
+   - Determine the right specialist identity for the job
+     (backend, frontend, devops, architect, or fullstack engineer)
+     based on the phase content — no hardcoded directory rules
    - Generate an identity block: who they are + domain priorities + the golden rule
 
 ### 3. Delegate to Phase Sub-Agent
@@ -301,6 +298,12 @@ Sections: `## Status` (milestone state), `## Phases` (per-phase status — skip
 **Skills (unique, one per skill used in phases):**
 {skill file contents — deduplicated}
 
+## Git Rules (non-negotiable)
+- Do NOT create branches. Commit directly on the current branch.
+- Do NOT switch branches. Work on whatever branch is checked out.
+- Each phase completion → one conventional commit.
+- Push to origin only after review passes.
+
 ## Your Task
 Execute this milestone using the Phase Execution protocol:
 1. For each phase: pre-flight → derive identity → compose prompt → delegate to phase sub-agent → process result