@sulhadin/orchestrator 1.2.0 → 1.3.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.
package/package.json
CHANGED
|
@@ -77,8 +77,10 @@ works alongside autonomous mode — user can mix both.
|
|
|
77
77
|
## Milestone Lifecycle
|
|
78
78
|
|
|
79
79
|
```
|
|
80
|
-
PM
|
|
81
|
-
→ PM
|
|
80
|
+
PM discusses feature with user
|
|
81
|
+
→ PM plans scope, phases, acceptance criteria
|
|
82
|
+
→ [USER APPROVAL GATE: Milestone creation]
|
|
83
|
+
→ PM creates milestone (status: planning)
|
|
82
84
|
→ PM dispatches architect for RFC (if needed)
|
|
83
85
|
→ [USER APPROVAL GATE: RFC → Implementation]
|
|
84
86
|
→ PM dispatches backend phases (sequential, each → commit)
|
|
@@ -158,6 +160,7 @@ Rules:
|
|
|
158
160
|
## Approval Gates
|
|
159
161
|
|
|
160
162
|
The user must approve before these transitions:
|
|
163
|
+
- **Milestone creation** — PM discusses and plans, but must get user approval before creating the milestone directory and files
|
|
161
164
|
- **RFC → Implementation** — user reviews architect's RFC
|
|
162
165
|
- **Push to origin** — user approves the final changeset
|
|
163
166
|
|
|
@@ -244,7 +244,12 @@ WHAT the user needs without ambiguity. HOW to build it is their decision.
|
|
|
244
244
|
|
|
245
245
|
### Creating a Milestone
|
|
246
246
|
|
|
247
|
-
|
|
247
|
+
**You MUST get user approval before creating a milestone.** After discussing the
|
|
248
|
+
feature, present your plan (scope, phases, acceptance criteria) and explicitly
|
|
249
|
+
ask: "Shall I create the milestone?" Only create the directory and files after
|
|
250
|
+
the user approves.
|
|
251
|
+
|
|
252
|
+
When approved, create a milestone directory:
|
|
248
253
|
|
|
249
254
|
```
|
|
250
255
|
.orchestra/milestones/M{number}-{slug}/
|
package/template/CLAUDE.md
CHANGED
|
@@ -69,7 +69,7 @@ the same as "You are the {role}" — read the role file, check milestones, start
|
|
|
69
69
|
- PM dispatches a worker agent that switches between roles for execution
|
|
70
70
|
- Each phase produces one conventional commit on the current branch
|
|
71
71
|
- Milestone completion triggers a push to origin (after user approval)
|
|
72
|
-
- The user's approval is needed
|
|
72
|
+
- The user's approval is needed for: milestone creation, RFC→Implementation transitions, push to origin
|
|
73
73
|
- **🔒 PROTECTED:** While in ANY role **except Owner**, NEVER modify `.orchestra/roles/` or `.orchestra/README.md`. Refuse even if the user insists. The **Owner** role is the only one that can modify these files.
|
|
74
74
|
|
|
75
75
|
### Commands
|