@sulhadin/orchestrator 4.0.1-beta → 4.0.1-beta.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/package.json +1 -1
  2. package/template/.claude-plugin/plugin.json +1 -1
  3. package/template/.orchestra/roles/product-manager.md +3 -0
  4. package/template/agents/lead.md +3 -6
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sulhadin/orchestrator",
3
- "version": "4.0.1-beta",
3
+ "version": "4.0.1-beta.0",
4
4
  "description": "AI Team Orchestration System — multi-role coordination for Claude Code",
5
5
  "bin": "bin/index.js",
6
6
  "scripts": {
package/template/.claude-plugin/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "orchestra",
3
3
  "description": "AI Team Orchestration — multi-role coordination with milestones, phases, and quality gates for Claude Code",
4
- "version": "4.0.1-beta",
4
+ "version": "4.0.1-beta.0",
5
5
  "author": {
6
6
  "name": "Sulhadin Öney"
7
7
  },
package/template/.orchestra/roles/product-manager.md CHANGED
@@ -16,6 +16,9 @@ one commit at a time. Push back and say no when it doesn't make sense.
16
16
  Can write: `.orchestra/milestones/*` (prd.md, milestone.md, grooming.md, phases)
17
17
  Cannot write: feature code, RFCs, architecture docs, review findings, system files
18
18
 
19
+ Do NOT ask for approval to write milestone files — they are your ownership scope.
20
+ Write directly, then inform the user what you changed.
21
+
19
22
  ## On Activation
20
23
 
21
24
  1. Read `.orchestra/config.yml` for pipeline settings
package/template/agents/lead.md CHANGED
@@ -81,12 +81,9 @@ phases with the same skills.
81
81
  6. Read `rfc.md` from milestone directory → rfc_content (read once per milestone, cache; skip if not exists)
82
82
  7. Derive team member identity from phase content:
83
83
  - Read the phase's `## Objective`, `## Scope`, and `skills:` list
84
- - Determine the right specialist identity for the job:
85
- - Scope targets `api/`, `server/`, `db/`, `migrations/`, `services/` + backend skills → **backend engineer**
86
- - Scope targets `app/`, `components/`, `pages/`, `styles/`, `ui/` + frontend skills → **frontend engineer**
87
- - Scope targets `infra/`, `.github/`, `docker`, `ci/`, `terraform/` + devops skills → **devops engineer**
88
- - Scope targets `rfc.md`, `architecture.md`, `adrs/` → **software architect**
89
- - Mixed or unclear → **fullstack engineer**
84
+ - Determine the right specialist identity for the job
85
+ (backend, frontend, devops, architect, or fullstack engineer)
86
+ based on the phase content — no hardcoded directory rules
90
87
  - Generate an identity block: who they are + domain priorities + the golden rule
91
88
 
92
89
  ### 3. Delegate to Phase Sub-Agent