task-decomposition-planning

Convert approved goals and designs into ordered, dependency-aware tasks with acceptance criteria.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/Zhachory1/autopraxis --skill task-decomposition-planning-zhachory1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-decomposition-planning
Source: https://github.com/Zhachory1/autopraxis/tree/main/skills/task-decomposition-planning
Command: npx skills add https://github.com/Zhachory1/autopraxis --skill task-decomposition-planning-zhachory1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved PRD, design doc, or experiment proposal into executable work often produces vague task lists with hidden dependencies, missing acceptance criteria, and uncontrolled scope creep. This Skill converts approved intent into an ordered, verifiable task plan that implementers can execute without re-deriving the original intent. ## Core Features & Use Cases - Dependency-aware task graphs: Extract deliverables, map prerequisites and external blockers, and order tasks by dependency and risk so unknowns are de-risked early. - Verifiable task definitions: Every task carries context, acceptance criteria, validation evidence, owner, and stop conditions, plus loop gates defining when work continues, stops, or escalates. - Delivery budget enforcement: Caps implementation at two PRs per issue across repositories, requiring explicit human approval before expanding scope. - Use Case: A developer with an approved feature spec uses this Skill to produce a task plan with execution waves, open blockers, and a handoff package for the shipping agent, complete with telemetry on task counts and plan confidence. ## Quick Start Ask the agent to decompose your approved PRD or design doc into an ordered task plan with acceptance criteria, dependencies, and validation for each task.

Frequently Asked Questions about task-decomposition-planning

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

FAQPage Schema
How do I break down a PRD into implementation tasks?▼

Provide the approved PRD along with success criteria and constraints, and the Skill extracts deliverables, maps dependencies, and writes tasks with acceptance criteria, validation, owners, and stop conditions. Tasks are ordered by dependency and risk so unknowns are addressed early.

How to create a task plan with acceptance criteria for each task?▼

The Skill enforces a testable-task principle: every task must include acceptance criteria and validation evidence before the plan is considered complete. The output contract includes a task graph with acceptance criteria, validation, risks, and handoff targets per task.

When should I not decompose a goal into tasks?▼

Do not decompose unstable or unapproved goals. If the PRD, design doc, or metrics are unclear, the Skill routes work back to document authoring or success-criteria definition, and escalates to human review when risk justifies it.

What are the limits on implementation PRs per issue?▼

The Skill caps delivery at two implementation PRs across all repositories for one issue. Exceeding that budget requires explicit human approval through an approval gate with scope, options, cost, and a recommendation.

Why does task decomposition fail on large features?▼

Common failures include hiding implementation details in planning, missing loop gates, scope creep during decomposition, and oversized tasks. The Skill fixes these by splitting work into reviewable slices, adding stop/continue/escalate conditions, and returning new requirements to PRD approval.