skills.rest
svssdeva
svssdevaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

planning-and-task-breakdown

Break down engineering specs into ordered tasks with acceptance criteria.

1|1|Updated Apr 20, 2026
Search Tags:#planning#task breakdown#acceptance criteria#engineering workflow#dependency graph#vertical slicing#project estimation
One-click install
npx skills add https://github.com/svssdeva/agentic-skills --skill planning-and-task-breakdown-svssdeva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/svssdeva/agentic-skills/tree/main/engineering/planning-and-task-breakdown
Command: npx skills add https://github.com/svssdeva/agentic-skills --skill planning-and-task-breakdown-svssdeva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you avoid starting large, vague tasks and ending up with tangled work by converting a spec or requirements into a clear, ordered implementation plan with acceptance criteria and verification steps.

Core Features & Use Cases

  • Structured plan-first workflow: Performs read-only exploration of the spec and codebase, maps dependencies, and determines an implementation order before any code changes.
  • Vertical slicing for end-to-end progress: Breaks work into feature-path slices (schema + API + UI) so each task produces working, testable functionality.
  • Task quality guardrails: Uses small, verifiable tasks with acceptance criteria, verification checkpoints, dependency tracking, and red-flag checks (e.g., fail fast, avoid XL tasks).

Quick Start

Use the planning-and-task-breakdown skill to turn my requirements into an ordered implementation plan with tasks, acceptance criteria, dependencies, and verification checkpoints.

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 complex engineering work into verifiable steps?▼

Vertical slicing breaks work into feature-path slices like schema, API, and UI so each task produces working, testable functionality. This approach ensures end-to-end progress and allows parallelization decisions to be made safely during engineering workflows.

How do I create an implementation plan from a spec with unclear scope?▼

Creating an implementation plan from an unclear spec requires read-only exploration of the spec and codebase to map dependencies. This produces a clear, ordered implementation plan with task sizing safeguards and red-flag checks to prevent tangled work.

What is the best way to map a dependency graph for project estimation?▼

The best way to map a dependency graph for project estimation is through read-only exploration of your codebase and requirements. This identifies implementation order, tracks dependencies, and enables parallelization decisions for your engineering workflow.

Can I use a plan-first approach to avoid XL tasks during software development?▼

No, this approach is designed for read-only planning and does not perform code changes. It focuses entirely on converting specs into ordered implementation plans with acceptance criteria, dependency graphs, and verification checkpoints before any coding begins.

Related Skills

Explore More Software Engineering Skills→
knowz-ioknowz-io
1

knowzcode-explore

Analyze project architecture and patterns to generate implementation roadmaps.

Official
Advanced
oxieoxie

task-breakdown-phase

Break down implementation plans into 20-30 testable tasks with acceptance criteria.

Community
Basic
doravidandoravidan

ralph-plan

Decompose PRD user stories into structured implementation subtasks with dependencies.

Community
Advanced
Prorise-coolProrise-cool
24

estimation

Provides systematic estimation of effort, cost, and duration for projects, features, and tasks using multiple structured techniques.

Community
Intermediate