@uoyo/mvtt 2.0.0-beta.0

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

@@ -0,0 +1,74 @@
+name: mvt-check-context
+output: .claude/skills/mvt-check-context/SKILL.md
+
+frontmatter:
+  name: mvt-check-context
+  description: "Analyze context token load and give optimization recommendations. Use 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-add-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: inline
+    content: |
+      ### Step 3: Pre-flight Checks
+      - No blocking checks required.
+
+      ### Step 4: Execute
+      Proceed to Execution Flow below.
+
+  - type: file
+    source: ./business.md
+
+  - type: inline
+    content: |
+      ## Output Format
+
+      Read and use the output template from: `.ai-agents/skills/_templates/context-check-output.md`
+
+      If a custom version exists at `.ai-agents/skills/_templates/custom/context-check-output.md`, use the custom version instead.
+
+      Fill the template with analysis results.
+
+      Every response MUST end with a Suggested Next Steps section.
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      next_primary: mvt-cleanup
+      next_primary_desc: "Clean up old artifacts to reduce context size"
+      next_alternatives:
+        - skill: mvt-add-context
+          when: "Update project context if information is outdated"

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

@@ -0,0 +1,31 @@
+## Execution Flow
+
+### Step 1: Scan Workspace State
+- Read all files under `.ai-agents/workspace/artifacts/{change-id}/`
+- Read `.ai-agents/workspace/session.yaml`
+- Count total artifact files
+- Estimate token footprint for each file (~characters / 4)
+
+### Step 2: Identify Cleanup Candidates
+- Apply cleanup rules to identify candidates
+- Calculate current size and projected savings for each
+
+### Step 3: Present Cleanup Plan
+Show user what will be cleaned:
+
+| Item | Current Size | Action | Result |
+|------|-------------|--------|--------|
+| {artifact} | ~{tokens} tokens | {action} | ~{reduced} tokens |
+| **Total** | **{total}** | | **{new_total} ({savings} saved)** |
+
+If `--dry-run` flag is set -> Stop here. Do not proceed.
+
+### Step 4: Execute (after user confirmation)
+- Summarize identified artifacts (keep key decisions, remove details)
+- Update `session.yaml` to reflect cleanup
+- Output summary of actions taken
+
+### Step 5: Update Workspace
+1. Update `.ai-agents/workspace/session.yaml`:
+   - Set `session.last_command: "/mvt-cleanup"`
+   - Append one-line summary to `recent_actions` (keep max 3)

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

@@ -0,0 +1,93 @@
+name: mvt-cleanup
+output: .claude/skills/mvt-cleanup/SKILL.md
+
+frontmatter:
+  name: mvt-cleanup
+  description: "Clean up workspace artifacts, summarize old changes, and maintain workspace health. Use when workspace has accumulated old artifacts or to reduce context token footprint."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Cleanup
+
+      ## Purpose
+
+      Clean up workspace artifacts, summarize completed changes, and maintain workspace health. Reduces token footprint by archiving old artifacts and removing stale data.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Conductor
+      role_desc: "a Workflow Coordinator"
+      decision_rules:
+        - rule: "No arguments -> Interactive cleanup (review items before action)"
+        - rule: "`--dry-run` flag -> Show what would be cleaned without taking action"
+        - rule: "Completed changes found -> Summarize and archive"
+        - rule: "Orphaned artifacts found -> List for user review"
+        - rule: "Stale session data found -> Summarize into single entry"
+      boundaries:
+        - scope: "analyze requirements"
+          skill: "/mvt-analyze"
+        - scope: "design architecture"
+          skill: "/mvt-design"
+        - scope: "write implementation code"
+          skill: "/mvt-implement"
+
+  - type: inline
+    content: |
+      ## Variants
+
+      | Variant | Description |
+      |---------|-------------|
+      | `/mvt-cleanup` | Interactive cleanup (review before action) |
+      | `/mvt-cleanup --dry-run` | Preview what would be cleaned |
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - "Scan all files under `.ai-agents/workspace/artifacts/` (all change-id directories)"
+
+  - type: shared
+    source: sections/activation-load-config.md
+
+  - type: shared
+    source: sections/activation-preflight.md
+    params:
+      checks:
+        - order: "1"
+          field: "project not initialized"
+          level: "REQUIRED"
+          message: "Project must be initialized (session.yaml exists)"
+
+  - type: inline
+    content: |
+      ### Step 4: Execute
+      Proceed to Execution Flow below.
+
+      ## Cleanup Rules
+
+      | Category | Rule | Action |
+      |----------|------|--------|
+      | Completed changes | Change with `status: completed` older than current task | Summarize -> archive |
+      | Orphaned artifacts | Files in `artifacts/` not referenced by any active change | List for user review |
+      | Stale session data | Session history entries older than 5 phases ago | Summarize into single entry |
+
+  - type: file
+    source: ./business.md
+
+  - type: inline
+    content: |
+      ## Output Format
+
+      Read and use the output template from: `.ai-agents/skills/_templates/cleanup-output.md`
+
+      If a custom version exists at `.ai-agents/skills/_templates/custom/cleanup-output.md`, use the custom version instead.
+
+      Every response MUST end with a Suggested Next Steps section.
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      next_primary: mvt-status
+      next_primary_desc: "Verify workspace state"

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

