@uoyo/mvtt 2.0.0 → 2.1.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 (61) hide show
  1. package/dist/fs/materialize.d.ts.map +1 -1
  2. package/dist/fs/materialize.js +3 -2
  3. package/dist/fs/materialize.js.map +1 -1
  4. package/dist/scripts/epic-update.cjs +181 -206
  5. package/dist/scripts/epic-update.md +57 -0
  6. package/dist/scripts/plan-update.cjs +203 -215
  7. package/dist/scripts/plan-update.md +59 -0
  8. package/dist/scripts/session-update.cjs +185 -209
  9. package/install-manifest.yaml +4 -0
  10. package/package.json +1 -1
  11. package/sources/defaults/config.yaml +5 -0
  12. package/sources/scripts/epic-update.js +3 -21
  13. package/sources/scripts/epic-update.md +57 -0
  14. package/sources/scripts/plan-update.js +30 -20
  15. package/sources/scripts/plan-update.md +59 -0
  16. package/sources/scripts/session-update.js +7 -23
  17. package/sources/sections/activation-load-config.md +7 -10
  18. package/sources/sections/activation-load-context.md +15 -25
  19. package/sources/sections/activation-preflight.md +1 -1
  20. package/sources/sections/footer-next-steps.md +1 -1
  21. package/sources/sections/language-constraint.md +3 -18
  22. package/sources/sections/output-format-constraint.md +6 -9
  23. package/sources/sections/script-usage-rule.md +32 -0
  24. package/sources/sections/session-update.md +24 -110
  25. package/sources/skills/mvt-analyze/business.md +1 -1
  26. package/sources/skills/mvt-analyze/manifest.yaml +7 -7
  27. package/sources/skills/mvt-analyze-code/manifest.yaml +7 -7
  28. package/sources/skills/mvt-cleanup/business.md +9 -0
  29. package/sources/skills/mvt-cleanup/manifest.yaml +6 -6
  30. package/sources/skills/mvt-config/business.md +1 -0
  31. package/sources/skills/mvt-config/manifest.yaml +1 -0
  32. package/sources/skills/mvt-decompose/business.md +18 -9
  33. package/sources/skills/mvt-decompose/manifest.yaml +7 -7
  34. package/sources/skills/mvt-design/business.md +34 -43
  35. package/sources/skills/mvt-design/manifest.yaml +7 -7
  36. package/sources/skills/mvt-fix/manifest.yaml +6 -6
  37. package/sources/skills/mvt-help/business.md +19 -9
  38. package/sources/skills/mvt-help/manifest.yaml +3 -14
  39. package/sources/skills/mvt-implement/business.md +27 -34
  40. package/sources/skills/mvt-implement/manifest.yaml +8 -14
  41. package/sources/skills/mvt-init/manifest.yaml +6 -6
  42. package/sources/skills/mvt-plan-dev/business.md +12 -2
  43. package/sources/skills/mvt-plan-dev/manifest.yaml +7 -7
  44. package/sources/skills/mvt-resume/manifest.yaml +3 -3
  45. package/sources/skills/mvt-review/business.md +3 -9
  46. package/sources/skills/mvt-review/manifest.yaml +7 -7
  47. package/sources/skills/mvt-status/business.md +2 -12
  48. package/sources/skills/mvt-status/manifest.yaml +3 -3
  49. package/sources/skills/mvt-sync-context/business.md +1 -1
  50. package/sources/skills/mvt-sync-context/manifest.yaml +6 -6
  51. package/sources/skills/mvt-test/business.md +2 -10
  52. package/sources/skills/mvt-test/manifest.yaml +7 -7
  53. package/sources/skills/mvt-update-plan/business.md +12 -27
  54. package/sources/skills/mvt-update-plan/manifest.yaml +12 -6
  55. package/sources/templates/analyze-output/body.md +41 -0
  56. package/sources/templates/decompose-output/body.md +36 -0
  57. package/sources/templates/design-output/body.md +48 -0
  58. package/sources/templates/implement-output/body.md +48 -3
  59. package/sources/templates/project-context/body.md +45 -0
  60. package/sources/templates/review-output/body.md +59 -0
  61. package/sources/templates/test-output/body.md +72 -0
