planning-and-task-breakdown

Decompose specs into small tasks with acceptance criteria and dependency ordering.

2|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/heimanba/port-lens --skill planning-and-task-breakdown-heimanba
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/heimanba/port-lens/tree/main/.cursor/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/heimanba/port-lens --skill planning-and-task-breakdown-heimanba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose vague project goals and specs into a structured, prioritized task list with clear acceptance criteria and checkpoints.

Core Features & Use Cases

  • Structured task decomposition from a spec to focused, testable tasks.
  • Acceptance criteria and verification steps embedded per task to ensure measurable progress.
  • Scenario-based planning that enables parallel work and risk management.

Quick Start

Provide a project brief or spec and ask the planner to break it into tasks.

Frequently Asked Questions about planning-and-task-breakdown

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

FAQPage Schema
How do I break down large project requirements into actionable tasks?▼

Task breakdown decomposes large project requirements into small, verifiable tasks. This planning process identifies task-level descriptions, acceptance criteria, and verification steps to enable parallel work and reliable delivery from ambiguous specs.

What is the best way to estimate work for ambiguous project specifications?▼

Estimating work for ambiguous specifications requires applying a structured planning process to decompose goals into focused, testable tasks. Each task includes embedded acceptance criteria and verification steps, providing measurable checkpoints for accurate project estimation and risk management.

Can I use task decomposition to enable parallel work across a team?▼

Task decomposition enables parallel work by breaking large specs into small, verifiable tasks with clear dependency ordering. This scenario-based planning process structures team assignments through task-level descriptions and acceptance criteria, allowing reliable concurrent delivery.

How do I add acceptance criteria and verification steps to a task breakdown?▼

Acceptance criteria and verification steps are embedded per task during the task breakdown process. Decomposing a project brief structures each task with measurable acceptance criteria and verification steps, ensuring focused, testable progress and clear checkpoints.

When should I apply a structured planning process to manage project dependencies?▼

Apply a structured planning process when project tasks are large or ambiguous and require dependency ordering. Decomposing work into small, verifiable tasks enables parallel work and reliable delivery by outlining a plan with task-level descriptions and checkpoints.

Does task breakdown work for managing project requirements without specialized software?▼

Task breakdown works by decomposing a provided project brief or spec into a structured, prioritized task list. It applies the planning process directly to your requirements to generate task descriptions, acceptance criteria, and dependency ordering without needing specialized software.