planning-and-task-breakdown

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

665|3|Updated Sep 12, 2026
One-click install
npx skills add https://github.com/rizqinrr/viserys-agent --skill planning-and-task-breakdown-rizqinrr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/rizqinrr/viserys-agent/tree/main/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/rizqinrr/viserys-agent --skill planning-and-task-breakdown-rizqinrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vaguely scoped work causes agents and developers to start coding without a plan, producing tangled implementations and missed requirements. This Skill turns a spec or clear requirements into an ordered set of small, verifiable tasks with explicit acceptance criteria, dependencies, and checkpoints. ## Core Features & Use Cases - Structured Planning Process: Read-only plan mode, dependency graph mapping, and vertical slicing so each task delivers working, testable functionality. - Task Templates and Sizing Rules: A standard task format (description, acceptance criteria, verification, dependencies, files touched) plus sizing guidelines that force oversized tasks to be broken down. - Plan and Task Outputs: Writes a plan document to tasks/plan.md and a task list to tasks/todo.md or an external tracker, with safeguards against overwriting incomplete plans. - Use Case: Given an approved PRD for a user registration feature, produce phased tasks (schema, API, UI) with checkpoints so each slice can be implemented and verified independently. ## Quick Start Ask the agent to break the current spec into an ordered task list with acceptance criteria and save the plan to tasks/plan.md.

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 smaller tasks?

Map the dependency graph first, then slice vertically so each task delivers one complete working feature path rather than a horizontal layer. Keep tasks to 1-5 files with acceptance criteria expressible in three or fewer bullet points.

What is vertical slicing in task breakdown?

Vertical slicing builds one complete feature path (schema, API, and UI together) per task instead of building all layers separately. Each slice leaves the system in a working, testable state.

When should a task be broken down further?

Break a task down when it exceeds one focused session, touches more than about five files, spans two independent subsystems, or its title contains 'and'. Tasks sized L or larger should always be split.

Can tasks be tracked in GitHub Issues or Jira instead of a markdown file?

Yes. If the project designates an external tracker, create one tracker item per task with acceptance criteria in the body and dependencies via the tracker's linking mechanism, and note the tracker in tasks/plan.md.

What happens if a tasks/plan.md file already exists?

The Skill checks for existing unchecked tasks before writing. Same work being replanned updates files in place; different work triggers a stop-and-ask rather than overwriting, since unchecked tasks may be mid-build in another session.