@@ -0,0 +1,57 @@
1
+ # Epic Update Script — Full Reference
2
+
3
+ > **This file is the authoritative usage reference for `epic-update.cjs`.**
4
+ > Read this file before calling the script. Do NOT read the `.cjs` or `.js` source to learn flag names or semantics.
5
+
6
+ The script has five modes — use exactly one mode per invocation:
7
+
8
+ ## Commands
9
+
10
+ ```bash
11
+ # Mode 1 — Complete the current child and advance to the next sub-change
12
+ node .ai-agents/scripts/epic-update.cjs --epic <epic_path> --complete-child <change_id>
13
+
14
+ # Mode 2 — Set a child's status without advancing current_change
15
+ node .ai-agents/scripts/epic-update.cjs --epic <epic_path> --set-child-status <change_id> --child-status <active|pending|done|abandoned>
16
+
17
+ # Mode 3 — Switch the active child to a different one (reorder)
18
+ node .ai-agents/scripts/epic-update.cjs --epic <epic_path> --switch-active <change_id>
19
+
20
+ # Mode 4 — Add one or more children to an existing epic
21
+ node .ai-agents/scripts/epic-update.cjs --epic <epic_path> \
22
+ --add-child <id> --child-title "<title>" --child-scope "<scope>" [--child-depends-on "dep1,dep2"] \
23
+ [--add-child <id2> --child-title "<title2>" --child-scope "<scope2>" ...]
24
+
25
+ # Mode 5 — Validate an epic.yaml (read-only, no write)
26
+ node .ai-agents/scripts/epic-update.cjs --validate <epic_path>
27
+ ```
28
+
29
+ ## Argument values
30
+
31
+ | Argument | Value source | Example |
32
+ |----------|-------------|---------|
33
+ | `--epic` | `active_epic.epic_path` resolved from session.yaml | `".ai-agents/workspace/artifacts/epic-20260608-ecommerce-platform/epic.yaml"` |
34
+ | `--complete-child` | `active_change.id` of the child whose plan is fully done | `20260608-sub` |
35
+ | `--set-child-status` | target child `change_id` to re-status | `20260608-sub` |
36
+ | `--child-status` | new status (with `--set-child-status`): `active` / `pending` / `done` / `abandoned` | `done` |
37
+ | `--switch-active` | target child `change_id` to make the active one | `20260609-sub2` |
38
+ | `--add-child` | new child id (repeatable for multiple children in one invocation) | `20260620-sub3` |
39
+ | `--child-title` | title for the child added by the preceding `--add-child` | `"Cart"` |
40
+ | `--child-scope` | scope description for the child added by the preceding `--add-child` | `"Shopping cart CRUD and checkout flow"` |
41
+ | `--child-depends-on` | optional; comma-separated prerequisite child `change_id` values | `"20260608-sub"` |
42
+ | `--validate` | path to an `epic.yaml` to validate (read-only) | same as `--epic` |
43
+
44
+ ## Parameter semantics
45
+
46
+ | Argument | When to use | Effect on `epic.yaml` |
47
+ |----------|-------------|------------------------|
48
+ | `--complete-child` | A child change's plan is fully done and the epic should advance | Sets the child `status: done`, advances `current_change` to the next `pending` child whose `depends_on` are all `done` (DAG-based). |
49
+ | `--set-child-status` + `--child-status` | Mark a child `done` or `abandoned` without advancing `current_change` (e.g. defer mode) | Sets the child's status only; `current_change` unchanged. |
50
+ | `--switch-active` | Reorder to a different child (dependencies permitting) | Sets the target child `active`, others `pending`, updates `current_change`. Rejects if the target's `depends_on` have unfinished prerequisites. |
51
+ | `--add-child` (+ `--child-title` / `--child-scope` / `--child-depends-on`) | Append one or more children to an existing epic | Adds entries to `children[]`; validates id uniqueness + DAG; defaults `project` to the sole project name when single-project. |
52
+ | `--validate` | Verify `epic.yaml` integrity (e.g. after `/mvt-decompose` writes it) | Read-only check; no write. Reports DAG/structure errors on stderr. |
53
+
54
+ ## Output interpretation
55
+
56
+ - **Exit 0**: success. stdout is a single-line JSON object (mirrors `plan-update.cjs` protocol). Use the fields directly to render output. The file is already written — do NOT read it back to verify.
57
+ - **Exit 1**: failure. stderr carries a plain-text error (unknown mode, child not found, dependency unsatisfied, validation failure, parse/write error). The file was **not** modified. Report the error to the user and do not fabricate a success summary.