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

package/sources/skills/mvt-plan-dev/manifest.yaml

@@ -1,91 +1,91 @@
-name: mvt-plan-dev
-output: .claude/skills/mvt-plan-dev/SKILL.md
-
-frontmatter:
-  name: mvt-plan-dev
-  description: "Generate a structured development plan (plan.yaml) for a large change. This skill should be used when a change is too big for a single implement pass and needs to be tracked across multiple sessions with task-level granularity."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Plan Dev
-
-      ## Purpose
-
-      Decompose a large change into a structured `plan.yaml` so progress can survive across conversations. Each task carries status, dependencies, acceptance criteria, and a recommended skill, enabling `/mvt-resume` to land precisely on the next executable task in a future session.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Architect
-      role_desc: "a Development Planner"
-      decision_rules:
-        - rule: "active_change is set AND has_plan is false -> Generate a fresh plan.yaml"
-        - rule: "active_change is set AND has_plan is true -> Confirm before regenerating; default to /mvt-update-plan"
-        - rule: "Tasks would exceed 10 -> Stop, propose phasing the change into multiple plans"
-        - rule: "Dependencies form a cycle -> Reject and ask the user to resolve"
-        - rule: "active_change is empty -> Stop and request /mvt-analyze first"
-      boundaries:
-        - scope: "create or modify the active change itself"
-          skill: "/mvt-analyze"
-        - scope: "design architecture"
-          skill: "/mvt-design"
-        - scope: "advance task status after completion"
-          skill: "/mvt-update-plan"
-        - scope: "implement code"
-          skill: "/mvt-implement"
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - ".ai-agents/workspace/artifacts/{active_change.id}/ -- Existing analysis/design artifacts for this change"
-        - ".ai-agents/workspace/artifacts/{active_change.id}/plan.yaml -- Existing plan, if any (regeneration mode)"
-
-  - 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: "active_change.id"
-          level: "BLOCK"
-          message: 'No active change. Run `/mvt-analyze` to create one before planning.'
-
-  - type: file
-    source: ./business.md
-
-
-  - type: shared
-    source: sections/session-update.md
-
-  - type: inline
-    content: |
-      ### Plan-Dev Specific State Updates
-
-      In addition to the mandatory updates above, this skill MUST update:
-
-      - `active_change.plan_path`: Set to `".ai-agents/workspace/artifacts/{active_change.id}/plan.yaml"`
-      - `active_change.has_plan`: Set to `true`
-      - `recent_changes`: Append (or update if entry with same `id` exists) an entry:
-        ```yaml
-        - id: "{active_change.id}"
-          title: "{active_change.title}"
-          plan_path: ".ai-agents/workspace/artifacts/{active_change.id}/plan.yaml"
-          last_updated: "{current timestamp ISO 8601}"
-        ```
-        Keep max 5 entries (drop the oldest by `last_updated` ascending).
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-plan-dev
+name: mvt-plan-dev
+output: .claude/skills/mvt-plan-dev/SKILL.md
+
+frontmatter:
+  name: mvt-plan-dev
+  description: "Generate a structured development plan (plan.yaml) for a large change. This skill should be used when a change is too big for a single implement pass and needs to be tracked across multiple sessions with task-level granularity."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Plan Dev
+
+      ## Purpose
+
+      Decompose a large change into a structured `plan.yaml` so progress can survive across conversations. Each task carries status, dependencies, acceptance criteria, and a recommended skill, enabling `/mvt-resume` to land precisely on the next executable task in a future session.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Architect
+      role_desc: "a Development Planner"
+      decision_rules:
+        - rule: "active_change is set AND has_plan is false -> Generate a fresh plan.yaml"
+        - rule: "active_change is set AND has_plan is true -> Confirm before regenerating; default to /mvt-update-plan"
+        - rule: "Tasks would exceed 10 -> Stop, propose phasing the change into multiple plans"
+        - rule: "Dependencies form a cycle -> Reject and ask the user to resolve"
+        - rule: "active_change is empty -> Stop and request /mvt-analyze first"
+      boundaries:
+        - scope: "create or modify the active change itself"
+          skill: "/mvt-analyze"
+        - scope: "design architecture"
+          skill: "/mvt-design"
+        - scope: "advance task status after completion"
+          skill: "/mvt-update-plan"
+        - scope: "implement code"
+          skill: "/mvt-implement"
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - ".ai-agents/workspace/artifacts/{active_change.id}/ -- Existing analysis/design artifacts for this change"
+        - ".ai-agents/workspace/artifacts/{active_change.id}/plan.yaml -- Existing plan, if any (regeneration mode)"
+
+  - 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: "active_change.id"
+          level: "BLOCK"
+          message: 'No active change. Run `/mvt-analyze` to create one before planning.'
+
+  - type: file
+    source: ./business.md
+
+
+  - type: shared
+    source: sections/session-update.md
+
+  - type: inline
+    content: |
+      ### Plan-Dev Specific State Updates
+
+      In addition to the mandatory updates above, this skill MUST update:
+
+      - `active_change.plan_path`: Set to `".ai-agents/workspace/artifacts/{active_change.id}/plan.yaml"`
+      - `active_change.has_plan`: Set to `true`
+      - `recent_changes`: Append (or update if entry with same `id` exists) an entry:
+        ```yaml
+        - id: "{active_change.id}"
+          title: "{active_change.title}"
+          plan_path: ".ai-agents/workspace/artifacts/{active_change.id}/plan.yaml"
+          last_updated: "{current timestamp ISO 8601}"
+        ```
+        Keep max 5 entries (drop the oldest by `last_updated` ascending).
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-plan-dev

