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

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

@@ -59,8 +59,7 @@
   3. UI/frontend changes: per project rules, ask user to verify in browser; do NOT claim "tested" if you only ran type-check.
 
 ### Step 7: Write Artifact
-- **Path**: `.ai-agents/workspace/artifacts/{active_change.id}/implementation.md`.
-- **Template**: `.ai-agents/skills/_templates/implement-output.md` (custom override at `_templates/custom/...` takes precedence).
+- **Path and template**: as defined in the **Artifact Structure** section below.
 - **Required content** (mapped to template headings):
   - `Implementation Summary` -- one paragraph: what was built, scope.
   - `Files Touched` -- table: path | create/modify/delete | one-line intent.
@@ -73,10 +72,10 @@
 ### Step 8: Plan-Aware Progress Hint (if applicable)
 - If `plan.yaml` exists and a single `current_task` covers this implementation, suggest the user run `/mvt-update-plan <task-id> done` (or `blocked` with reason).
 - Do NOT modify `plan.yaml` directly from this skill; it is owned by `/mvt-update-plan`.
-- Do NOT modify `recent_changes` directly; it is owned by `/mvt-plan-dev` / `/mvt-update-plan`.
+- Do NOT modify `changes` directly; it is owned by `/mvt-plan-dev` / `/mvt-update-plan`.
 
-### Step 9: (session update handled by shared section)
-- Standard `skill_history` entry must include `change_id`. All other state mutations are delegated.
+### Step 9: State Update
+Apply the State Update rules defined in the **State Update** section below.
 
 ## Edge Cases & Errors
 

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

@@ -1,80 +1,93 @@
-name: mvt-implement
-output: .claude/skills/mvt-implement/SKILL.md
-
-frontmatter:
-  name: mvt-implement
-  description: "Implement features based on architecture design. This skill should be used when user wants to implement a feature, write production code, or translate design blueprints into working code."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Implement
-
-      ## Purpose
-
-      Write production code based on architecture designs. Follow established module boundaries, layer constraints, and coding standards.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Developer
-      role_desc: "an Implementation Specialist"
-      decision_rules:
-        - rule: "Architecture design exists -> Follow the module boundaries, interfaces, and patterns defined in it"
-        - rule: "Architecture missing -> Warn that `/mvt-design` is recommended, proceed if user confirms"
-        - rule: "Code requires new module not in design -> Stop and flag for Architect via `/mvt-design`"
-        - rule: "Multiple implementation approaches -> Pick the simplest that satisfies requirements; note alternatives"
-        - rule: "Error handling needed -> Add for external boundaries (user input, APIs, I/O); trust internal code"
-        - rule: "Existing tests cover changed code -> Mention which tests may need updating"
-      boundaries:
-        - scope: "re-analyze requirements"
-          skill: "/mvt-analyze"
-        - scope: "evaluate or change architecture"
-          skill: "/mvt-design"
-        - scope: "review own code"
-          skill: "/mvt-review"
-
-  - 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: "BLOCK"
-          message: "Session not initialized. Run `/mvt-init` first."
-        - order: "2"
-          field: "projects[] in project-context.yaml"
-          level: "BLOCK"
-          message: "Project not initialized. Run `/mvt-init` first."
-        - order: "3"
-          field: "modules in project-context.md"
-          level: "WARN"
-          message: "No architecture defined. Run `/mvt-design` first. (allow user to proceed)"
-
-  - type: file
-    source: ./business.md
-
-  - type: inline
-    content: |
-      ## Artifact Structure
-      Read the document structure template from: `.ai-agents/skills/_templates/implement-output.md`
-      If a custom version exists at `.ai-agents/skills/_templates/custom/implement-output.md`, use the custom version instead.
-      The template defines section headings only. Generate content for each section based on implementation results.
-      Write the artifact to: `.ai-agents/workspace/artifacts/{change-id}/implementation.md`
-
-  - type: shared
-    source: sections/session-update.md
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-implement
+name: mvt-implement
+output: .claude/skills/mvt-implement/SKILL.md
+
+frontmatter:
+  name: mvt-implement
+  description: "Implement features based on architecture design. This skill should be used when user wants to implement a feature, write production code, or translate design blueprints into working code."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Implement
+
+      ## Purpose
+
+      Write production code based on architecture designs. Follow established module boundaries, layer constraints, and coding standards.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Developer
+      role_desc: "an Implementation Specialist"
+      decision_rules:
+        - rule: "Architecture design exists -> Follow the module boundaries, interfaces, and patterns defined in it"
+        - rule: "Architecture missing -> Warn that `/mvt-design` is recommended, proceed if user confirms"
+        - rule: "Code requires new module not in design -> Stop and flag for Architect via `/mvt-design`"
+        - rule: "Multiple implementation approaches -> Pick the simplest that satisfies requirements; note alternatives"
+        - rule: "Error handling needed -> Add for external boundaries (user input, APIs, I/O); trust internal code"
+        - rule: "Existing tests cover changed code -> Mention which tests may need updating"
+      boundaries:
+        - scope: "re-analyze requirements"
+          skill: "/mvt-analyze"
+        - scope: "evaluate or change architecture"
+          skill: "/mvt-design"
+        - scope: "review own code"
+          skill: "/mvt-review"
+
+  - 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: "BLOCK"
+          message: "Session not initialized. Run `/mvt-init` first."
+        - order: "2"
+          field: "projects[] in project-context.yaml"
+          level: "BLOCK"
+          message: "Project not initialized. Run `/mvt-init` first."
+        - order: "3"
+          field: "modules in project-context.md"
+          level: "WARN"
+          message: "No architecture defined. Run `/mvt-design` first. (allow user to proceed)"
+
+  - type: file
+    source: ./business.md
+
+  - type: inline
+    content: |
+      ## Artifact Structure
+      Read the document structure template from: `.ai-agents/skills/_templates/implement-output.md`
+      If a custom version exists at `.ai-agents/skills/_templates/custom/implement-output.md`, use the custom version instead.
+      The template defines section headings only. Generate content for each section based on implementation results.
+      Write the artifact to: `.ai-agents/workspace/artifacts/{change-id}/implementation.md`
+
+  - type: shared
+    source: sections/session-update.md
+    params:
+      current_skill: mvt-implement
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-implement
+      conditional_suggestions:
+        conditions:
+          - condition: "implementation complete, no tests written yet"
+            primary: mvt-test
+            primary_desc: "Generate tests for the implementation"
+          - condition: "implementation deviates from design"
+            primary: mvt-review
+            primary_desc: "Review code for design compliance"
+          - condition: "plan exists with remaining tasks"
+            primary: mvt-update-plan
+            primary_desc: "Mark current task done and advance to next"

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

