task-use-creator-decomposition-strategy

Generate a draft decomposition of a feature or epic with tasks, dependencies, risks, and open questions.

32|7|Updated Jan 28, 2026

Search Tags:#planning #task breakdown #decomposition #risk assessment #feature #dependency mapping #epic

Ready to run

npx skills add https://github.com/OzeroHAX/AssistAgents --skill task-use-creator-decomposition-strategy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-use-creator-decomposition-strategy
Source: https://github.com/OzeroHAX/AssistAgents/tree/main/templates/skills/task-use/creator/decomposition-strategy
Command: npx skills add https://github.com/OzeroHAX/AssistAgents --skill task-use-creator-decomposition-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps accelerate the planning process by generating a draft decomposition of a feature or epic, including potential dependencies and risks.

Core Features & Use Cases

Task Breakdown: Transforms requirements into a structured list of actionable work items.
Dependency Mapping: Identifies and outlines dependencies between tasks.
Risk Identification: Surfaces potential risks and unknowns early in the planning phase.
Use Case: When starting a new feature like "User Profile Management," use this Skill to get an initial breakdown of tasks, understand what needs to be built first, and anticipate potential roadblocks.

Quick Start

Use the task-use-creator-decomposition-strategy skill to decompose the "User authentication" epic into tasks with dependencies and acceptance criteria.

Frequently Asked Questions about task-use-creator-decomposition-strategy

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

FAQPage Schema

How do I break down a feature epic into actionable tasks?▼

To break down an epic into actionable tasks, you need feature decomposition. This process transforms requirements into a structured list of work items detailing dependencies, risks, and acceptance criteria.

What is the best way to map dependencies when planning feature development?▼

Mapping dependencies during feature development involves identifying relationships between tasks early. Using a decomposition strategy helps outline these dependencies to anticipate roadblocks and sequence work.

When do I need to use risk-first decomposition for task breakdown?▼

You need risk-first decomposition when planning features with high unknowns. This approach surfaces potential risks and open questions early, ensuring risky work items are prioritized before stable deliverables.

Can I generate a vertical slice decomposition from a PRD?▼

Yes, you can generate a vertical slice decomposition from a PRD. The strategy requires clear inputs like requirements or use cases and supports various decomposition strategies to deliver work items.

Does task decomposition work with specific tech stack constraints and timelines?▼

Task decomposition respects tech stack constraints and timelines. The generated breakdown transforms requirements into deliverables while operating within these defined project limitations.

Limitations of using automated decomposition for epics?▼

Automated decomposition generates a draft breakdown rather than a finalized plan. It requires clear inputs to function effectively and serves as an acceleration tool to identify risks, dependencies, and open questions.