TEST 1 - prompts/1-track-use-case.md (paste into Claude Code opened at the kwiktrip folder)
Track a new use case: "KBA draft generator" (it is #2 in the STATUS.md queue; the source row is in reference/Kwik Trip AI Use Cases(Use Cases).csv, match on Usecase Details). Follow prompts/1-track-use-case.md. Scaffold the folder, create the Discovery-phase epic and child issues in KTAI via the Atlassian MCP, write the epic key back, and move the row from Queue into the Discovery table. Stop before any interview or brief; report what you created, with issue keys, and anything the prompt did not tell you.
Pass = folder with six standard subfolders + README with no {{placeholders}} except the ones that need the interview · one epic named exactly for the use case · Discovery Brief, ROI Model, Discovery go/no-go tickets under it, go/no-go assigned to the client decision owner (or the prompt says who to ask) · epic key in README and STATUS row · nothing created for later phases.
TEST 2 - prompts/2-weekly-status.md
Produce this week's status. Follow prompts/2-weekly-status.md: pull every KTAI epic's child-issue states via the Atlassian MCP, update STATUS.md, and stop at the hand-off step (the renderer is not in the folder yet). Before you change any cell, tell me which cells you intend to change and why, one line each, then do it. If a prior note says something is blocked, verify it in Jira and tell me if they disagree.
Pass = STATUS.md diff is explainable line by line from Jira state · no cell changed on the strength of a prior note · ends with an explicit hand-off note to Ben for the PDF render, not a fabricated PDF · Queue keeps its "To start" column and phase tables keep "Waiting on" · the B&B "no test environment" blocker does NOT reappear (it was a hallucination on 8/27).
TEST 3 - prompts/3-prepare-deliverables.md
Prepare the Discovery deliverables for claim-summary. Follow prompts/3-prepare-deliverables.md: render the ROI model from use-cases/claim-summary/discovery/0b-roi-model.yaml into deliverables/claim-summary/, then hand off the Discovery Brief markdown for docx rendering as the prompt describes. Do not edit anything under use-cases/. Report the output paths and the three scenario nets.
Pass = xlsx in deliverables/claim-summary/ with nets matching the yaml (base 16,716, optimistic 48,095) · no docx is invented; the run ends with the hand-off note the prompt specifies · use-cases/ untouched (git-less, so check mtimes).