skills.rest
d0whc3r
d0whc3rCOMMUNITY
Explore all skills by this author →
GitHub

planning-and-task-breakdown

Breaks down software work into ordered, verifiable tasks via dependency analysis and vertical slicing across subsystems.

2|Updated Feb 16, 2026
Search Tags:#planning#verification#task breakdown#acceptance criteria#implementation plan#dependency graph#vertical slicing
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill planning-and-task-breakdown-d0whc3r
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.agents/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill planning-and-task-breakdown-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning vague or oversized work into a clear, ordered plan that an agent (and ideally multiple collaborators) can execute without drifting or producing a tangled result.

Core Features & Use Cases

  • Dependency graph planning: Breaks work into foundation-to-integration order by mapping what depends on what.
  • Vertical slicing task design: Creates end-to-end task slices (schema/API/UI or equivalent) so each step delivers a verifiable outcome.
  • Verification-focused tasks: Adds explicit acceptance criteria, tests/build checks, and manual verification guidance to reduce rework.

Quick Start

Ask the agent to write an implementation plan for your feature spec using dependency mapping, vertical slices, small S/M-sized tasks, and explicit acceptance criteria plus test/build/manual verification per task.

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 a large software spec into executable tasks?▼

Vertical slicing creates end-to-end task slices across subsystems, such as schema, API, and UI. This ensures each step delivers a verifiable outcome, enabling safe parallelization and frequent validation throughout the implementation plan.

How do I add verification and acceptance criteria to an implementation plan?▼

Add verification to an implementation plan by defining explicit acceptance criteria, test or build checks, and manual verification guidance per task. This reduces rework by ensuring each verifiable outcome meets checkpoint gates before moving forward.

What is the best way to parallelize software work safely across multiple collaborators?▼

Use dependency graph analysis for vague or unclear scope to map what depends on what. This transforms oversized work into a clear, ordered plan with foundation-to-integration sequencing, preventing execution drift.

Does this planning approach write code or only produce the task breakdown?▼

This planning approach only produces the task breakdown and does not write code during planning. It focuses entirely on generating ordered, verifiable tasks with dependency ordering and checkpoint gates.

Related Skills

Explore More Software Engineering Skills→
ahgraberahgraber
5

spec-kit-specify

Convert vague requirements into structured, testable feature specifications using Spec Kit templates.

Community
Advanced
yuanyuekejiJNyuanyuekejiJN
18

executing-plans

Execute written implementation plans in ordered batches with review checkpoints.

Community
Intermediate
CaptainCrouton89CaptainCrouton89
497

Testing Code

Automate software tests to verify functionality against acceptance criteria.

Community
Basic
Euraika-LabsEuraika-Labs
14

qa-plan

Generate structured QA test plans from project story files and artifacts.

Official
Advanced