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

package/sources/sections/session-update.md

@@ -1,47 +1,47 @@
-{{?read_only}}
-## State Update
-
-This skill is read-only and does NOT modify `.ai-agents/workspace/session.yaml`. No state mutation, no `skill_history` append, no `recent_actions` append.
-{{/read_only}}
-{{^read_only}}
-## State Update (Required)
-
-After execution, update `.ai-agents/workspace/session.yaml` with the following fields.
-
-### Mandatory (every skill must set)
-
-- `session.last_command`: Set to the current skill command (e.g., `"/mvt-analyze"`)
-- `skill_history`: Append entry:
-  ```yaml
-  - command: "/{skill-name}"
-    completed_at: "{current timestamp ISO 8601}"
-    summary: "{one-line summary of what was accomplished}"
-    change_id: "{active_change.id if set, otherwise empty string}"
-  ```
-  Keep max 10 entries. If exceeds, drop the oldest. The `change_id` field enables `/mvt-resume` to filter history per change when multiple changes are in flight.
-- `recent_actions`: Append one-line summary with format:
-  `[{YYYY-MM-DD HH:MM}] /{command}: {one-line summary}`
-  Keep max 5 entries. If exceeds, drop the oldest.
-{{#update_active_change}}
-
-### Conditional (set only when applicable)
-
-- `active_change.id`: Set when this skill creates a new change
-- `active_change.title`: Set when this skill creates a new change
-- `active_change.created_at`: Set when this skill creates a new change
-{{/update_active_change}}
-{{#update_initialized_at}}
-
-### Conditional (set only when applicable)
-
-- `session.initialized_at`: Set to current timestamp when this skill initializes the project
-{{/update_initialized_at}}
-
-### Forbidden
-
-- Do NOT update fields not listed above
-- Do NOT overwrite `active_change` unless this skill creates a new change
-- Do NOT modify `skill_history` entries other than appending a new one
-- Do NOT modify `recent_changes` -- it is owned by `/mvt-plan-dev` and `/mvt-update-plan`
-- Do NOT modify `active_change.plan_path` or `active_change.has_plan` -- these are owned by `/mvt-plan-dev`
-{{/read_only}}
+{{?read_only}}
+## State Update
+
+This skill is read-only and does NOT modify `.ai-agents/workspace/session.yaml`. No state mutation, no `skill_history` append, no `recent_actions` append.
+{{/read_only}}
+{{^read_only}}
+## State Update (Required)
+
+After execution, update `.ai-agents/workspace/session.yaml` with the following fields.
+
+### Mandatory (every skill must set)
+
+- `session.last_command`: Set to the current skill command (e.g., `"/mvt-analyze"`)
+- `skill_history`: Append entry:
+  ```yaml
+  - command: "/{skill-name}"
+    completed_at: "{current timestamp ISO 8601}"
+    summary: "{one-line summary of what was accomplished}"
+    change_id: "{active_change.id if set, otherwise empty string}"
+  ```
+  Keep max 10 entries. If exceeds, drop the oldest. The `change_id` field enables `/mvt-resume` to filter history per change when multiple changes are in flight.
+- `recent_actions`: Append one-line summary with format:
+  `[{YYYY-MM-DD HH:MM}] /{command}: {one-line summary}`
+  Keep max 5 entries. If exceeds, drop the oldest.
+{{#update_active_change}}
+
+### Conditional (set only when applicable)
+
+- `active_change.id`: Set when this skill creates a new change
+- `active_change.title`: Set when this skill creates a new change
+- `active_change.created_at`: Set when this skill creates a new change
+{{/update_active_change}}
+{{#update_initialized_at}}
+
+### Conditional (set only when applicable)
+
+- `session.initialized_at`: Set to current timestamp when this skill initializes the project
+{{/update_initialized_at}}
+
+### Forbidden
+
+- Do NOT update fields not listed above
+- Do NOT overwrite `active_change` unless this skill creates a new change
+- Do NOT modify `skill_history` entries other than appending a new one
+- Do NOT modify `recent_changes` -- it is owned by `/mvt-plan-dev` and `/mvt-update-plan`
+- Do NOT modify `active_change.plan_path` or `active_change.has_plan` -- these are owned by `/mvt-plan-dev`
+{{/read_only}}

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

@@ -10,7 +10,7 @@
 - Extract business rules and constraints
 - Note assumptions made
 
-### Step 2.5: Assess Complexity (Quick Path Detection)
+### Step 3: Assess Complexity (Quick Path Detection)
 - **What**: evaluate whether this requirement qualifies as a simple change suitable for the quick development path via `/mvt-quick-dev`.
 - **How**: check each criterion in the table below. ALL criteria must pass for the quick path to be offered.
 
@@ -40,30 +40,30 @@
     - Scope: ✗ touches auth middleware, user model, login UI, OAuth callback handler, config (5+ files)
     - No new concepts: ✗ introduces external IdP and OAuth callback contract
     - No integration concerns: ✗ new external dependency (Google IdP)
-    → Proceed with standard analysis flow (Steps 3-5).
+    → Proceed with standard analysis flow (Steps 4-6).
 
 - **Branches**:
 
   | Condition | Action |
   |-----------|--------|
   | ALL criteria pass | Ask user: "This appears to be a simple change (1-3 files, no architectural impact). Use /mvt-quick-dev for faster execution? (y / n / show-criteria)" |
-  | ANY criterion fails | Proceed with standard analysis flow (Steps 3-5) |
+  | ANY criterion fails | Proceed with standard analysis flow (Steps 4-6) |
   | Ambiguous (2-3 criteria unclear) | Proceed with standard analysis; do NOT offer quick path |
 
 - **On user choice**:
   - "y" -- Do NOT write an analysis artifact. Summarize the requirement understanding in conversation and recommend `/mvt-quick-dev` directly. Set `active_change` if one doesn't exist, so `/mvt-quick-dev` can reference the current work context.
-  - "n" -- Continue with full analysis flow (Steps 3-5).
+  - "n" -- Continue with full analysis flow (Steps 4-6).
   - "show-criteria" -- Display the assessment results (pass/fail per criterion), then re-prompt with y/n.
 
-### Step 3: Detect Ambiguities
+### Step 4: Detect Ambiguities
 - Check for unclear requirements
 - Check for missing information
 - Check for conflicting requirements
 
-### Step 4: Generate Clarification Questions
+### Step 5: Generate Clarification Questions
 - If ambiguities found -> List each with specific question, prioritized by impact
 - If no ambiguities -> Skip this step
 
-### Step 5: Update Workspace
+### Step 6: Update Workspace
 1. Generate change-id: `{YYYYMMDD}-{slug}` format (e.g., `20260425-user-authentication`)
 2. Write artifact: `.ai-agents/workspace/artifacts/{change-id}/analysis.md`

package/sources/skills/mvt-analyze-code/manifest.yaml

@@ -1,96 +1,96 @@
-name: mvt-analyze-code
-output: .claude/skills/mvt-analyze-code/SKILL.md
-
-frontmatter:
-  name: mvt-analyze-code
-  description: "Analyze existing code to generate project-context.md with terms, modules, layers, and business rules. This skill should be used when user wants to understand an existing codebase, generate documentation for legacy code, onboard to a new project, or extract requirements from source code."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Analyze Code
-
-      ## Purpose
-
-      Analyze existing code to generate the project-context.md file, which describes the project's terms, modules, layer structure, business rules, and API overview. This is an independent operation that does not create a change-id.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Analyst
-      role_desc: "a Code Analysis Expert"
-      decision_rules:
-        - rule: "Source code exists -> Proceed with codebase scanning"
-        - rule: "No source code found -> Warn user and suggest checking project path"
-        - rule: "Multiple frameworks detected -> List all and prompt for primary confirmation"
-        - rule: "Custom template exists -> Use it instead of default template"
-      boundaries:
-        - scope: "make architecture decisions"
-          skill: "/mvt-design"
-        - scope: "recommend technologies"
-          skill: "/mvt-design"
-        - scope: "write implementation code"
-          skill: "/mvt-implement"
-
-  - type: inline
-    content: |
-      ## Variants
-
-      | Variant | Description |
-      |---------|-------------|
-      | `/mvt-analyze-code` | Analyze the first (or only) project |
-      | `/mvt-analyze-code --all` | Analyze all projects in the workspace |
-      | `/mvt-analyze-code {name}` | Analyze a specific project by name |
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - "Scan project source directories for analysis"
-        - ".ai-agents/skills/_templates/project-context.md -- Default template for output structure"
-        - ".ai-agents/skills/_templates/custom/project-context.md -- Custom template (if exists)"
-
-  - 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: "projects[] in project-context.yaml"
-          level: "WARN"
-          message: "No projects registered. Run `/mvt-init` first."
-
-  - type: inline
-    content: |
-      ### Independent Operation Rules
-      - This is an independent operation -- no workflow prerequisites required
-      - Does NOT create a change-id
-      - Output is written to `.ai-agents/knowledge/project/_generated/project-context.md`
-
-  - type: file
-    source: ./business.md
-
-  - type: inline
-    content: |
-      ## Artifact Structure
-      Read the document structure template from: `.ai-agents/skills/_templates/project-context.md`
-      If a custom version exists at `.ai-agents/skills/_templates/custom/project-context.md`, use the custom version instead.
-      The template defines section headings only. Generate content for each section based on code analysis results.
-      Write the artifact to: `.ai-agents/knowledge/project/_generated/project-context.md`
-
-  - type: shared
-    source: sections/session-update.md
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-analyze-code
+name: mvt-analyze-code
+output: .claude/skills/mvt-analyze-code/SKILL.md
+
+frontmatter:
+  name: mvt-analyze-code
+  description: "Analyze existing code to generate project-context.md with terms, modules, layers, and business rules. This skill should be used when user wants to understand an existing codebase, generate documentation for legacy code, onboard to a new project, or extract requirements from source code."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Analyze Code
+
+      ## Purpose
+
+      Analyze existing code to generate the project-context.md file, which describes the project's terms, modules, layer structure, business rules, and API overview. This is an independent operation that does not create a change-id.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Analyst
+      role_desc: "a Code Analysis Expert"
+      decision_rules:
+        - rule: "Source code exists -> Proceed with codebase scanning"
+        - rule: "No source code found -> Warn user and suggest checking project path"
+        - rule: "Multiple frameworks detected -> List all and prompt for primary confirmation"
+        - rule: "Custom template exists -> Use it instead of default template"
+      boundaries:
+        - scope: "make architecture decisions"
+          skill: "/mvt-design"
+        - scope: "recommend technologies"
+          skill: "/mvt-design"
+        - scope: "write implementation code"
+          skill: "/mvt-implement"
+
+  - type: inline
+    content: |
+      ## Variants
+
+      | Variant | Description |
+      |---------|-------------|
+      | `/mvt-analyze-code` | Analyze the first (or only) project |
+      | `/mvt-analyze-code --all` | Analyze all projects in the workspace |
+      | `/mvt-analyze-code {name}` | Analyze a specific project by name |
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - "Scan project source directories for analysis"
+        - ".ai-agents/skills/_templates/project-context.md -- Default template for output structure"
+        - ".ai-agents/skills/_templates/custom/project-context.md -- Custom template (if exists)"
+
+  - 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: "projects[] in project-context.yaml"
+          level: "WARN"
+          message: "No projects registered. Run `/mvt-init` first."
+
+  - type: inline
+    content: |
+      ### Independent Operation Rules
+      - This is an independent operation -- no workflow prerequisites required
+      - Does NOT create a change-id
+      - Output is written to `.ai-agents/knowledge/project/_generated/project-context.md`
+
+  - type: file
+    source: ./business.md
+
+  - type: inline
+    content: |
+      ## Artifact Structure
+      Read the document structure template from: `.ai-agents/skills/_templates/project-context.md`
+      If a custom version exists at `.ai-agents/skills/_templates/custom/project-context.md`, use the custom version instead.
+      The template defines section headings only. Generate content for each section based on code analysis results.
+      Write the artifact to: `.ai-agents/knowledge/project/_generated/project-context.md`
+
+  - type: shared
+    source: sections/session-update.md
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-analyze-code

package/sources/skills/mvt-bug-detect/business.md

@@ -0,0 +1,101 @@
+## Execution Flow
+
+### Step 1: Receive & Complete Input
+- Read the user-provided bug description (free text, possibly with stack trace, error message, or reproduction steps).
+- Assess input completeness using the table below:
+
+  | Input Situation | Action |
+  |-----------------|--------|
+  | No input provided | Present a structured template and wait. Template fields: **Error message**, **Reproduction steps**, **Expected behavior**, **Actual behavior**, **Environment** |
+  | Only error message | Ask: trigger conditions, runtime environment, recent changes |
+  | Only behavioral description (no error) | Ask: any error message available, whether it reproduces reliably, affected scope |
+  | Stack trace present | Sufficient — proceed to Step 2 |
+  | Reproduction steps + error message | Sufficient — proceed to Step 2 |
+
+- When asking for clarification, be specific. Do NOT ask "can you provide more details?" — instead, name the exact missing dimension (e.g., "What error message do you see when this happens?").
+
+### Step 2: Signal Extraction & Localization
+- Extract concrete signals from the bug description: error message text, stack trace frames, file paths, function/class names, input data.
+- For each signal, locate matching code (Grep / Glob).
+- Build a candidate file list with one-line justification per file.
+- Read recent git state (`git diff HEAD`, `git log -n 10 --oneline`) to surface recent changes that may correlate with the issue.
+
+### Step 3: Reproduction Verification
+
+| Condition | Action |
+|-----------|--------|
+| Reproduction steps provided → successfully reproduced | Mark as `Verified`, capture observed vs expected behavior |
+| Reproduction steps provided → cannot reproduce | Mark as `Unverified`, continue with static analysis only |
+| No reproduction steps, but signals are concrete (stack trace + paths) | Continue with static analysis, mark as `Static-only` |
+| No reproduction steps, signals are vague | STOP — ask user for: minimal reproduction, exact error, environment, last-known-good version |
+
+### Step 4: Root Cause Analysis
+- Generate 1-5 candidate root cause hypotheses based on the dominant signal:
+
+  | Dominant Signal | Hypothesis Sources |
+  |-----------------|--------------------|
+  | Stack trace | Top frame in user code, recently changed code in any frame, null/undefined origin, type mismatch at boundary |
+  | Error message | Exact-string search in repo, typed exception class hierarchy, library docs for that error |
+  | Recent git diff | Files changed in last N commits intersecting with localized files, commit messages mentioning related modules |
+  | Behavioral description (no error) | Module boundary mismatches, off-by-one / null-handling, async/race, state leakage, configuration drift |
+
+- Each hypothesis must be written as: `<claim> -- evidence: <pointer> -- check: <how to verify>`.
+- Verify hypotheses from cheapest check to most expensive. Eliminate hypotheses that fail their checks.
+- If ALL hypotheses are eliminated — STOP, surface findings, request more info from user. Do NOT fabricate new hypotheses silently.
+
+### Step 5: Impact Assessment & Classification
+
+**Bug Confirmation Status:**
+
+| Status | Meaning |
+|--------|---------|
+| Confirmed | Root cause verified, bug definitely exists |
+| Likely | Evidence is strong but cannot fully rule out other possibilities |
+| NotABug | Actual behavior matches expected behavior / business rules — not a bug |
+| Inconclusive | Insufficient evidence, requires human judgment |
+
+**Severity:**
+
+| Level | Definition |
+|-------|------------|
+| Critical | Data loss, security vulnerability, core functionality broken |
+| High | Major feature broken but temporary workaround exists |
+| Medium | Minor feature broken or usability issue |
+| Low | Edge case issue, no significant impact on main flow |
+
+**Impact Scope:**
+- List affected modules/files with one-line description each.
+- List affected user scenarios / business flows.
+- Search for similar patterns elsewhere in the codebase (same root cause may exist in other locations).
+
+### Step 6: Present Diagnosis
+- Output the diagnosis in conversation using this format:
+
+  ```
+  Bug Detection Result
+  ─────────────────────
+  Status:      <Confirmed | Likely | NotABug | Inconclusive>
+  Severity:    <Critical | High | Medium | Low>
+  Root Cause:  <one paragraph>
+  Confidence:  <reasoning for the status judgment>
+  Impact:      <affected modules and scenarios>
+  Affected:    <file list with line ranges>
+  Similar:     <other locations that may have the same root cause>
+  ─────────────────────
+  ```
+
+- For `NotABug`: explain why the current behavior is expected, and suggest `/mvt-analyze` if the requirement itself needs revision.
+- For `Inconclusive`: summarize what was found and what remains unknown, so the user or `/mvt-fix` can act with full awareness.
+
+### Step 7: (session update handled by shared section)
+
+## Edge Cases & Errors
+
+| Case | Handling |
+|------|----------|
+| Bug is intermittent / racy | Mark reproduction as "flaky", state confidence level explicitly, suggest adding instrumentation rather than speculative analysis |
+| Root cause is in a third-party dependency | Document the upstream issue, note that local workaround would be the only fix option |
+| Bug description describes expected behavior (NotABug) | Explain clearly with evidence from code/business rules, do NOT proceed to suggest fixes |
+| Multiple independent bugs described in one input | Analyze each separately, present multiple diagnosis blocks |
+| User provides a URL or external reference | Note it but do NOT fetch external resources; work only with local code and the description text |
+| `active_change` is missing | Run without change context (shortcut mode); omit change-id references in output |

package/sources/skills/mvt-bug-detect/manifest.yaml

@@ -0,0 +1,84 @@
+name: mvt-bug-detect
+output: .claude/skills/mvt-bug-detect/SKILL.md
+
+frontmatter:
+  name: mvt-bug-detect
+  description: "Analyze and detect bugs by investigating root cause, assessing severity and impact scope. Produces a structured diagnosis in conversation without applying fixes. This skill should be used when user suspects a bug, wants to understand a problem before fixing, or needs impact analysis."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Bug Detect
+
+      ## Purpose
+
+      Investigate suspected bugs: confirm whether the bug exists, identify root cause, assess severity and impact scope, and produce a structured diagnosis. This skill does NOT apply fixes — it provides analysis to help the user understand the problem and decide on next steps.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Analyst
+      role_desc: "a Bug Investigation Specialist"
+      decision_rules:
+        - rule: "Bug description provided -> Analyze and investigate"
+        - rule: "Input too vague -> Prompt for specific details with structured template"
+        - rule: "No input -> Provide input template and wait"
+        - rule: "Root cause confirmed -> Assess impact and produce diagnosis"
+        - rule: "Multiple possible causes -> List hypotheses with evidence, verify each"
+        - rule: "Bug does not exist (expected behavior) -> Report clearly, suggest /mvt-analyze if requirement gap"
+        - rule: "Evidence insufficient -> Report findings, request more info, do NOT fabricate hypotheses"
+      boundaries:
+        - scope: "apply fixes"
+          skill: "/mvt-fix"
+        - scope: "design architecture"
+          skill: "/mvt-design"
+        - scope: "review code quality"
+          skill: "/mvt-review"
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - "Related source files (load based on bug description signals)"
+
+  - 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 write any artifact — diagnosis is presented in conversation only
+      - Do NOT modify any source code — this skill is read-only analysis
+
+  - type: file
+    source: ./business.md
+
+  - type: shared
+    source: sections/session-update.md
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-bug-detect
+      conditional_suggestions:
+        conditions:
+          - condition: "bug confirmed, fix is straightforward"
+            primary: "mvt-fix"
+            primary_desc: "Fix this bug"
+          - condition: "bug confirmed, fix requires architecture change"
+            primary: "mvt-design"
+            primary_desc: "Design architectural solution first"
+            alternatives:
+              - skill: "mvt-fix"
+                desc: "Apply a minimal workaround"
+          - condition: "not a bug (expected behavior)"
+            primary: "mvt-analyze"
+            primary_desc: "Re-analyze the underlying requirement"
+          - condition: "inconclusive, needs deeper code understanding"
+            primary: "mvt-analyze-code"
+            primary_desc: "Deep-dive into the codebase"

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

@@ -1,63 +1,63 @@
-name: mvt-check-context
-output: .claude/skills/mvt-check-context/SKILL.md
-
-frontmatter:
-  name: mvt-check-context
-  description: "Analyze context token load and provide optimization recommendations. This skill should be used when user wants to check how much context MVTT loads, identify large files, or optimize workspace size for better performance."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Context Check
-
-      ## Purpose
-
-      Analyze the total context information that MVTT loads at runtime, estimate token consumption, assess health status, and provide actionable optimization recommendations.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Conductor
-      role_desc: "a Workflow Coordinator"
-      decision_rules:
-        - rule: "Total tokens < 5,000 -> Report as \"Good\""
-        - rule: "Total tokens 5,000-15,000 -> Report as \"Moderate\""
-        - rule: "Total tokens 15,000-30,000 -> Report as \"High\", suggest optimizations"
-        - rule: "Total tokens > 30,000 -> Report as \"Overloaded\", strongly recommend cleanup"
-      boundaries:
-        - scope: "modify any files"
-          skill: "(Only analyze and recommend)"
-        - scope: "clean up artifacts"
-          skill: "/mvt-cleanup"
-        - scope: "modify context"
-          skill: "/mvt-manage-context"
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - ".ai-agents/config.yaml -- Framework configuration (to be scanned for size)"
-
-  - 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-check-context
+name: mvt-check-context
+output: .claude/skills/mvt-check-context/SKILL.md
+
+frontmatter:
+  name: mvt-check-context
+  description: "Analyze context token load and provide optimization recommendations. This skill should be used when user wants to check how much context MVTT loads, identify large files, or optimize workspace size for better performance."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Context Check
+
+      ## Purpose
+
+      Analyze the total context information that MVTT loads at runtime, estimate token consumption, assess health status, and provide actionable optimization recommendations.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Conductor
+      role_desc: "a Workflow Coordinator"
+      decision_rules:
+        - rule: "Total tokens < 5,000 -> Report as \"Good\""
+        - rule: "Total tokens 5,000-15,000 -> Report as \"Moderate\""
+        - rule: "Total tokens 15,000-30,000 -> Report as \"High\", suggest optimizations"
+        - rule: "Total tokens > 30,000 -> Report as \"Overloaded\", strongly recommend cleanup"
+      boundaries:
+        - scope: "modify any files"
+          skill: "(Only analyze and recommend)"
+        - scope: "clean up artifacts"
+          skill: "/mvt-cleanup"
+        - scope: "modify context"
+          skill: "/mvt-manage-context"
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - ".ai-agents/config.yaml -- Framework configuration (to be scanned for size)"
+
+  - 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-check-context