package/sources/skills/mvt-quick-dev/manifest.yaml

@@ -1,69 +1,69 @@
-name: mvt-quick-dev
-output: .claude/skills/mvt-quick-dev/SKILL.md
-
-frontmatter:
-  name: mvt-quick-dev
-  description: "Quickly implement simple, well-scoped changes without the full analyze-design-implement workflow. This skill should be used when the change is small (1-3 files), architecturally neutral, and clearly specified — such as adding a field, fixing a label, adjusting config, or making a targeted enhancement."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Quick Dev
-
-      ## Purpose
-
-      Implement simple, well-scoped changes quickly, bypassing the full workflow. For changes that are small (1-3 files), architecturally neutral, and clearly specified. Produces no artifacts — results are conversation-only.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Developer
-      role_desc: "an Implementation Specialist"
-      decision_rules:
-        - rule: "Change is Trivial (1 file, ≤10 lines) -> Implement directly, conversation-only"
-        - rule: "Change is Simple (1-3 files, no module break) -> Implement, show plan first, conversation-only"
-        - rule: "Change is Complex -> STOP, recommend /mvt-analyze or /mvt-design"
-        - rule: "Ambiguous scope -> Ask user to confirm before proceeding"
-        - rule: "Implementation reveals unexpected complexity -> Revert and escalate"
-        - rule: "Existing tests cover changed code -> Suggest running them"
-      boundaries:
-        - scope: "analyze complex requirements"
-          skill: "/mvt-analyze"
-        - scope: "design architecture"
-          skill: "/mvt-design"
-        - scope: "review code"
-          skill: "/mvt-review"
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - ".ai-agents/knowledge/project/_generated/project-context.md -- Module/layer map (optional)"
-        - ".ai-agents/knowledge/principle/coding-standards.md -- Coding standards (optional)"
-        - "Target source files (load based on change description)"
-
-  - type: shared
-    source: sections/activation-load-config.md
-
-  - type: shared
-    source: sections/output-language-constraint.md
-
-  - type: inline
-    content: |
-      ### Shortcut Operation Rules
-      - Can execute at any time without checking workflow prerequisites
-      - Do NOT update `progress` (this is a shortcut operation, not a workflow phase)
-      - Do NOT create an `active_change` if one doesn't already exist
-      - Do NOT write any artifact or document — results are conversation-only
-      - Do NOT interact with plan.yaml in any way — this skill is plan-independent
-
-  - type: file
-    source: ./business.md
-
-  - type: shared
-    source: sections/session-update.md
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-quick-dev
+name: mvt-quick-dev
+output: .claude/skills/mvt-quick-dev/SKILL.md
+
+frontmatter:
+  name: mvt-quick-dev
+  description: "Quickly implement simple, well-scoped changes without the full analyze-design-implement workflow. This skill should be used when the change is small (1-3 files), architecturally neutral, and clearly specified — such as adding a field, fixing a label, adjusting config, or making a targeted enhancement."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Quick Dev
+
+      ## Purpose
+
+      Implement simple, well-scoped changes quickly, bypassing the full workflow. For changes that are small (1-3 files), architecturally neutral, and clearly specified. Produces no artifacts — results are conversation-only.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Developer
+      role_desc: "an Implementation Specialist"
+      decision_rules:
+        - rule: "Change is Trivial (1 file, ≤10 lines) -> Implement directly, conversation-only"
+        - rule: "Change is Simple (1-3 files, no module break) -> Implement, show plan first, conversation-only"
+        - rule: "Change is Complex -> STOP, recommend /mvt-analyze or /mvt-design"
+        - rule: "Ambiguous scope -> Ask user to confirm before proceeding"
+        - rule: "Implementation reveals unexpected complexity -> Revert and escalate"
+        - rule: "Existing tests cover changed code -> Suggest running them"
+      boundaries:
+        - scope: "analyze complex requirements"
+          skill: "/mvt-analyze"
+        - scope: "design architecture"
+          skill: "/mvt-design"
+        - scope: "review code"
+          skill: "/mvt-review"
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - ".ai-agents/knowledge/project/_generated/project-context.md -- Module/layer map (optional)"
+        - ".ai-agents/knowledge/principle/coding-standards.md -- Coding standards (optional)"
+        - "Target source files (load based on change description)"
+
+  - type: shared
+    source: sections/activation-load-config.md
+
+  - type: shared
+    source: sections/output-language-constraint.md
+
+  - type: inline
+    content: |
+      ### Shortcut Operation Rules
+      - Can execute at any time without checking workflow prerequisites
+      - Do NOT update `progress` (this is a shortcut operation, not a workflow phase)
+      - Do NOT create an `active_change` if one doesn't already exist
+      - Do NOT write any artifact or document — results are conversation-only
+      - Do NOT interact with plan.yaml in any way — this skill is plan-independent
+
+  - type: file
+    source: ./business.md
+
+  - type: shared
+    source: sections/session-update.md
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-quick-dev

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

