skills.rest
chrislema
chrislemaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

decompose-tasks

Decompose product requirements into dependency-ordered implementation tasks with acceptance criteria.

8|Updated Mar 15, 2026
Search Tags:#workflow#planning#task management#product management#decomposition#engineering
One-click install
npx skills add https://github.com/chrislema/claude-environments --skill decompose-tasks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decompose-tasks
Source: https://github.com/chrislema/claude-environments/tree/main/skills/decompose-tasks
Command: npx skills add https://github.com/chrislema/claude-environments --skill decompose-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of vague or overwhelming project requirements by breaking them down into concrete, dependency-ordered implementation tasks with clear acceptance criteria.

Core Features & Use Cases

  • Task Decomposition: Converts high-level product documents or feature requests into granular, reviewable work units.
  • Dependency Mapping: Identifies and enforces logical order between tasks to prevent bottlenecks.
  • Standardized Acceptance: Defines objective, checkable criteria for every task to ensure quality and reduce ambiguity.
  • Use Case: Use this when you have a complex feature spec and need to generate a structured implementation plan that assigns specific roles and deliverables to each part of the work.

Quick Start

Use the decompose-tasks skill to analyze the attached product document and generate a dependency-ordered task list with acceptance criteria.

Frequently Asked Questions about decompose-tasks

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

FAQPage Schema
How do I break down complex product requirements into actionable tasks?▼

Task decomposition converts high-level product documents into granular work units by mapping dependencies, assigning specific roles, and defining objective acceptance criteria to eliminate ambiguity in project scoping.

What is dependency mapping in software development planning?▼

Dependency mapping in software development planning identifies and enforces a logical execution order between implementation tasks to prevent engineering bottlenecks during the product lifecycle.

How do I define objective acceptance criteria for engineering tasks?▼

Defining objective acceptance criteria requires establishing standardized, checkable conditions for every decomposed task to ensure deliverable quality and reduce ambiguity in technical project management.

Can I use task decomposition for vague or overwhelming project scoping?▼

Task decomposition effectively handles vague project scoping by converting overwhelming product requirements into structured, reviewable work units with clear deliverables and standardized acceptance criteria.

When do I need to decompose tasks for engineering workflow refinement?▼

You need to decompose tasks during engineering workflow refinement when you have a complex feature spec and must generate a structured implementation plan assigning specific roles and deliverables to each work unit.

Related Skills

Explore More Product & Management Skills→
Andrej1601Andrej1601

architecture

Translate feature specs into high-level architecture designs with component structures and data flows.

Community
Advanced
usuroborusurobor
8

plan

Convert accepted designs into ordered implementation plans with acceptance criteria and file changes.

Community
Advanced
richardmbaileyrichardmbailey

rb-create-issues

Convert project requirements and implementation plans into structured issue tickets.

Community
Intermediate
bsamieebsamiee
2

plan-decompose

Parses work units from plan documents and creates ordered GitHub issues with blockers.

Community
Advanced