mvt-plan-dev

Generate a structured plan.yaml with tasks, dependencies, and acceptance criteria.

19|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/uoyoCsharp/My-Virtual-TechTeam --skill mvt-plan-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mvt-plan-dev
Source: https://github.com/uoyoCsharp/My-Virtual-TechTeam/tree/main/.claude/skills/mvt-plan-dev
Command: npx skills add https://github.com/uoyoCsharp/My-Virtual-TechTeam --skill mvt-plan-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you break down a large software change into a structured development plan that can survive across multiple AI sessions. It reduces the risk of losing progress, skipping dependencies, or tackling work in the wrong order when a change is too big for a single implementation pass.

Core Features & Use Cases

  • Structured task decomposition: Splits a large change into ordered tasks with status, dependencies, project ownership, and acceptance criteria.
  • Plan validation and regeneration: Detects existing plans, validates task graphs, prevents cycles, and supports safe regeneration when needed.
  • Session-aware planning: Reads active change context, analysis artifacts, design artifacts, and workspace configuration to create a plan aligned with the current project state.
  • Use case: When a feature spans multiple modules or projects, use this Skill to produce a plan.yaml that tells future sessions exactly what task to do next and which skill should handle it.

Quick Start

Ask the AI to use the mvt-plan-dev skill to generate a plan.yaml for the current active change based on the existing analysis and design artifacts.

Frequently Asked Questions about mvt-plan-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a large software change into a trackable development plan?

To break down a large software change into a trackable development plan, generate a structured plan.yaml with ordered tasks, dependency graphs, acceptance criteria, and execution hints. This ensures progress survives across multiple AI sessions without skipping dependencies.

What is task decomposition for multi-session feature delivery?

Task decomposition for multi-session feature delivery is the process of splitting a cross-project change into ordered, independent tasks with status and project ownership. It aligns active change tracking with session state to sequence execution correctly in repository-based workflows.

How do I validate dependency graphs and prevent cycles when regenerating a project plan?

To validate dependency graphs and prevent cycles during plan regeneration, load existing plan.yaml files to detect DAG dependency violations and project attribution errors. Safe regeneration updates session metadata while maintaining valid task execution sequencing.

Do I need existing analysis and design artifacts to generate a plan.yaml?

Yes, generating a plan.yaml requires reading workspace session state, project context, registry, and configuration files. Loading relevant analysis and design artifacts ensures the structured development plan aligns with the current active project state.

Can I use yaml-based planning for cross-project change decomposition in AI workflows?

Yes, you can use yaml-based planning for cross-project change decomposition in repository-based AI workflows. It splits large changes into ordered tasks with project ownership and next-step execution hints, allowing future sessions to resume work seamlessly.