@@ -1,86 +1,86 @@
-name: mvt-refactor
-output: .claude/skills/mvt-refactor/SKILL.md
-
-frontmatter:
-  name: mvt-refactor
-  description: "Refactor existing code while preserving behavior. This skill should be used when user wants to improve code structure, rename symbols, extract methods or classes, or reorganize code without changing functionality."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Refactor
-
-      ## Purpose
-
-      Refactor existing code while preserving observable behavior. This is a structure-only operation focused on improving code quality, readability, and maintainability. This is a shortcut operation that can run at any time.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Developer
-      role_desc: "an Implementation Specialist"
-      decision_rules:
-        - rule: "Refactoring target specified -> Analyze and plan the refactoring"
-        - rule: "No target specified -> Prompt user for refactoring target"
-        - rule: "Risk level is High -> Warn user and require explicit confirmation"
-        - rule: "Tests exist for target code -> Recommend running them after refactoring"
-        - rule: "No tests exist -> Describe how to verify behavior is unchanged"
-        - rule: "Change requires new module not in design -> Flag for Architect"
-      boundaries:
-        - scope: "re-analyze requirements"
-          skill: "/mvt-analyze"
-        - scope: "evaluate architecture"
-          skill: "/mvt-design"
-        - scope: "review own code"
-          skill: "/mvt-review"
-
-  - type: inline
-    content: |
-      ### Constraints
-      - Do NOT change observable behavior -- refactoring is structure-only
-      - Do NOT introduce new features during refactoring
-      - Do NOT modify unrelated code outside the refactoring scope
-
-      ## Refactoring Types
-
-      | Type | Risk Level | Examples |
-      |------|------------|----------|
-      | Rename | Low | Variable, function, file rename |
-      | Extract Method/Class | Low | Pull repeated logic into a helper |
-      | Inline | Low | Eliminate a thin wrapper |
-      | Move | Medium | Relocate code to appropriate module/layer |
-      | Decompose Conditional | Medium | Simplify complex if/switch logic |
-      | Replace Inheritance with Composition | High | Class-hierarchy redesign |
-      | Change Interface/API | High | Modify public contracts |
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - "Related source files to be refactored"
-
-  - type: shared
-    source: sections/activation-load-config.md
-
-  - type: shared
-    source: sections/output-language-constraint.md
-
-  - type: inline
-    content: |
-      ### Step 3: Pre-flight Checks
-      - No blocking checks required (shortcut operation).
-
-      ### Shortcut Operation Rules
-      - Can execute at any time without checking workflow prerequisites
-
-  - type: file
-    source: ./business.md
-
-
-  - type: shared
-    source: sections/session-update.md
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-refactor
+name: mvt-refactor
+output: .claude/skills/mvt-refactor/SKILL.md
+
+frontmatter:
+  name: mvt-refactor
+  description: "Refactor existing code while preserving behavior. This skill should be used when user wants to improve code structure, rename symbols, extract methods or classes, or reorganize code without changing functionality."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Refactor
+
+      ## Purpose
+
+      Refactor existing code while preserving observable behavior. This is a structure-only operation focused on improving code quality, readability, and maintainability. This is a shortcut operation that can run at any time.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Developer
+      role_desc: "an Implementation Specialist"
+      decision_rules:
+        - rule: "Refactoring target specified -> Analyze and plan the refactoring"
+        - rule: "No target specified -> Prompt user for refactoring target"
+        - rule: "Risk level is High -> Warn user and require explicit confirmation"
+        - rule: "Tests exist for target code -> Recommend running them after refactoring"
+        - rule: "No tests exist -> Describe how to verify behavior is unchanged"
+        - rule: "Change requires new module not in design -> Flag for Architect"
+      boundaries:
+        - scope: "re-analyze requirements"
+          skill: "/mvt-analyze"
+        - scope: "evaluate architecture"
+          skill: "/mvt-design"
+        - scope: "review own code"
+          skill: "/mvt-review"
+
+  - type: inline
+    content: |
+      ### Constraints
+      - Do NOT change observable behavior -- refactoring is structure-only
+      - Do NOT introduce new features during refactoring
+      - Do NOT modify unrelated code outside the refactoring scope
+
+      ## Refactoring Types
+
+      | Type | Risk Level | Examples |
+      |------|------------|----------|
+      | Rename | Low | Variable, function, file rename |
+      | Extract Method/Class | Low | Pull repeated logic into a helper |
+      | Inline | Low | Eliminate a thin wrapper |
+      | Move | Medium | Relocate code to appropriate module/layer |
+      | Decompose Conditional | Medium | Simplify complex if/switch logic |
+      | Replace Inheritance with Composition | High | Class-hierarchy redesign |
+      | Change Interface/API | High | Modify public contracts |
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - "Related source files to be refactored"
+
+  - type: shared
+    source: sections/activation-load-config.md
+
+  - type: shared
+    source: sections/output-language-constraint.md
+
+  - type: inline
+    content: |
+      ### Step 3: Pre-flight Checks
+      - No blocking checks required (shortcut operation).
+
+      ### Shortcut Operation Rules
+      - Can execute at any time without checking workflow prerequisites
+
+  - type: file
+    source: ./business.md
+
+
+  - type: shared
+    source: sections/session-update.md
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-refactor

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

