planning-and-task-breakdown

Decomposes specifications into ordered, verifiable implementation tasks with acceptance criteria.

5|Updated Mar 5, 2024
One-click install
npx skills add https://github.com/TRAPZZY/God-Eyes --skill planning-and-task-breakdown-trapzzy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/TRAPZZY/God-Eyes/tree/main/.skills/planning-and-task-breakdown
Command: npx skills add https://github.com/TRAPZZY/God-Eyes --skill planning-and-task-breakdown-trapzzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vague work items cause agents and developers to produce tangled, incomplete implementations. This Skill turns a spec or clear requirements into small, verifiable tasks with explicit acceptance criteria, dependencies, and checkpoints so work can be executed reliably. ## Core Features & Use Cases - Dependency Graph Mapping: Identifies what depends on what (schema, API, UI) so implementation order follows foundations first. - Vertical Slicing: Structures tasks as complete feature paths rather than horizontal layers, so every task delivers working, testable functionality. - Task Sizing and Checkpoints: Provides sizing guidelines (XS through XL), a plan document template, parallelization rules, and verification checkpoints between phases. - Use Case: Given a feature spec for user authentication, produce a phased plan where Task 1 covers registration end-to-end (schema + API + UI), Task 2 covers login, with a checkpoint verifying tests pass before proceeding. ## Quick Start Break this feature spec into an ordered implementation plan with acceptance criteria and verification steps for each 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 a large feature into implementable tasks?▼

Map the dependency graph first, then slice vertically so each task delivers one complete feature path across schema, API, and UI. Every task gets acceptance criteria, verification steps, and a size estimate of five files or fewer.

What is vertical slicing in task breakdown?▼

Vertical slicing builds one complete feature path at a time, such as user registration covering schema, API, and UI together. It contrasts with horizontal slicing, which builds all database, then all API, then all UI, delaying testable functionality.

When should a task be broken down further?▼

Break a task down when it exceeds one focused session, needs more than three acceptance criteria bullets, touches two independent subsystems, or contains 'and' in its title. Tasks sized L or larger should always be split.

When should I not use a formal planning process?▼

Skip formal planning for single-file changes with obvious scope, or when the spec already contains well-defined tasks. Planning adds value when work is large, vague, parallelized, or has unclear implementation order.

Which tasks can be parallelized across multiple agents?▼

Independent feature slices, tests for already-implemented features, and documentation are safe to parallelize. Database migrations, shared state changes, and dependency chains must remain sequential, and shared API contracts need coordination first.