planning-and-task-breakdown

Decomposes feature specifications into dependency-ordered tasks with acceptance criteria.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill planning-and-task-breakdown-rkaaaa404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/Rkaaaa404/cyberhack-SYDT/tree/main/.agents/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill planning-and-task-breakdown-rkaaaa404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large feature specs often get implemented in one unplanned pass, causing dependency loops, rework, and unverifiable progress. This Skill turns any spec into small, independently testable tasks with clear acceptance criteria and dependency ordering. ## Core Features & Use Cases - Task Decomposition: Breaks a spec into concrete deliverables (migrations, API routes, types, UI pages, tests, docs), each sized to roughly 30 minutes to 4 hours maximum. - Dependency Ordering: Maps task dependencies so foundational work (database, API) precedes dependent work (forms, lists, tests), preventing integration failures. - DaaS Phase Alignment: Aligns tasks with the DaaS phased development model (Foundation, Data, UI, Logic, Relations, Polish), including a mandatory Phase 0 Buildpad UI component install before any UI task. - Use Case: Given a "Task Management" feature spec, produce an implementation plan where the migration, API route, TypeScript types, list page, form page, RBAC, and tests each become a separate committable task with pass/fail acceptance criteria. ## Quick Start Ask the AI to break down your feature specification into an ordered implementation plan with acceptance criteria 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 feature spec into implementation tasks?▼

List every concrete deliverable from the spec (migrations, API routes, types, pages, tests, docs), order them by dependency, then write each task with acceptance criteria. Keep tasks small enough to complete and verify in one sitting.

What makes a good task acceptance criterion?▼

A good acceptance criterion is a verifiable pass/fail statement, such as "migration runs without errors" or "GET returns a paginated list." Each task should be independently testable without depending on other unfinished tasks.

How large should a single implementation task be?▼

Tasks should range from about 30 minutes for a single file change to a maximum of 4 hours. Anything larger should be split further, since oversized tasks hide unknowns and cannot be verified incrementally.

Why must Buildpad UI components be installed before UI tasks?▼

Components like CollectionList and VForm only exist at @/components/ui/* after the Buildpad CLI installs them. Any UI task importing those paths will fail unless a Phase 0 bootstrap or add task is ordered first.

What are common mistakes when planning implementation tasks?▼

Common red flags include tasks without acceptance criteria, flat lists with no dependency ordering, tasks exceeding four hours, mixing development phases in one task, and skipping risk identification.