@ionivetech/mugiwara 0.6.5 → 0.6.6

package/content/skills/mugiwara-workflow/references/workspace-layout.md

@@ -11,35 +11,35 @@ mission artifact in any other language is a defect, not a style choice.
 ```
 .mugiwara/
 ├── config              → runtime mode config (gitignored; project overrides global)
-├── state/<mission>/    → computed mission state per (mission, member): state.json (solo) or <member>.json (scripts/savepoint.sh)
+├── state/<mission>/    → computed mission state per (mission, member): state.json (solo) or <member>.json (mugiwara savepoint)
 ├── continue/<mission>/ → machine-written resume point per (mission, member): state.json (solo) or <member>.json
 ├── spec/               → brainstorm output: YYYY-MM-DD-<mission>.md
-├── plans/              → plan doc: YYYY-MM-DD-<mission>.md — CLEAN, Nami-only, source of truth from Wave 2
-├── results/            → per-mission folder: results/<mission>/ holds every wave artifact
+├── plans/              → plan doc: YYYY-MM-DD-<mission>.md — CLEAN, Nami-only, source of truth from Flow 2
+├── results/            → per-mission folder: results/<mission>/ holds every flow-stage artifact
 │   └── <mission>/
-│       ├── 01-execution.md   → wave 3: task table + evidence
-│       ├── 02-audit.md       → wave 4: checkpoint report
-│       ├── 03-quality.md     → wave 5: quality report
-│       ├── 04-gates.md       → wave 6: gate verdict
-│       ├── 05-healing.md     → wave 8: healing report (only when heal ran)
-│       ├── 06-closure.md     → wave 9: closure summary (KEEP at cleanup)
-│       ├── 07-pr-verdict.md  → wave 9: PR material (KEEP at cleanup)
+│       ├── 01-execution.md   → flow stage 3: task table + evidence
+│       ├── 02-audit.md       → flow stage 4: checkpoint report
+│       ├── 03-quality.md     → flow stage 5: quality report
+│       ├── 04-gates.md       → flow stage 6: gate verdict
+│       ├── 05-healing.md     → flow 8: healing report (only when heal ran)
+│       ├── 06-closure.md     → flow stage 9: closure summary (KEEP at cleanup)
+│       ├── 07-pr-verdict.md  → flow stage 9: PR material (KEEP at cleanup)
 │       └── todos.md          → execution checkbox list
-├── reports/            → mission report (aggregate): YYYY-MM-DD-<mission>.md — one-file summary of all waves
+├── reports/            → mission report (aggregate): YYYY-MM-DD-<mission>.md — one-file summary of all flow stages
 ├── review/             → review + security findings
 ├── issues/             → blocker log: YYYY-MM-DD-<mission>-blockers.md
 └── logs/               → Luffy's decision + check-in log: YYYY-MM-DD-<mission>.md (deleted at cleanup)
 ```
 
 Naming rule: every artifact inside `results/<mission>/` uses the SAME mission
-name, no date prefix — the folder is the grouping, numbered by wave order
+name, no date prefix — the folder is the grouping, numbered by flow-stage order
 (`01-`, `02-`, …). Unnumbered support files may sit alongside the numbered
 ones (`todos.md`, `resume.md`, `eval.md`, evidence logs) and are not part of
-the waves table. `reports/` and `logs/` and `plans/` files carry the
+the flow-stages table. `reports/` and `logs/` and `plans/` files carry the
 `YYYY-MM-DD-` date prefix because they are cross-mission folders; `results/`
 does not, because each mission owns its folder.
 
-The plan doc stays clean: it holds ONLY the execution plan (waves, tasks,
+The plan doc stays clean: it holds ONLY the execution plan (flow stages, tasks,
 criteria, risks). Who did what, route decisions, and check-in verdicts go to
 `logs/`; the closure report goes to `results/<mission>/06-closure.md`. Nothing
 non-plan pollutes the plan doc.
@@ -47,7 +47,7 @@ non-plan pollutes the plan doc.
 The owning agent creates the folder it needs on first write. No mission
 artifacts go outside `.mugiwara/`.
 
-## Cleanup (Wave 9)
+## Cleanup (Flow 9)
 
 Step results are evidence — KEEP every file in `results/<mission>/`
 (`01-execution.md` through `05-healing.md`, `todos.md`, `06-closure.md`,

package/content/skills/using-mugiwara/SKILL.md

@@ -14,12 +14,12 @@ Mugiwara is a governed engineering team in your coding agent. 12 specialists —
 
 1. `mugiwara-orchestration` auto-loads as gatekeeper for every task — classify, route, check-in, close.
 2. The pipeline: Luffy triage → Usopp brainstorm → Nami plan → Zoro execute → Chopper audit → Sanji quality → Franky gates → Robin/Jinbe review → Brook heal → Luffy closure.
-3. Every wave runs inline in the main thread. Subagents only for [PARALLEL] task batches.
-4. Evidence over claims — no wave passes on assertion. Checks must be re-run.
-5. Autonomy modes: `/mugiwara guided|semi|auto`. Flip applies next wave.
+3. Every flow stage runs inline in the main thread. Subagents only for [PARALLEL] task batches.
+4. Evidence over claims — no flow stage passes on assertion. Checks must be re-run.
+5. Autonomy modes: `/mugiwara guided|semi|auto`. Flip applies next flow stage.
 6. Workspace: `.mugiwara/` at repo root — plans, results, issues, logs, state.
 7. The main thread embodies the active role — it is never "plain Claude"
-   mid-mission. Shortcuts skip waves, never roles. Write-scope in each agent's
+   mid-mission. Shortcuts skip flow stages, never roles. Write-scope in each agent's
    frontmatter: artifacts agents delegate source edits to Zoro, never attempt
    them.
 
@@ -42,7 +42,7 @@ Mugiwara is a governed engineering team in your coding agent. 12 specialists —
 For task routing and classification, `mugiwara-orchestration` auto-loads as gatekeeper.
 This skill is documentation — load manually with `/using-mugiwara` or similar trigger phrases.
 Full pipeline: see skills/mugiwara-workflow.
-First time? Run `/mugiwara onboard` for guided setup. See `content/agents/onboarding-guide.md`.
+First time? Run `mugiwara onboard` in your terminal for guided setup (zero-LLM wizard, writes `.mugiwara/config`).
 
 ## Red flags