@@ -0,0 +1,26 @@
+## Execution Flow
+
+### Interactive Menu (Default)
+1. Read current settings from `config.yaml`
+2. Display configuration menu with categories and current values
+3. Wait for user to select a category (1-5)
+4. Show category detail view with editable settings
+5. Apply changes after user confirmation
+
+### Direct Set (`set {key} {value}`)
+1. Validate key exists -- if not, show available keys
+2. Validate value type -- if wrong, show expected type
+3. Preview the change (old -> new)
+4. Ask user to confirm
+5. Apply and write `config.yaml`
+
+### Guided Wizard (`wizard`)
+1. Step 1: Language Preference
+2. Step 2: Output Style (emojis, data format)
+3. Step 3: Architecture Pattern
+4. Summary Preview -> User confirms -> Apply all changes
+
+### Reset (`reset`)
+1. Show all settings that will be reset
+2. Ask user confirmation
+3. Write default values to `config.yaml`

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

@@ -0,0 +1,108 @@
+name: mvt-config
+output: .claude/skills/mvt-config/SKILL.md
+
+frontmatter:
+  name: mvt-config
+  description: "Interactive configuration management for framework settings. Use when user wants to change language, output format, architecture pattern, or other framework settings."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Config
+
+      ## Purpose
+
+      Interactive configuration management for MVTT framework settings. Provides guided setup, direct key-value setting, and a setup wizard for common configurations.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Conductor
+      role_desc: "a Workflow Coordinator"
+      decision_rules:
+        - rule: "No arguments -> Show interactive configuration menu"
+        - rule: "`show` argument -> Display all current settings"
+        - rule: "`set {key} {value}` -> Validate and apply the specific setting"
+        - rule: "`wizard` argument -> Start guided setup flow"
+        - rule: "`reset` argument -> Reset all settings to defaults after confirmation"
+        - rule: "Invalid key -> Show available keys and exit"
+        - rule: "Invalid value type -> Show expected type and exit"
+      boundaries:
+        - scope: "analyze requirements"
+          skill: "/mvt-analyze"
+        - scope: "design architecture"
+          skill: "/mvt-design"
+        - scope: "write implementation code"
+          skill: "/mvt-implement"
+
+  - type: inline
+    content: |
+      ## Variants
+
+      | Variant | Description |
+      |---------|-------------|
+      | `/mvt-config` | Show interactive configuration menu |
+      | `/mvt-config show` | Display all current settings |
+      | `/mvt-config set {key} {value}` | Set a specific configuration value |
+      | `/mvt-config wizard` | Start guided setup wizard |
+      | `/mvt-config reset` | Reset all settings to defaults |
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - ".ai-agents/config.yaml -- Current configuration (this skill's primary target)"
+
+  - type: shared
+    source: sections/activation-load-config.md
+
+  - type: inline
+    content: |
+      ### Step 3: Pre-flight Checks
+      - No blocking checks required (config is always accessible)
+
+      ### Step 4: Execute
+      Proceed to Execution Flow below.
+
+      ## Configuration Keys
+
+      ### User Preferences
+
+      | Key | Type | Default | Description |
+      |-----|------|---------|-------------|
+      | `preferences.language` | enum | `en-US` | Output language for all responses and documents (en-US, zh-CN) |
+      | `preferences.output.no_emojis` | bool | `true` | Disable emojis in output |
+      | `preferences.output.data_format` | enum | `yaml` | Data output format (yaml, json) |
+
+      ### Pattern Settings
+
+      | Key | Type | Default | Description |
+      |-----|------|---------|-------------|
+      | `pattern.active` | enum | `` | Active architecture pattern |
+      | `pattern.selection.auto_detect` | bool | `true` | Auto-detect pattern on init |
+      | `pattern.selection.confirm_with_user` | bool | `true` | Confirm pattern with user |
+
+  - type: file
+    source: ./business.md
+
+  - type: inline
+    content: |
+      ## Output Format
+
+      Read and use the output template from: `.ai-agents/skills/_templates/config-output.md`
+
+      If a custom version exists at `.ai-agents/skills/_templates/custom/config-output.md`, use the custom version instead.
+
+      Every response MUST end with a Suggested Next Steps section.
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      next_primary: mvt-config
+      next_primary_desc: "`show` -- Verify changes"
+      next_alternatives:
+        - skill: mvt-init
+          when: "--refresh -- Re-analyze with new pattern"
+      always_show:
+        - skill: mvt-status
+          desc: "Check current project state"

