skills.rest
ProfFroggo
ProfFroggoCOMMUNITY
Explore all skills by this author →
GitHub

task-decomposition

Decompose complex work into owner-assigned subtasks with completion conditions for Mission Control.

1|Updated Mar 8, 2026
Search Tags:#workflow#planning#ownership#agile#subtasks#task-decomposition
One-click install
npx skills add https://github.com/ProfFroggo/froggo-mission-control --skill task-decomposition-proffroggo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-decomposition
Source: https://github.com/ProfFroggo/froggo-mission-control/tree/main/.claude/skills/task-decomposition
Command: npx skills add https://github.com/ProfFroggo/froggo-mission-control --skill task-decomposition-proffroggo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a practical framework to break down complex work into discrete, verifiable subtasks that can be assigned to individual agents in the Mission Control task board.

Core Features & Use Cases

  • Define end-state with measurable completion conditions for each subtask.
  • Assign a single owner per task and map dependencies to maintain flow.
  • Consume the framework across product-management, software engineering, design, and research workflows.

Quick Start

Decompose a high-level task into owner-assigned subtasks with clear completion criteria for the Mission Control task board.

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 complex project work into actionable subtasks?▼

Task decomposition breaks complex project work into discrete subtasks by enforcing a single completion condition per subtask, assigning one owner, and mapping explicit dependencies for the Mission Control task board.

What is the best way to assign ownership and dependencies when planning an agile sprint?▼

Agile sprint planning ownership and dependencies are managed by assigning a single owner per task and explicitly mapping dependencies between subtasks to maintain workflow flow across engineering, design, research, and product-management tasks.

Can I use task decomposition for both software engineering and design workflows?▼

Task decomposition works across software engineering, design, research, and product-management workflows, consuming the same framework to define end-states with measurable completion conditions for each subtask.

How do I define completion criteria for subtasks during workflow triage?▼

Defining completion criteria for subtasks during workflow triage requires establishing a single, measurable end-state completion condition for each subtask before assigning it to an individual agent on the task board.

Does task decomposition require artifact linkage to the mission-control library?▼

Task decomposition enforces artifact linkage to the mission-control library, ensuring every decomposed subtask connects to relevant project artifacts to maintain verifiable context and faster delivery.

When should I not use single-owner task decomposition for project planning?▼

Single-owner task decomposition should not be used for project planning tasks that require collaborative ownership or lack a distinct, measurable end-state, as the framework enforces one owner and one completion condition per subtask.

Related Skills

Explore More Product & Management Skills→
angrysky56angrysky56

kanban-orchestrator

Decompose high-level project goals into structured kanban tasks with worker assignment.

Community
Intermediate
wall3nwall3n

task-management

Track feature subtasks and dependencies with structured task files.

Community
Intermediate
aquariuscookaquariuscook

github-project-management

Orchestrate GitHub issue lifecycle automation and project board synchronization.

Community
Advanced
Yusei-SHIRAISHIYusei-SHIRAISHI

plane-project-management

Orchestrate Plane projects, modules, and work items with dependencies and reviews.

Community
Advanced