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

package/sources/skills/mvt-sync-context/manifest.yaml

@@ -1,96 +1,96 @@
-name: mvt-sync-context
-output: .claude/skills/mvt-sync-context/SKILL.md
-
-frontmatter:
-  name: mvt-sync-context
-  description: "Aggregate completed change artifacts (analysis/design/implementation) and merge new domain knowledge into project-context.md and project-context.yaml. This skill should be used after one or more changes are completed to keep long-term project knowledge in sync with delivered work."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Sync Context
-
-      ## Purpose
-
-      Keep `project-context.md` (semantic) and `project-context.yaml` (structural index) in sync with completed work. This is an artifact-driven, incremental synchronization: it reads workspace artifacts of completed changes, classifies new domain knowledge, and merges it into the long-term context. It does NOT scan code for new content; an optional read-only code verification step can validate that artifact-claimed entities exist.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Conductor
-      role_desc: "a Workflow Coordinator"
-      decision_rules:
-        - rule: "Completed changes found -> List for user confirmation, then aggregate"
-        - rule: "No completed changes since last sync -> Report nothing to do"
-        - rule: "Conflicts with existing project-context.md -> Render conflict table, require user resolution"
-        - rule: "User opts in to code verification -> Run read-only scan; flag artifact entries that cannot be located"
-        - rule: "Code-only entities discovered (in code, not in artifacts) -> Do NOT write; recommend /mvt-analyze-code"
-        - rule: "Artifact references modules/source_paths absent from project-context.yaml -> Propose yaml additions for user confirmation"
-      boundaries:
-        - scope: "regenerate project-context.md from full code scan"
-          skill: "/mvt-analyze-code"
-        - scope: "archive completed change artifacts"
-          skill: "/mvt-cleanup"
-        - scope: "manage shared / per-skill knowledge files"
-          skill: "/mvt-manage-context"
-
-  - type: inline
-    content: |
-      ### When to Use
-      - After one or more changes are marked `completed` and you want to fold their knowledge into long-term context
-      - BEFORE running `/mvt-cleanup` (sync first, archive after)
-      - When `project-context.md` looks behind delivered work but you do not want to pay a full `/mvt-analyze-code` regeneration
-
-      ### When NOT to Use
-      - For deletions, renames, or module deprecations -> use `/mvt-analyze-code` (full ground-truth rebuild)
-      - To pick up code changes never recorded as MVTT changes -> use `/mvt-analyze-code`
-      - To clean / archive workspace -> use `/mvt-cleanup`
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - ".ai-agents/workspace/artifacts/{change-id}/ -- Source artifacts for completed changes"
-        - ".ai-agents/knowledge/project/_generated/project-context.md -- Current semantic context (merge target)"
-        - ".ai-agents/workspace/project-context.yaml -- Current structural index (merge target)"
-
-  - 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: "BLOCK"
-          message: "Session not initialized. Run `/mvt-init` first."
-        - order: "2"
-          field: ".ai-agents/knowledge/project/_generated/project-context.md exists"
-          level: "BLOCK"
-          message: "project-context.md not found. Run `/mvt-analyze-code` to create the initial document; this skill only handles incremental updates."
-
-  - type: file
-    source: ./business.md
-
-  - type: shared
-    source: sections/session-update.md
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-sync-context
-      conditional_suggestions:
-        conditions:
-          - condition: "merge applied successfully"
-            primary: "mvt-cleanup"
-            primary_desc: "Archive aggregated change artifacts now that knowledge is sync'd"
-          - condition: "code verification flagged code-only entities"
-            primary: "mvt-analyze-code"
-            primary_desc: "Regenerate project-context.md from full code scan"
-          - condition: "default"
-            primary: "mvt-check-context"
-            primary_desc: "Audit token cost and overall context health"
+name: mvt-sync-context
+output: .claude/skills/mvt-sync-context/SKILL.md
+
+frontmatter:
+  name: mvt-sync-context
+  description: "Aggregate completed change artifacts (analysis/design/implementation) and merge new domain knowledge into project-context.md and project-context.yaml. This skill should be used after one or more changes are completed to keep long-term project knowledge in sync with delivered work."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Sync Context
+
+      ## Purpose
+
+      Keep `project-context.md` (semantic) and `project-context.yaml` (structural index) in sync with completed work. This is an artifact-driven, incremental synchronization: it reads workspace artifacts of completed changes, classifies new domain knowledge, and merges it into the long-term context. It does NOT scan code for new content; an optional read-only code verification step can validate that artifact-claimed entities exist.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Conductor
+      role_desc: "a Workflow Coordinator"
+      decision_rules:
+        - rule: "Completed changes found -> List for user confirmation, then aggregate"
+        - rule: "No completed changes since last sync -> Report nothing to do"
+        - rule: "Conflicts with existing project-context.md -> Render conflict table, require user resolution"
+        - rule: "User opts in to code verification -> Run read-only scan; flag artifact entries that cannot be located"
+        - rule: "Code-only entities discovered (in code, not in artifacts) -> Do NOT write; recommend /mvt-analyze-code"
+        - rule: "Artifact references modules/source_paths absent from project-context.yaml -> Propose yaml additions for user confirmation"
+      boundaries:
+        - scope: "regenerate project-context.md from full code scan"
+          skill: "/mvt-analyze-code"
+        - scope: "archive completed change artifacts"
+          skill: "/mvt-cleanup"
+        - scope: "manage shared / per-skill knowledge files"
+          skill: "/mvt-manage-context"
+
+  - type: inline
+    content: |
+      ### When to Use
+      - After one or more changes are marked `completed` and you want to fold their knowledge into long-term context
+      - BEFORE running `/mvt-cleanup` (sync first, archive after)
+      - When `project-context.md` looks behind delivered work but you do not want to pay a full `/mvt-analyze-code` regeneration
+
+      ### When NOT to Use
+      - For deletions, renames, or module deprecations -> use `/mvt-analyze-code` (full ground-truth rebuild)
+      - To pick up code changes never recorded as MVTT changes -> use `/mvt-analyze-code`
+      - To clean / archive workspace -> use `/mvt-cleanup`
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - ".ai-agents/workspace/artifacts/{change-id}/ -- Source artifacts for completed changes"
+        - ".ai-agents/knowledge/project/_generated/project-context.md -- Current semantic context (merge target)"
+        - ".ai-agents/workspace/project-context.yaml -- Current structural index (merge target)"
+
+  - 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: "BLOCK"
+          message: "Session not initialized. Run `/mvt-init` first."
+        - order: "2"
+          field: ".ai-agents/knowledge/project/_generated/project-context.md exists"
+          level: "BLOCK"
+          message: "project-context.md not found. Run `/mvt-analyze-code` to create the initial document; this skill only handles incremental updates."
+
+  - type: file
+    source: ./business.md
+
+  - type: shared
+    source: sections/session-update.md
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-sync-context
+      conditional_suggestions:
+        conditions:
+          - condition: "merge applied successfully"
+            primary: "mvt-cleanup"
+            primary_desc: "Archive aggregated change artifacts now that knowledge is sync'd"
+          - condition: "code verification flagged code-only entities"
+            primary: "mvt-analyze-code"
+            primary_desc: "Regenerate project-context.md from full code scan"
+          - condition: "default"
+            primary: "mvt-check-context"
+            primary_desc: "Audit token cost and overall context health"

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