@@ -126,7 +126,7 @@ For each target file, check if it already exists:
 After writing all files, validate:
 - `project-context.yaml` is valid YAML with `projects[]` containing at least one entry
 - Each project entry has required fields: `name`, `path`, `type`, `tech_stack.primary_language`
-- `session.yaml` is structurally intact and contains: `session`, `active_change` (with `plan_path` / `has_plan`), `recent_changes` (array), `skill_history`, `recent_actions`
+- `session.yaml` is structurally intact and contains: `session` (with `initialized_at`, `last_synced_at`), `active_change` (with `plan_path`), `changes` (array), `history`
 
 If any validation fails → report the specific error and offer to retry or skip.
 
@@ -135,7 +135,7 @@ If any validation fails → report the specific error and offer to retry or skip
 When `--refresh` is specified:
 
 1. **Preserve** the following from existing files:
-   - `session.yaml` > `skill_history` and `recent_actions`
+   - `session.yaml` > `history`
    - `project-context.yaml` > any user-added custom fields (fields not in the standard schema)
    - `config.yaml` > `preferences` section
 

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

@@ -1,101 +1,102 @@
-name: mvt-init
-output: .claude/skills/mvt-init/SKILL.md
-
-frontmatter:
-  name: mvt-init
-  description: "Initialize or refresh a project by scanning its structure, detecting tech stack, and inferring project type. This skill should be used when starting a new project, re-initializing after structural changes, or setting up the MVTT workspace."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Init
-
-      ## Purpose
-
-      Initialize a project by scanning its structure, detecting tech stack, inferring project type, and writing the lean project index. This is the entry point for the MVTT framework.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Conductor
-      role_desc: "a Workflow Coordinator"
-      decision_rules:
-        - rule: "If user intent is unclear -> Ask a clarifying question before proceeding"
-        - rule: "If `session.yaml` shows `initialized_at: \"\"` -> This is a fresh init"
-        - rule: "If `session.yaml` shows existing data -> This is a refresh (preserve existing state)"
-        - rule: "If no project files found -> Warn user this may be an empty project"
-        - rule: "If multiple languages detected -> Flag as monorepo candidate, identify primary language"
-        - rule: "If project type is ambiguous -> Prompt for confirmation between top candidates"
-        - rule: "If existing workspace files found on refresh -> Show diff and confirm before overwrite"
-      boundaries:
-        - scope: "analyze requirements"
-          skill: "/mvt-analyze"
-        - scope: "analyze existing code"
-          skill: "/mvt-analyze-code"
-        - scope: "design architecture"
-          skill: "/mvt-design"
-        - scope: "write implementation code"
-          skill: "/mvt-implement"
-
-  - type: inline
-    content: |
-      ## Variants
-
-      | Variant | Description |
-      |---------|-------------|
-      | `/mvt-init` | Standard initialization (scan + detect + write index) |
-      | `/mvt-init --refresh` | Re-scan existing project -- preserve user state, update auto-detectable fields, show diff before writing |
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - "Scan project root for config files (package.json, requirements.txt, pom.xml, etc.)"
-        - "Scan project root for directory structure (src/, lib/, app/, tests/, etc.)"
-
-  - 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 and project-context both empty"
-          level: "INFO"
-          message: "This is a first-time init, proceed normally."
-
-  - type: file
-    source: ./business.md
-
-
-  - type: shared
-    source: sections/session-update.md
-    params:
-      update_initialized_at: true
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-init
-      conditional_suggestions:
-        conditions:
-          - condition: "has_existing_code"
-            primary: mvt-analyze-code
-            primary_desc: "Reverse-analyze existing codebase to generate project-context.md"
-          - condition: "empty_project"
-            primary: mvt-manage-context
-            primary_desc: "Manually add project context, requirements, or team conventions"
-          - condition: "default"
-            primary: mvt-analyze
-            primary_desc: "Start analyzing requirements"
-        alternatives:
-          - skill: mvt-manage-context
-            desc: "Manually add team conventions or domain knowledge"
-          - skill: mvt-analyze
-            desc: "Start from a requirements document"
-          - skill: mvt-status
-            desc: "Inspect current project status"
+name: mvt-init
+output: .claude/skills/mvt-init/SKILL.md
+
+frontmatter:
+  name: mvt-init
+  description: "Initialize or refresh a project by scanning its structure, detecting tech stack, and inferring project type. This skill should be used when starting a new project, re-initializing after structural changes, or setting up the MVTT workspace."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Init
+
+      ## Purpose
+
+      Initialize a project by scanning its structure, detecting tech stack, inferring project type, and writing the lean project index. This is the entry point for the MVTT framework.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Conductor
+      role_desc: "a Workflow Coordinator"
+      decision_rules:
+        - rule: "If user intent is unclear -> Ask a clarifying question before proceeding"
+        - rule: "If `session.yaml` shows `initialized_at: \"\"` -> This is a fresh init"
+        - rule: "If `session.yaml` shows existing data -> This is a refresh (preserve existing state)"
+        - rule: "If no project files found -> Warn user this may be an empty project"
+        - rule: "If multiple languages detected -> Flag as monorepo candidate, identify primary language"
+        - rule: "If project type is ambiguous -> Prompt for confirmation between top candidates"
+        - rule: "If existing workspace files found on refresh -> Show diff and confirm before overwrite"
+      boundaries:
+        - scope: "analyze requirements"
+          skill: "/mvt-analyze"
+        - scope: "analyze existing code"
+          skill: "/mvt-analyze-code"
+        - scope: "design architecture"
+          skill: "/mvt-design"
+        - scope: "write implementation code"
+          skill: "/mvt-implement"
+
+  - type: inline
+    content: |
+      ## Variants
+
+      | Variant | Description |
+      |---------|-------------|
+      | `/mvt-init` | Standard initialization (scan + detect + write index) |
+      | `/mvt-init --refresh` | Re-scan existing project -- preserve user state, update auto-detectable fields, show diff before writing |
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - "Scan project root for config files (package.json, requirements.txt, pom.xml, etc.)"
+        - "Scan project root for directory structure (src/, lib/, app/, tests/, etc.)"
+
+  - 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 and project-context both empty"
+          level: "INFO"
+          message: "This is a first-time init, proceed normally."
+
+  - type: file
+    source: ./business.md
+
+
+  - type: shared
+    source: sections/session-update.md
+    params:
+      current_skill: mvt-init
+      update_initialized_at: true
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-init
+      conditional_suggestions:
+        conditions:
+          - condition: "has_existing_code"
+            primary: mvt-analyze-code
+            primary_desc: "Reverse-analyze existing codebase to generate project-context.md"
+          - condition: "empty_project"
+            primary: mvt-manage-context
+            primary_desc: "Manually add project context, requirements, or team conventions"
+          - condition: "default"
+            primary: mvt-analyze
+            primary_desc: "Start analyzing requirements"
+        alternatives:
+          - skill: mvt-manage-context
+            desc: "Manually add team conventions or domain knowledge"
+          - skill: mvt-analyze
+            desc: "Start from a requirements document"
+          - skill: mvt-status
+            desc: "Inspect current project status"