get-tasks

Converts an approved PRD into dependency-ordered task files with acceptance criteria and rollback plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A PRD states what to build but not in what order, what can run in parallel, or how to prove each piece is done. This Skill turns an approved PRD into a tracked set of executable task files, preventing heroic single-pass changes and arbitrary build orders that break halfway. ## Core Features & Use Cases - Dependency-First Decomposition: Maps a producer-to-consumer dependency graph, slices work vertically into demoable tracer bullets, and handles wide refactors via expand-migrate-contract sequencing. - Fully Specified Task Files: Writes one file per task under tasks/<name>/ with acceptance criteria, five-way verification, blocking edges, size estimates, and rollback procedures, plus a plan.md index with risks and parallelization classification. - Use Case: You have an approved PRD at docs/prd/billing.md for a new billing module. Run this Skill to produce tasks/billing/task-01.md through task-NN.md in dependency order, with checkpoints and a plan document, ready to hand off to incremental implementation. ## Quick Start Break down the approved PRD at docs/prd/billing.md into executable task files with acceptance criteria and a plan document.

Frequently Asked Questions about get-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a PRD into executable tasks?

Run the breakdown in phases: extract commitments from the PRD, map a dependency graph, slice work vertically into demoable tracer bullets, then write one task file per slice with acceptance criteria, verification steps, blockers, and rollback. Get user approval on the task table before writing files.

What is vertical slicing versus horizontal slicing in task breakdown?

Vertical slicing cuts each task through every layer a behavior needs (data, logic, interface, test) so each task is demoable on its own. Horizontal slicing groups work by layer, which produces nothing runnable until the last task and hides wrong assumptions until the end.

When should I not use a PRD task breakdown workflow?

Skip it when no PRD or spec exists yet, when the change is a single obvious edit in one file, or when a task list already exists and you only need execution. In those cases write the PRD first, just make the edit, or go straight to implementation.

How do I handle a task that fails during execution?

Diagnose the exact failure, then decide: fix minor issues inline, revise the task file for rework, insert new tasks and renumber downstream if a dependency surfaced, or re-run the decomposition phases if the plan is fundamentally wrong. Update task files and re-sync the todo list, never silently drop tasks.

Can task breakdown output go to an issue tracker instead of files?

Yes. If project rules or the user designate a tracker like GitHub Issues, Jira, Linear, or beads, publish one item per task, mapping acceptance criteria to the body, blockers to native linking, and size to labels. Choose one target and record it in plan.md to avoid drift.