prompt-decomposition

Decompose complex prompts into atomic tasks with explicit dependencies.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/fgiova/claude-marketplace --skill prompt-decomposition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-decomposition
Source: https://github.com/fgiova/claude-marketplace/tree/main/plugins/planning-workflow/skills/prompt-decomposition
Command: npx skills add https://github.com/fgiova/claude-marketplace --skill prompt-decomposition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams and agents transform vague prompts into structured, executable plans by breaking down complex tasks into atomic, independent actions.

Core Features & Use Cases

  • Atomic task decomposition with explicit dependencies
  • Parallelizable phased execution and plan persistence for cross-session resume
  • Iterative plan review and refinement with clear task ownership and milestones

Quick Start

Ask me to plan a task and I will bootstrap a plan, decompose tasks into atomic steps, and organize phases automatically.

Frequently Asked Questions about prompt-decomposition

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

FAQPage Schema
How do I decompose complex prompts into executable tasks?

Task decomposition breaks complex prompts into atomic, independently executable actions with explicit dependencies. This skill bootstraps a deterministic workflow that maps dependencies, divides work into phases, and creates structured task files for organized execution.

What is the best way to break down project work into parallelizable tasks?

Phased parallel execution divides project work into independent atomic tasks with explicit dependencies. This approach organizes milestones, enables parallel task execution across phases, and establishes clear task ownership for complex planning scenarios.

Can I resume an incomplete task plan across different sessions?

Cross-session resume persists plans to the .plans directory, allowing you to stop and continue task execution later. The deterministic workflow saves task files and dependency maps automatically to support iterative plan review and refinement.

Do I need any external dependencies to map task dependencies for project scoping?

No external dependencies are required to map task dependencies for project scoping. The skill operates independently to bootstrap .plans, create task files, and organize phased execution workflows without relying on external tools or frameworks.

When should I not use atomic task decomposition for planning?

Atomic task decomposition is not suited for simple, single-step prompts that require no dependency mapping or phased execution. If your workflow does not benefit from cross-session resume or parallelizable task files, this structured planning approach adds unnecessary overhead.