@uoyo/mvtt 2.0.0-beta.1 → 2.0.0-beta.3

package/sources/skills/mvt-review/manifest.yaml

@@ -1,87 +1,108 @@
-name: mvt-review
-output: .claude/skills/mvt-review/SKILL.md
-
-frontmatter:
-  name: mvt-review
-  description: "Perform code review for quality, standards compliance, and best practices. This skill should be used when user wants code reviewed, quality checked, or to identify issues before merging."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Review
-
-      ## Purpose
-
-      Review code for quality, standards compliance, and best practices. Identify issues by severity, suggest improvements, and ensure architecture compliance.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Reviewer
-      role_desc: "a Code Quality Guardian"
-      decision_rules:
-        - rule: "Critical issue found (security, data loss, crash) -> Mark as CRITICAL, require fix before merge"
-        - rule: "Layer violation found -> Flag for Architect, suggest `/mvt-design`"
-        - rule: "Minor style issue -> Note as suggestion, don't block"
-        - rule: "Subjective preference -> Mark as \"non-blocking\" optional improvement"
-        - rule: "Good code pattern found -> Highlight positively"
-        - rule: "Bug found -> Document with reproduction steps, suggest `/mvt-fix`"
-        - rule: "Insufficient test coverage -> Recommend specific scenarios, suggest `/mvt-test`"
-      boundaries:
-        - scope: "fix code directly"
-          skill: "/mvt-fix"
-        - scope: "make architecture decisions"
-          skill: "/mvt-design"
-        - scope: "modify source code"
-          skill: "(This is a read-only review)"
-
-  - type: inline
-    content: |
-      ## Aspect Options
-
-      | Aspect | Focus Areas |
-      |--------|-------------|
-      | `architecture` | Layer compliance, module boundaries, dependency direction |
-      | `security` | Input validation, injection prevention, authentication |
-      | `performance` | N+1 queries, memory leaks, caching |
-      | `style` | Naming conventions, formatting, documentation |
-
-      Usage: `/mvt-review` or `/mvt-review --aspect {type}`
-
-  - type: shared
-    source: sections/activation-load-config.md
-
-  - type: shared
-    source: sections/output-language-constraint.md
-
-  - type: shared
-    source: sections/activation-preflight.md
-    params:
-      checks:
-        - order: "1"
-          field: "session.initialized_at"
-          level: "WARN"
-          message: "Session not initialized. Run `/mvt-init` first."
-        - order: "2"
-          field: "no code to review"
-          level: "WARN"
-          message: "No code to review. Run `/mvt-implement` first or specify files."
-
-  - type: file
-    source: ./business.md
-
-  - type: inline
-    content: |
-      ## Artifact Structure
-      Read the document structure template from: `.ai-agents/skills/_templates/review-output.md`
-      If a custom version exists at `.ai-agents/skills/_templates/custom/review-output.md`, use the custom version instead.
-      The template defines section headings only. Generate content for each section based on review results.
-      Write the artifact to: `.ai-agents/workspace/artifacts/{change-id}/review.md`
-
-  - type: shared
-    source: sections/session-update.md
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-review
+name: mvt-review
+output: .claude/skills/mvt-review/SKILL.md
+
+frontmatter:
+  name: mvt-review
+  description: "Perform code review for quality, standards compliance, and best practices. This skill should be used when user wants code reviewed, quality checked, or to identify issues before merging."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Review
+
+      ## Purpose
+
+      Review code for quality, standards compliance, and best practices. Identify issues by severity, suggest improvements, and ensure architecture compliance.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Reviewer
+      role_desc: "a Code Quality Guardian"
+      decision_rules:
+        - rule: "Critical issue found (security, data loss, crash) -> Mark as CRITICAL, require fix before merge"
+        - rule: "Layer violation found -> Flag for Architect, suggest `/mvt-design`"
+        - rule: "Minor style issue -> Note as suggestion, don't block"
+        - rule: "Subjective preference -> Mark as \"non-blocking\" optional improvement"
+        - rule: "Good code pattern found -> Highlight positively"
+        - rule: "Bug found -> Document with reproduction steps, suggest `/mvt-fix`"
+        - rule: "Insufficient test coverage -> Recommend specific scenarios, suggest `/mvt-test`"
+      boundaries:
+        - scope: "fix code directly"
+          skill: "/mvt-fix"
+        - scope: "make architecture decisions"
+          skill: "/mvt-design"
+        - scope: "modify source code"
+          skill: "(This is a read-only review)"
+
+  - type: inline
+    content: |
+      ## Aspect Options
+
+      | Aspect | Focus Areas |
+      |--------|-------------|
+      | `architecture` | Layer compliance, module boundaries, dependency direction |
+      | `security` | Input validation, injection prevention, authentication |
+      | `performance` | N+1 queries, memory leaks, caching |
+      | `style` | Naming conventions, formatting, documentation |
+
+      Usage: `/mvt-review` or `/mvt-review --aspect {type}`
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - ".ai-agents/workspace/artifacts/{active_change.id}/analysis.md -- Requirements analysis"
+        - ".ai-agents/workspace/artifacts/{active_change.id}/design.md -- Architecture design"
+        - ".ai-agents/workspace/artifacts/{active_change.id}/implementation.md -- Implementation record"
+
+  - type: shared
+    source: sections/activation-load-config.md
+
+  - type: shared
+    source: sections/output-language-constraint.md
+
+  - type: shared
+    source: sections/activation-preflight.md
+    params:
+      checks:
+        - order: "1"
+          field: "session.initialized_at"
+          level: "WARN"
+          message: "Session not initialized. Run `/mvt-init` first."
+        - order: "2"
+          field: "review target (user args, implementation.md, or git diff)"
+          level: "WARN"
+          message: "No code to review. Run `/mvt-implement` first or specify files."
+
+  - type: file
+    source: ./business.md
+
+  - type: inline
+    content: |
+      ## Artifact Structure
+      Read the document structure template from: `.ai-agents/skills/_templates/review-output.md`
+      If a custom version exists at `.ai-agents/skills/_templates/custom/review-output.md`, use the custom version instead.
+      The template defines section headings only. Generate content for each section based on review results.
+      Write the artifact to: `.ai-agents/workspace/artifacts/{change-id}/review.md`
+
+  - type: shared
+    source: sections/session-update.md
+    params:
+      current_skill: mvt-review
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-review
+      conditional_suggestions:
+        conditions:
+          - condition: "critical issues found"
+            primary: mvt-fix
+            primary_desc: "Fix the critical issues before merge"
+          - condition: "review approved, tests not written"
+            primary: mvt-test
+            primary_desc: "Add test coverage"
+          - condition: "review approved, all checks passed"
+            primary: mvt-update-plan
+            primary_desc: "Mark review task done in the plan"

