task-builder

Break down PRDs into vertical slices with plan.md and task files.

Updated Feb 24, 2021
One-click install
npx skills add https://github.com/roderik/roderik.github.io --skill task-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-builder
Source: https://github.com/roderik/roderik.github.io/tree/main/.agents/skills/task-builder
Command: npx skills add https://github.com/roderik/roderik.github.io --skill task-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating messy PRDs into concrete, end-to-end task plans that can be handed to teams and executed without ambiguity.

Core Features & Use Cases

  • Tracer bullet first to validate architecture with a minimal end-to-end slice.
  • Vertical-slice decomposition into milestones and self-contained tasks using task templates.
  • Output artifacts: plan.md, tasks/..., and updated module mappings and anti-requirements based on codebase exploration.
  • Ensures self-contained tasks that can be implemented by a fresh Claude session without reading other tasks.

Quick Start

Provide the PRD and any constraints, and I will generate a complete tracer-bullet task breakdown with plan.md and ready-to-write task files.

Frequently Asked Questions about task-builder

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

FAQPage Schema
How do I break down an approved PRD into actionable tasks for my team?

To break down an approved PRD, you decompose it into vertical slices and self-contained tasks using a tracer bullet approach. This generates a plan.md, milestones, and task files with YAML frontmatter, ensuring deterministic execution without ambiguity.

What is a tracer bullet in software task planning and when do I need it?

A tracer bullet is a minimal end-to-end slice used to validate architecture before full implementation. You need it when decomposing a PRD to ensure the foundational architecture works, allowing a fresh Claude session to execute subsequent tasks independently.

How do I create self-contained development tasks that do not require reading other tasks?

You create self-contained tasks by generating markdown files with YAML frontmatter that reference exact codebase paths discovered during exploration. Each task includes a tracer bullet and module mappings, enabling implementation by a fresh session without reading other tasks.

Can I generate module mappings and anti-requirements directly from a PRD?

Yes, you can generate updated module mappings and anti-requirements from codebase exploration aligned to the PRD. The task planning process explores the codebase to output these artifacts alongside milestones and verification protocols.

What's the best way to translate messy product requirements into vertical slice milestones?

The best way to translate messy product requirements is vertical-slice decomposition into milestones using task templates. This approach validates architecture first with a tracer bullet, then outputs a structured plan.md and ready-to-write task files.