breakdown
Breakdown
Decompose a PRD and architecture into small, ordered, verifiable development tasks — the final output of the analytics pipeline.
When to Use
- A PRD and architecture document exist and are approved
- You need to turn requirements into implementable work items
- The work is too large to start without a task list
- Tasks need to be parallelized across agents or sessions
- You need to communicate scope and order to a developer or team
When NOT to use: The work is a single-file change with obvious scope, or a task list already exists and is still accurate.
Input
prd.mdfrom the artifact folder (required)architecture.mdfrom the artifact folder (required)context-map.mdfrom the artifact folder (recommended)
More from olamedia/analytics-skills
analyze-project
Use when starting work on any project to produce or update living documentation (TechStack.md, ProjectStructure.md) that bootstraps context for any AI agent session. Run before any feature work, or periodically to keep docs current.
13humanizer
>-
12architect
>-
12goal-definition
Use when you have a raw idea or request and need to define a clear goal with success criteria before exploring solutions. Use when requirements are vague, when "what does done look like" is unclear, or when assumptions need surfacing.
11prd
Use when you have a chosen direction and need to formalize requirements into a Product Requirements Document. Use when user stories, acceptance criteria, and scope boundaries need to be written down before architecture or implementation.
10analyze
Use when you have a raw idea or request and want to run the full analytics pipeline automatically — from research through to an interlinked task list. Best for straightforward problems where the full pipeline can flow with minimal back-and-forth.
10