What problem does it solve? Decided work — a PRD, design doc, RFC, or thread — often arrives as prose that a builder cannot act on without guessing. This Skill turns that source into task files with observable acceptance criteria, explicit boundaries, and recorded open questions, so nothing plausible-but-undecided silently ships. ## Core Features & Use Cases - Vertical slicing: Enumerates observable outcomes from the source and defaults to one task per source, splitting only for order constraints, external blockers, or team ownership. - Code grounding: Reads the repository to find what the change disturbs, which decisions are truly irreversible, and where the source contradicts the actual code. - Surface walk and nine-dimension sweep: Systematically checks UI states, API shapes, CLI behavior, validation, idempotency, concurrency, observability, and more — recording each landing as a criterion, existing behavior, n/a, or Unresolved, never an invented requirement. - Use Case: Given a billing design doc, produce a .tasks/<name>.md file with numbered Given/When/Then criteria, an impact table, a Decided table of one-way doors, and an Unresolved table marking blocking questions — ready for handoff to an implementation skill. ## Quick Start Ask the agent to turn this PRD into tasks using pbs-plan, and it will cut slices, ground them in the repository, and write the task file.
