mvt-analyze

Analyze software requirements and extract domain concepts into a structured project analysis document.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn raw requirements into a clear analysis artifact before design and implementation begin. It reduces confusion by extracting features, actors, business rules, assumptions, and ambiguities so downstream work starts from a shared understanding.

Core Features & Use Cases

  • Structured requirements analysis: Parses requirement text or files into features, stakeholders, constraints, and assumptions.
  • Ambiguity detection and clarification: Stops when requirements are unclear, conflicting, or incomplete, then generates targeted clarification questions.
  • Workflow routing: Detects when a request is epic-scale and should be decomposed first, or when it is simple enough for a quick development path.
  • Workspace artifact generation: Writes a standardized analysis document and updates session state for the next Skill in the workflow.
  • Use Case: A developer pastes a new feature request for a customer portal; this Skill identifies the affected business rules, flags unclear acceptance criteria, and creates an analysis artifact that an architecture or implementation Skill can use next.

Quick Start

Ask the AI to use mvt-analyze on your requirement document or pasted feature request to extract requirements, detect ambiguities, and prepare the project for design or implementation.

Frequently Asked Questions about mvt-analyze

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

FAQPage Schema
How do I analyze software requirements for ambiguities before development?

Requirement ambiguity detection parses input text to extract features and constraints, stopping to generate targeted clarification questions when acceptance criteria are unclear, conflicting, or incomplete before development begins.

What is epic decomposition in requirements analysis?

Epic decomposition in requirements analysis detects large-scale requests and breaks them into smaller, manageable features before design, ensuring structured workflow routing instead of attempting direct implementation.

How do I extract domain concepts and business rules from a feature request?

Extracting domain concepts and business rules uses structured requirements analysis to parse feature requests, identifying stakeholders, constraints, assumptions, and affected logic into a standardized analysis document.

Can I generate a standardized analysis document from raw project requirements?

Generating a standardized analysis document from raw project requirements parses input text to produce a structured artifact containing features, constraints, and session state updates for the next workflow step.

Does requirements analysis support multilingual output control?

Requirements analysis supports multilingual output control, allowing teams to generate standardized analysis documents and clarification questions across multiple languages for shared understanding.

When should I use automated requirements analysis instead of manual review?

Automated requirements analysis is used when raw requirements need rapid extraction of features, constraints, and assumptions, or when workflow routing is needed to detect epic-scale requests requiring decomposition.