@@ -1,63 +1,63 @@
-name: mvt-template
-output: .claude/skills/mvt-template/SKILL.md
-
-frontmatter:
-  name: mvt-template
-  description: "View, customize, and manage output templates for MVTT skills. This skill should be used when user wants to inspect available templates, create custom template versions, reset customizations, or export templates."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Custom Template
-
-      ## Purpose
-
-      View, customize, and manage MVTT output templates. Inspect default templates, create custom versions that override defaults, reset customizations, and export templates.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Conductor
-      role_desc: "a Workflow Coordinator"
-      decision_rules:
-        - rule: "No arguments -> Show template list with status"
-        - rule: "User selects \"view\" -> Display full template content (custom version if exists)"
-        - rule: "User selects \"customize\" -> Guide through modification process"
-        - rule: "User selects \"reset\" -> Delete custom version, restore default"
-        - rule: "User selects \"export\" -> Output template to specified location"
-        - rule: "Custom template must preserve frontmatter format"
-      boundaries:
-        - scope: "modify default templates in `_templates/` root"
-          skill: "(Only create/modify in `custom/`)"
-        - scope: "modify skill logic"
-          skill: "(Only change output formatting)"
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - "Scan `.ai-agents/skills/_templates/custom/` for existing customizations"
-
-  - 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.
-
-  - 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-template
+name: mvt-template
+output: .claude/skills/mvt-template/SKILL.md
+
+frontmatter:
+  name: mvt-template
+  description: "View, customize, and manage output templates for MVTT skills. This skill should be used when user wants to inspect available templates, create custom template versions, reset customizations, or export templates."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Custom Template
+
+      ## Purpose
+
+      View, customize, and manage MVTT output templates. Inspect default templates, create custom versions that override defaults, reset customizations, and export templates.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Conductor
+      role_desc: "a Workflow Coordinator"
+      decision_rules:
+        - rule: "No arguments -> Show template list with status"
+        - rule: "User selects \"view\" -> Display full template content (custom version if exists)"
+        - rule: "User selects \"customize\" -> Guide through modification process"
+        - rule: "User selects \"reset\" -> Delete custom version, restore default"
+        - rule: "User selects \"export\" -> Output template to specified location"
+        - rule: "Custom template must preserve frontmatter format"
+      boundaries:
+        - scope: "modify default templates in `_templates/` root"
+          skill: "(Only create/modify in `custom/`)"
+        - scope: "modify skill logic"
+          skill: "(Only change output formatting)"
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - "Scan `.ai-agents/skills/_templates/custom/` for existing customizations"
+
+  - 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.
+
+  - 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-template

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

