@mstar-harness/opencode 0.6.1 → 0.6.2
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.
|
@@ -131,6 +131,10 @@ Before first implement dispatch (non-hotfix):
|
|
|
131
131
|
|
|
132
132
|
If any fail -> do not dispatch implement.
|
|
133
133
|
|
|
134
|
+
### Autonomous Execute (sessions entered via `/pm`)
|
|
135
|
+
|
|
136
|
+
After first **implement** dispatch with **GO**, continuously drive the **active iteration** backlog (possibly **multiple** `plan_id`s) through implement → InReview → Done. Do **not** pause for basic yes/no harness questions—use PM-recommended defaults and act. Process or gate uncertainty: **Read** the relevant `mstar-*` skill; **`Blocked`** only when rules still conflict or an irreversible scope choice is missing from plan/spec. Full rules: `skills/pm/SKILL.md` § **Autonomous Execute push**.
|
|
137
|
+
|
|
134
138
|
---
|
|
135
139
|
|
|
136
140
|
## Phase Routing Pre-Flight (Mandatory)
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: pm
|
|
3
|
-
description: "Force
|
|
3
|
+
description: "Force Morning Star PM mode (`/pm`): load `mstar-harness-core`, run as `project-manager`, and after Execute starts continuously drive one iteration's pending work (possibly multiple plans) with PM-default decisions—no basic yes/no prompts; resolve process rules from `mstar-*` skills. Read `mstar-review-qc` before any QC dispatch."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Project-Manager Force Entry (`/pm`)
|
|
@@ -23,10 +23,22 @@ If this session runs in Cursor **Plan mode**:
|
|
|
23
23
|
3. **CreatePlan** must dual-write to harness SSOT: fixed prefix todos **`harness-init`** → **`spec-register`** → **`mirror-plan`**, then implement todos. Do **not** skip bootstrap todos or mark implement todos done without per–task-ID **commit** + SSOT plan checkbox + evidence (`git log -1 --oneline`).
|
|
24
24
|
4. Before **SwitchMode → Agent**, verify mirror plan file and `status.json` `plan_id` registration per the bridge reference.
|
|
25
25
|
|
|
26
|
+
## Autonomous Execute push (iteration driver)
|
|
27
|
+
|
|
28
|
+
Once **Execute** has started (`plan` locked, `tasks` ready, **Pre-implement Gate Check** = `GO`):
|
|
29
|
+
|
|
30
|
+
1. **Drive the whole iteration backlog** — Treat the active **iteration** (see `{ITERATION_DIR}` / `status.json` `iteration_*` when present) as the unit of forward motion. **Continuously** advance **all** pending implement → InReview → Done work for that iteration before pausing for routine progress checks.
|
|
31
|
+
2. **Multiple plans, one push** — One iteration may reference **several** `{PLAN_DIR}` plans (`plan_id`s). Do **not** stop after closing a single plan if sibling plans in the same iteration still have open tasks, open residuals, or incomplete QC/QA waves. Use **`mstar-plan-artifacts`** + **`references/project-manager/plan-management.md`** for status/residual sync across plans.
|
|
32
|
+
3. **Default-forward, no basic prompts** — Do **not** ask the user binary or “should I continue?” questions for harness basics (next task, batch size, default route, parallel vs serial when the task board already allows it, standard QC tri-review, report-to-status rhythm). **Decide and dispatch** using PM judgment and the **recommended** option (same spirit as Prepare **`clarify`** in **`mstar-phase-gates`**: explore first, recommend, act).
|
|
33
|
+
4. **Process uncertainty → Read `mstar-*`, don't improvise** — Gate order, dispatch shape, branch/worktree, residuals, Superpowers stacking, host invoke rules: **Read** the authoritative topic skill (`mstar-phase-gates`, `mstar-dispatch-gates`, `mstar-branch-worktree`, `mstar-plan-conventions`, `mstar-plan-artifacts`, `mstar-review-qc`, `mstar-superpowers-align`, `mstar-host`) and follow it. Only **`Blocked`** or escalate when rules still conflict after reading, or when the user must choose an **irreversible** product/scope trade-off **not** already locked in plan/spec.
|
|
34
|
+
5. **Rhythm (unchanged)** — Per batch: dispatch → wait for Completion Report v2 → **status.json** + plan sync → next dispatch. Parallel batches still obey **`mstar-dispatch-gates`** (one turn, N invokes when required).
|
|
35
|
+
|
|
36
|
+
**Still ask the user** when: explicit user stop/redirect; true **`Blocked`** after harness lookup; missing secrets/credentials; or a high-impact ambiguity that **cannot** be resolved from repo/spec/plan and would change acceptance materially.
|
|
37
|
+
|
|
26
38
|
## Operating baseline
|
|
27
39
|
|
|
28
40
|
- Prefer **`specify → clarify → plan → tasks → delegate`** (align with `mstar-phase-gates`; do not skip `specify`).
|
|
29
|
-
-
|
|
41
|
+
- After Execute starts, follow **Autonomous Execute push** above — coordinate and **keep dispatching** until the iteration backlog is done or legitimately **`Blocked`**.
|
|
30
42
|
- Before dispatching any QC task, read `mstar-review-qc` (and relevant references) in the current round.
|
|
31
43
|
- Require evidence before completion claims.
|
|
32
44
|
- Treat `mstar-harness-core` as SSOT for gates, routing, and delivery loop.
|