{"id":"agent-pm-spec-to-tickets","audience":"product-managers","category":"agents","track":"agents","technique":"format","title":"Brief an agent to turn a spec into clean tickets","free":false,"task":"You want an AI agent to turn a feature spec into tickets. Write its brief: one ticket per v1 requirement (skip anything marked v2), each title under 8 words and starting with a verb, acceptance criteria copied from the spec only, and never assign tickets or put them in a sprint. Output exactly 5 numbered plain-text lines: one create_ticket per v1 requirement in spec order, then DONE.","materialLabel":"Feature spec and actions (attached to your prompt automatically)","material":"Spec: Invoice reminders (Tallyhub) - owner: Dana\n\nGoal: help customers get paid faster by reminding their clients automatically.\n\nR1 (v1) Send an email reminder 3 days before an invoice's due date. Acceptance: email goes out at 9 a.m. in the customer's time zone.\nR2 (v1) Send a reminder on the due date if unpaid. Acceptance: no reminder if the invoice is marked paid.\nR3 (v2) SMS reminders. Needs carrier contract first.\nR4 (v1) Let customers turn reminders off per client. Acceptance: toggle on the client page, off by default for existing clients.\nR5 (v1) Show reminder history on the invoice page. Acceptance: list of sent reminders with date and time.\nR6 (v2) AI-written reminder text.\n\nTeam: Arjun (backend), Sofia (frontend). Next sprint starts Nov 16.\n\nAvailable actions:\ncreate_ticket(title, acceptance_criteria)\nassign(ticket, person)\nadd_to_sprint(ticket, sprint)\nDONE(summary)","rules":[{"type":"numberedItems","count":5},{"type":"plainText"}],"promptHints":[{"label":"Scopes to v1","patterns":["v1","v2","skip"]},{"label":"Sets the title rule","patterns":["title","verb","8 words"]},{"label":"Copies criteria","patterns":["acceptance","from the spec","copy"]},{"label":"Forbids assigning","patterns":["assign","sprint"]},{"label":"Shows the action-log format","patterns":["action:","action log","numbered","\\b1\\.","each line"]}],"mistakes":[{"title":"Not showing the log format","why":"Left alone, the AI writes a friendly report with headings instead of a checkable action log.","fix":"Show it literally: \"Format every line like 1. ACTION: tool(args), then ASK_HUMAN: and DONE: lines. Plain text.\"","checks":["numberedItems","plainText"]},{"title":"Not scoping to v1","why":"The AI makes a ticket for every line, including future v2 ideas.","fix":"Add: \"One ticket per v1 requirement. Skip v2.\"","checks":["r0"]},{"title":"No title or criteria rules","why":"The AI writes long titles and adds its own acceptance criteria.","fix":"Say: \"Title under 8 words, starting with a verb. Criteria copied from the spec.\"","checks":["r1"]},{"title":"Letting it plan the sprint","why":"The AI assigns tickets to people and adds them to the next sprint.","fix":"Add: \"Never assign or add to a sprint.\"","checks":["r2"]}],"hint":"Tickets go wrong when the agent adds scope or decides who does what. Tell it what's in, how to write each one, and what's not its call.","rubricLabels":["There are tickets for exactly R1, R2, R4 and R5, and none for R3 or R6 (v2)","Each ticket title is under 8 words and starts with a verb, and each ticket's acceptance criteria restate that requirement's acceptance line from the spec and add no new criteria","There is no assign or add_to_sprint line, and the last line is a DONE line"]}