@mstar-harness/opencode 0.6.15 → 0.6.16
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.
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: iteration-drive
|
|
3
|
+
description: Drive the active iteration to completion — run the PM Autonomous Execute loop (implement → QC → QA → Done) until all plans are Done, then optionally create PR to main
|
|
4
|
+
agent: project-manager
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Drive Iteration
|
|
8
|
+
|
|
9
|
+
Drive the active Morning Star iteration forward. Run the **Autonomous Execute driver** from `skills/pm/SKILL.md` (`§ Autonomous Execute driver`) to advance all non-`Done` plans to completion.
|
|
10
|
+
|
|
11
|
+
## Boot
|
|
12
|
+
|
|
13
|
+
1. `mstar-harness-core`
|
|
14
|
+
2. `mstar-roles` → `references/project-manager.md`
|
|
15
|
+
3. `skills/pm/SKILL.md` → focus on **§ When to activate autonomous Execute** and **§ Autonomous Execute driver**
|
|
16
|
+
4. `mstar-dispatch-gates` + host reference
|
|
17
|
+
5. `mstar-plan-artifacts`, `mstar-plan-conventions`, `mstar-branch-worktree`
|
|
18
|
+
|
|
19
|
+
## Precondition Gate
|
|
20
|
+
|
|
21
|
+
Check the three conditions from **§ When to activate autonomous Execute**:
|
|
22
|
+
|
|
23
|
+
1. `{HARNESS_DIR}/status.json` exists with at least one plan **not** `Done`
|
|
24
|
+
2. **Pre-implement gate = GO** (`plan` locked, tasks ready)
|
|
25
|
+
3. User intent is **continue Execute**
|
|
26
|
+
|
|
27
|
+
If any is **false** → stop. If Prepare is incomplete → tell the user to run `/iteration-start` first.
|
|
28
|
+
|
|
29
|
+
## Execute Loop
|
|
30
|
+
|
|
31
|
+
Follow **§ Autonomous Execute driver** from the PM skill exactly:
|
|
32
|
+
|
|
33
|
+
1. **Session todos** — set host todos for current `plan_id` + next gates
|
|
34
|
+
2. **Read backlog** — `status.json`, active plans, `primary_spec` / `spec_integration_branch`
|
|
35
|
+
3. **Checkout integration branch** — resolve or create from `status.json` metadata
|
|
36
|
+
4. **Per-plan loop** — for each non-`Done` plan:
|
|
37
|
+
- Create plan feature branch from integration branch
|
|
38
|
+
- Dispatch implement subagents (dispatch-first, no parent agent implementation)
|
|
39
|
+
- Update `status.json` + main plan after each Completion Report
|
|
40
|
+
- QC tri-review + QA per `mstar-review-qc`
|
|
41
|
+
- Merge plan branch → integration branch
|
|
42
|
+
- Move to next plan
|
|
43
|
+
5. Repeat until **all** plans in the iteration are `Done`
|
|
44
|
+
|
|
45
|
+
## Completion
|
|
46
|
+
|
|
47
|
+
When every plan is `Done` in `status.json`:
|
|
48
|
+
|
|
49
|
+
- Create a PR from `spec_integration_branch` to `main`
|
|
50
|
+
- Report a summary: plans completed, branch names, PR link
|