package/sources/skills/mvt-create-skill/business.md

@@ -0,0 +1,111 @@
+## Execution Flow
+
+### Step 1: Requirements Gathering
+Ask the user for:
+- **Skill name**: Suggest `mvt-` prefix for consistency, but also accept project-specific prefixes (e.g., `app-`, `proj-`)
+- **Purpose**: What does this skill do?
+- **Category**: workflow / utility / project-specific
+- **Trigger keywords**: What phrases should invoke this skill? (used for `description` field)
+
+### Step 2: Skill Design
+- Load an existing skill file as structural reference
+- Load config.yaml for project configuration context
+- Determine required input parameters
+- Determine execution mode: interactive / automated / hybrid
+- Determine output format needs
+
+### Step 3: Template Decision
+- Does the skill need an output template?
+  - Yes -> Choose: adapt existing template or create new one
+  - No -> Skip template creation
+- Does the skill need context loading beyond session + project-context?
+  - Yes -> Define the file list
+  - No -> Use only basic loading
+
+### Step 4: Generate Skill Files
+1. Create `.claude/skills/{name}/SKILL.md` with standard structure:
+   - YAML frontmatter (`name`, `description`)
+   - Purpose section
+   - Role section (Decision Rules + Boundaries)
+   - Context Loading section
+   - Execution Flow section
+   - State Update section (MANDATORY — see below)
+   - Output Format section
+   - Suggested Next Steps section
+2. If output template needed -> Create `.ai-agents/skills/_templates/{name}-output.md`
+3. Update registry if template was created
+
+### Step 4.5: Register in Registry (MANDATORY)
+Append the new skill entry to `.ai-agents/registry.yaml` > `skills` section:
+```yaml
+  {name}:
+    agent: {agent}
+    path: .claude/skills/{name}/SKILL.md
+    template: {template_path_or_null}
+    category: {category}
+    mode: independent
+    custom: true
+```
+The `custom: true` field is **required** for all user-created skills. It protects the skill from being overwritten during framework updates.
+
+### Step 5: Validation
+- Verify SKILL.md format compliance (frontmatter has `name` + `description`)
+- Confirm no naming conflicts with existing skills
+- Verify `registry.yaml` entry includes `custom: true`
+- Show the user how to invoke: `/{name}`
+
+## Generated Skill Structure
+
+```markdown
+---
+name: mvt-{name}
+description: '{trigger keyword description}'
+---
+
+# MVT {Name}
+
+## Purpose
+{user-defined purpose}
+
+## Role
+You are the **Conductor** -- a Workflow Coordinator.
+
+### Decision Rules
+{generated based on skill purpose}
+
+### Boundaries
+{standard boundaries}
+
+## Activation Protocol
+
+### Step 1: Load Context (Context Foundation)
+Load the following files as foundational context:
+- `.ai-agents/workspace/session.yaml` -- Current workflow state
+- `.ai-agents/workspace/project-context.yaml` -- Project domain data
+
+### Step 2: Load Config & Apply Preferences (Config Foundation)
+Read `.ai-agents/config.yaml` and enforce the following throughout this entire session:
+- `preferences.language` → Use this language for ALL output
+- `preferences.output.no_emojis` → If true, never use emojis
+- `preferences.output.data_format` → Use this format for data sections
+
+### Step 3: Pre-flight Checks
+{skill-specific checks}
+
+### Step 4: Execute
+Proceed to Execution Flow below.
+
+## Execution Flow
+{generated based on user requirements}
+
+## State Update (Required)
+After execution, update `.ai-agents/workspace/session.yaml`:
+- Set `session.last_command: "/{name}"`
+- Append one-line summary to `recent_actions` (keep max 3)
+
+## Output Format
+{template reference or inline format}
+
+## Suggested Next Steps
+{contextual suggestions}
+```

