task-decomposition

Name: task-decomposition
Availability: InStock
Author: pavel-molyanov

Decompose approved technical specifications into validated atomic task files.

244|75|Updated Dec 22, 2025

Search Tags:#workflow automation #validation #task decomposition #agile development #technical specification #feature breakdown

Ready to run

npx skills add https://github.com/pavel-molyanov/molyanov-ai-dev --skill task-decomposition-pavel-molyanov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-decomposition
Source: https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/task-decomposition
Command: npx skills add https://github.com/pavel-molyanov/molyanov-ai-dev --skill task-decomposition-pavel-molyanov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms a complex, approved technical specification into a series of small, manageable, and validated individual tasks, ensuring clarity and preventing scope creep.

Core Features & Use Cases

Task Generation: Automatically creates individual task files from a technical specification.
Parallel Validation: Validates tasks individually and then checks for cross-task integration conflicts.
Use Case: After a technical specification for a new user authentication feature is approved, use this skill to break it down into tasks like "Implement JWT generation," "Create user registration API endpoint," and "Develop password reset flow," ensuring each task is well-defined and validated.

Quick Start

Decompose the tech-spec for the 'user-profile-update' feature into individual tasks.

Frequently Asked Questions about task-decomposition

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

FAQPage Schema

How do I break down an approved technical specification into actionable development tasks?▼

To break down an approved technical specification into actionable tasks, you can decompose the tech-spec and user-spec files to automatically generate individual, validated task files in English while ensuring template compliance and cross-task integration.

What is the best way to prevent scope creep when decomposing complex features for agile development?▼

Feature breakdown prevents scope creep by decomposing complex technical specifications into small, manageable atomic task files, validating each task individually, and checking for cross-task integration conflicts before user approval.

How does parallel validation work when generating task files from a technical specification?▼

Parallel validation works by validating generated task files individually and then performing cross-task integration conflict checks, running up to three iterations of validation to ensure reality checks and template compliance before presenting a summary.

Do I need an approved tech-spec file before I can generate individual task files?▼

Yes, you need an approved tech-spec file and user-spec files as input. The decomposition process reads these approved specifications to generate individual atomic task files, ensuring the output aligns with the validated technical requirements.

Can I validate cross-task integration conflicts after breaking down a technical specification?▼

Yes, after generating task files from a technical specification, the process validates tasks individually and then checks for cross-task integration conflicts, running up to three validation iterations before presenting a summary for final user approval.