planning-and-task-breakdown

Decomposes specs into ordered, verifiable tasks with acceptance criteria and checkpoints.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/GonkaGate/opencode-setup --skill planning-and-task-breakdown-gonkagate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/GonkaGate/opencode-setup/tree/main/.agents/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/GonkaGate/opencode-setup --skill planning-and-task-breakdown-gonkagate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vaguely defined work items cause agents and developers to start coding without a clear path, producing tangled implementations and rework. This Skill turns a spec or clear requirements into small, ordered, verifiable tasks with explicit acceptance criteria, dependencies, and checkpoints. ## Core Features & Use Cases - Dependency Mapping: Builds a dependency graph of the work so implementation order follows foundations first. - Vertical Task Slicing: Structures tasks as complete slices (contract, code, tests, docs) instead of horizontal layers, keeping the repository truthful after each step. - Task Templates and Sizing: Provides a task document template with acceptance criteria, verification commands, and sizing guidelines from XS to XL. - Use Case: Given a product spec for a new CLI feature, produce a phased implementation plan where each task lists files touched, test commands like npm run ci, and checkpoints for human review. ## Quick Start Ask the agent to break the current spec into an ordered implementation plan with acceptance criteria, verification steps, and checkpoints before writing any code.

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 spec into implementable tasks?

Map the dependency graph first, then slice vertically so each task delivers a complete slice of contract, code, tests, and docs. Each task needs acceptance criteria, a verification command, and a size of roughly five files or fewer.

What is vertical slicing in task planning?

Vertical slicing means each task completes one thin end-to-end slice of functionality rather than doing all docs, then all code, then all tests. This keeps the repository in a working, truthful state after every task.

When should I not use a formal task breakdown process?

Skip it for single-file changes with obvious scope, when the spec already contains well-defined tasks, or when the request is still too ambiguous and needs brainstorming first. Planning overhead only pays off for multi-step work.

How big should a single implementation task be?

Aim for small tasks of one to two files or medium tasks of three to five files, completable in one focused session. Anything touching eight or more files is too large and should be split further.

Can multiple agents work on a task plan in parallel?

Independent feature slices and tests for finished features parallelize safely. Shared config contract changes and dependency chains must stay sequential, so define shared contracts first before splitting work.