@@ -1,102 +1,102 @@
-name: mvt-test
-output: .claude/skills/mvt-test/SKILL.md
-
-frontmatter:
-  name: mvt-test
-  description: "Generate and design tests to validate implementations. This skill should be used when user wants to write tests, validate code, generate test cases, or analyze test coverage."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Test
-
-      ## Purpose
-
-      Design and write tests to validate implementations against requirements and business rules. Ensure code works correctly with comprehensive coverage of happy paths, edge cases, and error scenarios.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Tester
-      role_desc: "a Quality Assurance Specialist"
-      decision_rules:
-        - rule: "Happy path works -> Add edge case and boundary tests"
-        - rule: "Bug found during testing -> Document with reproduction steps, suggest `/mvt-fix`"
-        - rule: "Coverage gap found -> Add tests focused on that area"
-        - rule: "Flaky test detected -> Flag for investigation"
-        - rule: "Test requires external service -> Use mocks/stubs, document the dependency"
-        - rule: "Security constraints in requirements -> Add security-focused test cases"
-        - rule: "Existing tests conflict with new implementation -> Flag the conflict"
-      boundaries:
-        - scope: "modify the code being tested"
-          skill: "/mvt-fix"
-        - scope: "make architecture decisions"
-          skill: "(Test against existing design)"
-        - scope: "skip edge cases or negative tests"
-          skill: "(Never)"
-
-  - type: inline
-    content: |
-      ## Variants
-
-      | Variant | Description |
-      |---------|-------------|
-      | `/mvt-test` | Generate tests for recent implementation |
-      | `/mvt-test {feature}` | Generate tests for specific feature |
-      | `/mvt-test --coverage` | Generate tests with coverage analysis |
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - "Implementation files to be tested"
-
-  - 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 implementation files"
-          level: "WARN"
-          message: "No implementation found. Run `/mvt-implement` first."
-
-  - type: inline
-    content: |
-      ## Test Case Types
-
-      | Type | Description | Priority |
-      |------|-------------|----------|
-      | Happy Path | Normal successful flow | High |
-      | Edge Case | Boundary conditions | High |
-      | Negative | Invalid inputs, errors | High |
-      | Security | Authentication, injection | Medium |
-      | Performance | Load, stress | Low |
-
-  - type: file
-    source: ./business.md
-
-  - type: inline
-    content: |
-      ## Artifact Structure
-      Read the document structure template from: `.ai-agents/skills/_templates/test-output.md`
-      If a custom version exists at `.ai-agents/skills/_templates/custom/test-output.md`, use the custom version instead.
-      The template defines section headings only. Generate content for each section based on test design results.
-      Write the artifact to: `.ai-agents/workspace/artifacts/{change-id}/tests/test-design.md`
-
-  - type: shared
-    source: sections/session-update.md
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-test
+name: mvt-test
+output: .claude/skills/mvt-test/SKILL.md
+
+frontmatter:
+  name: mvt-test
+  description: "Generate and design tests to validate implementations. This skill should be used when user wants to write tests, validate code, generate test cases, or analyze test coverage."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Test
+
+      ## Purpose
+
+      Design and write tests to validate implementations against requirements and business rules. Ensure code works correctly with comprehensive coverage of happy paths, edge cases, and error scenarios.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Tester
+      role_desc: "a Quality Assurance Specialist"
+      decision_rules:
+        - rule: "Happy path works -> Add edge case and boundary tests"
+        - rule: "Bug found during testing -> Document with reproduction steps, suggest `/mvt-fix`"
+        - rule: "Coverage gap found -> Add tests focused on that area"
+        - rule: "Flaky test detected -> Flag for investigation"
+        - rule: "Test requires external service -> Use mocks/stubs, document the dependency"
+        - rule: "Security constraints in requirements -> Add security-focused test cases"
+        - rule: "Existing tests conflict with new implementation -> Flag the conflict"
+      boundaries:
+        - scope: "modify the code being tested"
+          skill: "/mvt-fix"
+        - scope: "make architecture decisions"
+          skill: "(Test against existing design)"
+        - scope: "skip edge cases or negative tests"
+          skill: "(Never)"
+
+  - type: inline
+    content: |
+      ## Variants
+
+      | Variant | Description |
+      |---------|-------------|
+      | `/mvt-test` | Generate tests for recent implementation |
+      | `/mvt-test {feature}` | Generate tests for specific feature |
+      | `/mvt-test --coverage` | Generate tests with coverage analysis |
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - "Implementation files to be tested"
+
+  - 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 implementation files"
+          level: "WARN"
+          message: "No implementation found. Run `/mvt-implement` first."
+
+  - type: inline
+    content: |
+      ## Test Case Types
+
+      | Type | Description | Priority |
+      |------|-------------|----------|
+      | Happy Path | Normal successful flow | High |
+      | Edge Case | Boundary conditions | High |
+      | Negative | Invalid inputs, errors | High |
+      | Security | Authentication, injection | Medium |
+      | Performance | Load, stress | Low |
+
+  - type: file
+    source: ./business.md
+
+  - type: inline
+    content: |
+      ## Artifact Structure
+      Read the document structure template from: `.ai-agents/skills/_templates/test-output.md`
+      If a custom version exists at `.ai-agents/skills/_templates/custom/test-output.md`, use the custom version instead.
+      The template defines section headings only. Generate content for each section based on test design results.
+      Write the artifact to: `.ai-agents/workspace/artifacts/{change-id}/tests/test-design.md`
+
+  - type: shared
+    source: sections/session-update.md
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-test