package/sources/skills/mvt-status/business.md

@@ -9,24 +9,24 @@
   - If `session.yaml` exists but is empty (zero keys), treat as `not initialized` -> recommend `/mvt-init`.
 
 ### Step 2: Build Activity Timeline
-- **What**: produce the most-recent-first list of skill_history entries with derived metadata.
+- **What**: produce the most-recent-first list of history entries with derived metadata.
 - **How**:
-  1. Read `skill_history` from `session.yaml`.
+  1. Read `history` from `session.yaml`.
   2. For each entry, attach: relative time (e.g., "2h ago"), `change_id` (if present), and the originating skill name.
   3. Limit to the last 10 entries for the rendered table; keep full count separately for the summary line.
 
 ### Step 3: Discover All Plans (Multi-Change Dashboard)
 - **What**: produce the canonical plan list across the workspace.
 - **How**:
-  1. Iterate `recent_changes[]` from `session.yaml`. For each entry with a `plan_path`, attempt to read the plan file.
-  2. Glob `.ai-agents/workspace/artifacts/*/plan.yaml` to find any plans not registered in `recent_changes` (mark them `unindexed`).
+  1. Iterate `changes[]` from `session.yaml`. For each entry with a `plan_path`, attempt to read the plan file.
+  2. Glob `.ai-agents/workspace/artifacts/*/plan.yaml` to find any plans not registered in `changes` (mark them `unindexed`). **Exclude paths under `artifacts/_archived/`** — those are completed changes archived by `/mvt-cleanup`.
   3. For each plan, extract: `change_id`, `title`, `status`, `current_task`, task progress (`done/total`), `updated_at`, `skill_hint` (from current task if present).
   4. If a plan file is present but malformed, include a row with `(corrupt)` in the status column and mark the file path; do not abort.
 - **Branches**:
 
   | Condition | Action |
   |-----------|--------|