package/sources/skills/mvt-create-skill/manifest.yaml

@@ -0,0 +1,79 @@
+name: mvt-create-skill
+output: .claude/skills/mvt-create-skill/SKILL.md
+
+frontmatter:
+  name: mvt-create-skill
+  description: "Create custom MVTT skills through interactive guided workflow. Use when user wants to create a new skill, extend the framework with custom functionality, or build project-specific automation."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Custom Skill
+
+      ## Purpose
+
+      Guide users through designing and creating custom MVTT-compliant skills. Generates properly structured SKILL.md files with optional output templates, ensuring compatibility with the framework.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Conductor
+      role_desc: "a Workflow Coordinator"
+      decision_rules:
+        - rule: "User provides skill name -> Validate and proceed with design"
+        - rule: "Name conflicts with existing skill -> Warn and ask for alternative"
+        - rule: "Skill needs output template -> Create template in `_templates/` and update manifest"
+        - rule: "Skill needs state updates -> Include session.yaml update rules"
+      boundaries:
+        - scope: "Generated skills must follow MVTT SKILL.md standard structure"
+          skill: "(constraint)"
+        - scope: "Skill names may use `mvt-` prefix or a project-specific prefix (e.g., `app-`, `proj-`)"
+          skill: "(constraint)"
+        - scope: "All custom skills MUST be registered in `registry.yaml` with `custom: true`"
+          skill: "(to prevent overwrite during framework updates)"
+        - scope: "Description field must contain effective trigger keywords"
+          skill: "(constraint)"
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - "Load one existing SKILL.md as structural reference (e.g., `.claude/skills/mvt-status/SKILL.md`)"
+        - ".ai-agents/registry.yaml -- Registered skills list"
+
+  - type: shared
+    source: sections/activation-load-config.md
+
+  - type: inline
+    content: |
+      ### Step 3: Pre-flight Checks
+      - No blocking checks required.
+
+      ### Step 4: Execute
+      Proceed to Execution Flow below.
+
+  - type: file
+    source: ./business.md
+
+  - type: inline
+    content: |
+      ## Output Format
+
+      No external template -- output is the generated skill file itself plus a creation summary:
+
+      ```markdown
+      ## Custom Skill Created
+
+      - **Skill**: `/{name}`
+      - **Location**: `.claude/skills/{name}/SKILL.md`
+      - **Registry**: `registry.yaml` (custom: true)
+      - **Template**: {created/none}
+      - **Category**: {category}
+
+      You can now use `/{name}` to invoke your new skill.
+
+      ---
+      **Suggested Next Steps**:
+      - Test your new skill by running `/{name}`
+      - `/mvt-help` -- View updated skills list
+      ```

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

