prd-to-tasks
Break a PRD into independently-grabbable Backlog tasks using tracer-bullet vertical slices. Use when user wants to convert a PRD to tasks, create implementation tickets, or break down a PRD into work items.
Best use case
prd-to-tasks is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Break a PRD into independently-grabbable Backlog tasks using tracer-bullet vertical slices. Use when user wants to convert a PRD to tasks, create implementation tickets, or break down a PRD into work items.
Teams using prd-to-tasks should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/prd-to-tasks/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How prd-to-tasks Compares
| Feature / Agent | prd-to-tasks | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Break a PRD into independently-grabbable Backlog tasks using tracer-bullet vertical slices. Use when user wants to convert a PRD to tasks, create implementation tickets, or break down a PRD into work items.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# PRD to Tasks Break a PRD into independently-grabbable Backlog tasks using vertical slices (tracer bullets). ## Process ### 1. Locate the PRD Ask the user for the PRD — it may be a Backlog document, a file in the repo, or pasted inline. If the PRD is a Backlog document, fetch it with `document_view`. If it's a file, read it from disk. ### 2. Explore the codebase (optional) If you have not already explored the codebase, do so to understand the current state of the code. ### 3. Draft vertical slices Break the PRD into **tracer bullet** tasks. Each task is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer. Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible. <vertical-slice-rules> - Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick ones </vertical-slice-rules> ### 4. Quiz the user Present the proposed breakdown as a numbered list. For each slice, show: - **Title**: short descriptive name - **Type**: HITL / AFK - **Blocked by**: which other slices (if any) must complete first - **User stories covered**: which user stories from the PRD this addresses Ask the user: - Does the granularity feel right? (too coarse / too fine) - Are the dependency relationships correct? - Should any slices be merged or split further? - Are the correct slices marked as HITL and AFK? Iterate until the user approves the breakdown. ### 5. Create the Backlog tasks For each approved slice, create a task using `task_create` (consult `get_task_creation_guide` for structure). Create tasks in dependency order (blockers first) so you can reference them in later tasks. Each task should include: - **Title**: the slice title - **Description**: a concise description of the end-to-end behavior (not layer-by-layer implementation). Reference the parent PRD document rather than duplicating content. - **Acceptance criteria**: checkable criteria for completion - **Dependencies**: note which other tasks must complete first, or "None - can start immediately" - **Context**: which user stories from the PRD this addresses If the PRD is a Backlog document, link back to it in each task's description. Do NOT modify the parent PRD document.
Related Skills
write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then store as a Backlog document. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
team-lead
Orchestrates large bodies of work (features, refactors, milestones, backlog tasks) using sub-agents as a team. Use this skill when the user explicitly asks you to "take responsibility", "orchestrate", "lead", or "team-lead" a set of tasks or a milestone. This is a manual-trigger skill — only activate when the user clearly invokes it.
improve-codebase-architecture
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
astro
Skill for using Astro projects. Includes CLI commands, project structure, core config options, and adapters. Use this skill when the user needs to work with Astro or when the user mentions Astro.
webiny-api-tasks-catalog
api/tasks — 2 abstractions.
hunting-for-suspicious-scheduled-tasks
Hunt for adversary persistence and execution via Windows scheduled tasks by analyzing task creation events, suspicious task properties, and unusual execution patterns that indicate T1053.005 abuse.
detecting-malicious-scheduled-tasks-with-sysmon
Detect malicious scheduled task creation and modification using Sysmon Event IDs 1 (Process Create for schtasks.exe), 11 (File Create for task XML), and Windows Security Event 4698/4702. The analyst correlates task creation with suspicious parent processes, public directory paths, and encoded command arguments to identify persistence and lateral movement via scheduled tasks. Activates for requests involving scheduled task detection, Sysmon persistence hunting, or T1053.005 Scheduled Task/Job analysis.
doing-tasks
Use when executing any task. Work through plans systematically, tracking progress, handling blockers, and coordinating with other skills. The central execution skill.
search-tasks
Search and browse tasks on OpenAnt. Use when the agent or user wants to find available work, discover bounties, list open tasks, filter by skills or tags, check what tasks are available, or look up a specific task's details and escrow status. Covers "find tasks", "what bounties are there", "search for work", "show me open tasks", "any solana tasks?".
my-tasks
View your personal task history and status on OpenAnt. Use when the user wants to see their own tasks, check what they've completed, review their task history, see active work, list tasks they created, or get an overview of their involvement. Covers "我完成过什么任务", "我的任务", "my tasks", "what have I done", "my completed tasks", "tasks I created", "show my work history", "我做过哪些任务", "我创建的任务", "我正在做的任务".
monitor-tasks
Monitor task activity, check notifications, and view platform stats on OpenAnt. Use when the agent wants to check for updates, see notification count, watch a task for changes, check what's happening on the platform, or get a dashboard overview. Covers "check notifications", "any updates?", "platform stats", "what's new", "status update", "watch task". For personal task history and listing, use the my-tasks skill instead.