To Scenarios

Draft executable-quality behavioral scenarios for an issue. The drafted ## Scenarios block becomes the spec that the tdd skill consumes without further approval.

The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.

When this runs

• Called by to-issues for each testable slice after slice breakdown is approved but before publish. Returns the scenarios block to the caller.
• Standalone with an issue reference (number, URL, or path). Fetches the issue, drafts scenarios, edits the body to insert ## Scenarios between ## What to build and ## Definition of Done.

Process

1. Gather context

• Delegated call: read the slice description, parent plan/PRD, sibling slices, and dependencies from the conversation.
• Standalone: fetch the issue from the tracker. Read ## What to build, any existing body sections, and dependencies in ## Blocked by. If the issue references a parent plan/PRD, read it.

If the description is too ambiguous to draft scenarios from, do not invent — surface the ambiguity and stop.