@@ -1,71 +1,71 @@
-name: mvt-resume
-output: .claude/skills/mvt-resume/SKILL.md
-
-frontmatter:
-  name: mvt-resume
-  description: "Resume an in-progress development task in a new conversation. Reads session.yaml (active_change, skill_history, recent_actions) and recent artifacts to reconstruct context. Does not read git state."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Resume
-
-      ## Purpose
-
-      Reconstruct an in-progress development task in a fresh conversation by replaying state from `session.yaml`, recent artifacts, and plan.yaml (if one exists). When multiple plans are in-flight, prompt the user to select which change to resume. Use this skill at the start of a new conversation to pick up exactly where the last session left off.
-
-      ## Arguments
-
-      | Argument | Required | Description |
-      |----------|----------|-------------|
-      | `{change-id}` | No | Directly resume a specific change (skips candidate selection). Error if not found or not in_progress. |
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Conductor
-      role_desc: "a Workflow Coordinator"
-      decision_rules:
-        - rule: "Multiple in_progress plans found -> Pause and display candidate table, wait for user selection"
-        - rule: "Exactly one in_progress plan found -> Auto-select it and proceed"
-        - rule: "No plans found BUT active_change is set -> Fall back to legacy skill_history-based resume"
-        - rule: "active_change is empty AND skill_history is empty AND no plans -> Recommend `/mvt-init` or `/mvt-status`"
-        - rule: "Plan exists and has current_task -> Use current_task's skill_hint as next-step recommendation"
-        - rule: "Plan's current_task has been in_progress for >5 days -> Surface stale warning"
-        - rule: "Last skill failed or was interrupted -> Surface the failure context, suggest retry"
-      boundaries:
-        - scope: "read git state (branch, diff, commits)"
-          skill: "(Out of scope -- this skill is session-state only)"
-        - scope: "modify any files"
-          skill: "(Read-only)"
-        - scope: "run analyses or tests"
-          skill: "(Use the recommended next skill)"
-
-  - 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
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-resume
+name: mvt-resume
+output: .claude/skills/mvt-resume/SKILL.md
+
+frontmatter:
+  name: mvt-resume
+  description: "Resume an in-progress development task in a new conversation. Reads session.yaml (active_change, skill_history, recent_actions) and recent artifacts to reconstruct context. Does not read git state."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Resume
+
+      ## Purpose
+
+      Reconstruct an in-progress development task in a fresh conversation by replaying state from `session.yaml`, recent artifacts, and plan.yaml (if one exists). When multiple plans are in-flight, prompt the user to select which change to resume. Use this skill at the start of a new conversation to pick up exactly where the last session left off.
+
+      ## Arguments
+
+      | Argument | Required | Description |
+      |----------|----------|-------------|
+      | `{change-id}` | No | Directly resume a specific change (skips candidate selection). Error if not found or not in_progress. |
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Conductor
+      role_desc: "a Workflow Coordinator"
+      decision_rules:
+        - rule: "Multiple in_progress plans found -> Pause and display candidate table, wait for user selection"
+        - rule: "Exactly one in_progress plan found -> Auto-select it and proceed"
+        - rule: "No plans found BUT active_change is set -> Fall back to legacy skill_history-based resume"
+        - rule: "active_change is empty AND skill_history is empty AND no plans -> Recommend `/mvt-init` or `/mvt-status`"
+        - rule: "Plan exists and has current_task -> Use current_task's skill_hint as next-step recommendation"
+        - rule: "Plan's current_task has been in_progress for >5 days -> Surface stale warning"
+        - rule: "Last skill failed or was interrupted -> Surface the failure context, suggest retry"
+      boundaries:
+        - scope: "read git state (branch, diff, commits)"
+          skill: "(Out of scope -- this skill is session-state only)"
+        - scope: "modify any files"
+          skill: "(Read-only)"
+        - scope: "run analyses or tests"
+          skill: "(Use the recommended next skill)"
+
+  - 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
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-resume