-  | No plans found anywhere | Skip the Changes Overview section entirely; render only legacy `active_change` summary |
+  | No plans found anywhere | Skip the Changes Overview section entirely; render "No active changes." |
   | One plan found | Render Changes Overview with one row |
   | Multiple plans found | Render Changes Overview sorted: `in_progress` desc by `updated_at` first, then `done` desc by `updated_at`, then `abandoned` last |
   | Any plan over the cap (more than ~12 rows) | Show top 10 rows; print a `+N older changes hidden -- see artifacts/` line |
@@ -37,35 +37,31 @@
   1. **Header** -- one-line summary: project name (from `project-context.yaml`), framework version, last synced timestamp.
   2. **Projects** -- table: name | type | tech stack (truncated). Cap at 10 rows; collapse the rest into `+N more`.
   3. **Semantic Context** -- one line: `project-context.md present` / `missing -- run /mvt-analyze-code`.
-  4. **Active Change** -- if `active_change` exists: id, title, current phase, start time. Else: `none`.
+  4. **Active Change** -- if `active_change` exists: id, title, start time. Else: `none`.
   5. **Changes Overview** -- table from Step 3 (skip if no plans). Render with these columns:
 
-     | change-id | title | status | progress | current_task | last_updated |
-     |-----------|-------|--------|----------|--------------|--------------|
+     | change-id | title | status | progress | current_task | updated_at |
+     |-----------|-------|--------|----------|--------------|------------|
   6. **Skill History** -- last 5 rows of the timeline from Step 2.
-  7. **Recent Actions** -- compact list (max 5).
 
-- Hard cap: total rendered output should not exceed ~120 lines. If it would, truncate Skill History and Recent Actions first; never truncate the active change or Changes Overview header rows.
+- Hard cap: total rendered output should not exceed ~120 lines. If it would, truncate Skill History first; never truncate the active change or Changes Overview header rows.
 
 ### Step 5: Suggest Next Step
 - Resolution order (first match wins):
   1. `active_change` has a plan in `in_progress`, `current_task` is set -> suggest the task's `skill_hint` (or, if missing, recommend `/mvt-update-plan` to set `current_task`).
-  2. `active_change` exists but no plan -> infer next workflow phase from `skill_history` (last completed phase determines next).
-  3. No `active_change`, but `project-context.md` is missing -> suggest `/mvt-analyze-code`.
-  4. No `active_change`, no missing context -> suggest `/mvt-analyze` to start a new feature OR `/mvt-help` to browse the catalog.
+  2. `project-context.md` is missing -> suggest `/mvt-analyze-code`.
+  3. No `active_change` or no active plan -> suggest `/mvt-analyze` to start a new feature OR `/mvt-help` to browse the catalog.
 - The suggestion must be a single line: skill command + one-clause reason.
 
-### Step 6: (session update handled by shared section)
-
 ## Edge Cases & Errors
 
 | Case | Handling |
 |------|----------|
 | `session.yaml` missing entirely | Render a minimal report (Projects section if available) and recommend `/mvt-init` |
-| `session.yaml` corrupt (parse error) | Surface error with file path, render Projects only, recommend `/mvt-sync-context` |
-| `recent_changes[]` references a `plan_path` that no longer exists | Include in Changes Overview with `(missing)` marker; do not delete the index entry from this skill |
+| `session.yaml` corrupt (parse error) | Surface error with file path, render Projects only, recommend `/mvt-init` to reinitialize |
+| `changes[]` references a `plan_path` that no longer exists | Include in Changes Overview with `(missing)` marker; do not delete the index entry from this skill |
 | Plan file's `current_task` references a task id not in `tasks[]` | Render `current_task` as `(invalid: <id>)`; do not attempt to fix |
 | Plan file's `status` is not one of the known values | Render the raw value verbatim; flag in skip-checks of the report |
-| Both `recent_changes[]` and the artifact glob find the same plan | Deduplicate by `change_id`; prefer the indexed entry's metadata |
+| Both `changes[]` and the artifact glob find the same plan | Deduplicate by `change_id`; prefer the indexed entry's metadata |
 | Multiple `in_progress` plans | All rendered in Changes Overview; Step 5's suggestion picks the most recently updated; mention the count in the suggestion line |
 | Workspace contains zero projects | Render header only with a single suggestion: `/mvt-init` |