@@ -0,0 +1,34 @@
+## Execution Flow
+
+### Step 1: Review Requirements
+- Load requirements from `project-context.yaml`
+- Load analysis artifact if exists
+- Identify key architectural concerns (scalability, security, performance, etc.)
+
+### Step 2: Select Architecture Approach
+- Check active pattern in config
+- Load pattern-specific knowledge
+- If `--plan` flag -> Skip to high-level plan, omit detailed interfaces
+
+### Step 3: Design Module Structure
+- Define modules with responsibilities and layers
+- Define interfaces between modules
+- Establish dependency direction rules
+
+### Step 4: Create Data Flow Design
+- Design request/response flows
+- Define service interactions
+- Create sequence diagrams (Mermaid)
+
+### Step 5: Document Decisions
+- Record Architecture Decision Records (ADRs)
+- Include rationale, alternatives considered, and trade-offs
+
+### Step 6: Update Workspace
+1. Update `.ai-agents/workspace/session.yaml`:
+   - Set `progress.design: done`
+   - Set `session.last_command: "/mvt-design"`
+   - Append one-line summary to `recent_actions` (keep max 3)
+2. Update `.ai-agents/workspace/project-context.yaml`:
+   - Write to `architecture` section (modules, decisions, interfaces)
+3. Write artifact: `.ai-agents/workspace/artifacts/{change-id}/design.md`

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

@@ -0,0 +1,105 @@
+name: mvt-design
+output: .claude/skills/mvt-design/SKILL.md
+
+frontmatter:
+  name: mvt-design
+  description: "Create architecture design based on analyzed requirements. Applies architectural patterns, defines module structure, and creates technical blueprints. Use when user wants to design system architecture."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Design
+
+      ## Purpose
+
+      Design system architecture based on analyzed requirements. Apply architectural patterns and create technical blueprints that guide implementation. This is the second phase in the full workflow: analyze -> design -> implement -> review -> test.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Architect
+      role_desc: "a System Architecture Expert"
+      decision_rules:
+        - rule: "Multiple valid patterns exist -> Present top 2-3 options with pros/cons table, recommend one"
+        - rule: "Trade-off affects performance vs maintainability -> Document as ADR, state the trade-off"
+        - rule: "User asks for technology choice -> Evaluate against: requirements fit, team familiarity, maintenance cost"
+        - rule: "Design needs breaking change -> Highlight impact scope, list affected files, propose migration"
+        - rule: "Requirements are ambiguous -> Stop and ask clarification before designing"
+        - rule: "Pattern conflicts with project structure -> Report conflict, suggest pattern change via `/mvt-config`"
+      boundaries:
+        - scope: "write implementation code"
+          skill: "/mvt-implement"
+        - scope: "re-analyze requirements"
+          skill: "/mvt-analyze"
+        - scope: "review code"
+          skill: "/mvt-review"
+
+  - type: inline
+    content: |
+      ## Variants
+
+      | Variant | Description |
+      |---------|-------------|
+      | `/mvt-design` | Full architecture design |
+      | `/mvt-design --plan` | High-level implementation plan only |
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - ".ai-agents/knowledge/patterns/{pattern.active}/ -- Active architecture pattern knowledge"
+        - ".ai-agents/knowledge/core/ -- Core knowledge files"
+        - ".ai-agents/workspace/artifacts/{active_change.id}/analysis.md -- Analysis from previous phase"
+
+  - type: shared
+    source: sections/activation-load-config.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: "project.name"
+          level: "BLOCK"
+          message: 'Project not initialized. Run `/mvt-init` first.'
+        - order: "3"
+          field: "pattern.active"
+          level: "BLOCK"
+          message: 'Architecture pattern required. Run `/mvt-init` to detect and set the pattern.'
+        - order: "4"
+          field: "requirements in project-context"
+          level: "WARN"
+          message: 'No requirements found. Run `/mvt-analyze` first." (allow user to proceed)'
+
+  - type: inline
+    content: |
+      ### Step 4: Execute
+      Proceed to Execution Flow below.
+
+  - type: file
+    source: ./business.md
+
+  - type: inline
+    content: |
+      ## Output Format
+
+      Read and use the output template from: `.ai-agents/skills/_templates/design-output.md`
+
+      If a custom version exists at `.ai-agents/skills/_templates/custom/design-output.md`, use the custom version instead.
+
+      Fill the template placeholders with the design results.
+
+      Every response MUST end with a Suggested Next Steps section.
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      next_primary: mvt-implement
+      next_primary_desc: "Start implementing this design"
+      always_show:
+        - skill: mvt-status
+          desc: "Check current workflow progress"