package/sources/skills/mvt-status/manifest.yaml

@@ -1,66 +1,74 @@
-name: mvt-status
-output: .claude/skills/mvt-status/SKILL.md
-
-frontmatter:
-  name: mvt-status
-  description: "Display current project and workflow status including skill history, active changes, and session state. This skill should be used when user wants to check project status, review workflow progress, or see where they are in the development cycle."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Status
-
-      ## Purpose
-
-      Display comprehensive project and workflow status, showing project list, semantic context availability, skill history, active changes, and current session state.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Conductor
-      role_desc: "a Workflow Coordinator"
-      decision_rules:
-        - rule: "If project not initialized -> Warn and suggest `/mvt-init`"
-        - rule: "If no active change -> Show project info only, suggest starting a workflow"
-        - rule: "If workflow in progress -> Highlight recent skill history and next recommended step"
-        - rule: "If project-context.md missing -> Suggest `/mvt-analyze-code` to generate semantic context"
-        - rule: "If one or more plans exist -> Show Changes Overview table with progress for all plans"
-        - rule: "If an in_progress plan has a current_task -> Suggest the matching skill_hint as next step"
-      boundaries:
-        - scope: "analyze requirements"
-          skill: "/mvt-analyze"
-        - scope: "design architecture"
-          skill: "/mvt-design"
-        - scope: "write implementation code"
-          skill: "/mvt-implement"
-
-  - type: shared
-    source: sections/activation-load-context.md
-
-  - type: shared
-    source: sections/activation-load-config.md
-
-  - type: shared
-    source: sections/output-language-constraint.md
-
-  - type: shared
-    source: sections/activation-preflight.md
-    params:
-      checks:
-        - order: "1"
-          field: "session.initialized_at"
-          level: "WARN"
-          message: "Session not initialized. Run `/mvt-init` first."
-
-  - type: file
-    source: ./business.md
-
-  - type: shared
-    source: sections/session-update.md
-    params:
-      read_only: true
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-status
+name: mvt-status
+output: .claude/skills/mvt-status/SKILL.md
+
+frontmatter:
+  name: mvt-status
+  description: "Display current project and workflow status including skill history, active changes, and session state. This skill should be used when user wants to check project status, review workflow progress, or see where they are in the development cycle."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Status
+
+      ## Purpose
+
+      Display comprehensive project and workflow status, showing project list, semantic context availability, skill history, active changes, and current session state.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Conductor
+      role_desc: "a Workflow Coordinator"
+      decision_rules:
+        - rule: "If project not initialized -> Warn and suggest `/mvt-init`"
+        - rule: "If no active change -> Show project info only, suggest starting a workflow"
+        - rule: "If workflow in progress -> Highlight recent skill history and next recommended step"
+        - rule: "If project-context.md missing -> Suggest `/mvt-analyze-code` to generate semantic context"
+        - rule: "If one or more plans exist -> Show Changes Overview table with progress for all plans"
+        - rule: "If an in_progress plan has a current_task -> Suggest the matching skill_hint as next step"
+      boundaries:
+        - scope: "analyze requirements"
+          skill: "/mvt-analyze"
+        - scope: "design architecture"
+          skill: "/mvt-design"
+        - scope: "write implementation code"
+          skill: "/mvt-implement"
+
+  - type: shared
+    source: sections/activation-load-context.md
+
+  - type: shared
+    source: sections/activation-load-config.md
+
+  - type: shared
+    source: sections/activation-preflight.md
+    params:
+      checks:
+        - order: "1"
+          field: "session.initialized_at"
+          level: "WARN"
+          message: "Session not initialized. Run `/mvt-init` first."
+
+  - type: file
+    source: ./business.md
+
+  - type: shared
+    source: sections/session-update.md
+    params:
+      read_only: true
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-status
+      conditional_suggestions:
+        conditions:
+          - condition: "active change with current_task"
+            primary: mvt-resume
+            primary_desc: "Resume work on the current task"
+          - condition: "project-context.md missing"
+            primary: mvt-analyze-code
+            primary_desc: "Generate semantic project context"
+          - condition: "no active change"
+            primary: mvt-analyze
+            primary_desc: "Start analyzing a new feature"