▣User storiesDrop the story in as written, acceptance criteria and all. The agent plans against the criteria, and Review checks them off box by box.DEFAULT CARD · STORY IN, PR OUT
▣Change requestsPaste the request from a customer or a colleague. The agent scopes it, names the risks, and asks before touching anything shared.DEFAULT CARD · SCOPED BEFORE BUILT
✕Support ticketsForward the ticket. The agent reproduces the complaint, traces it to its cause, and files the fix with the ticket linked.BUG CARD · TICKET, CAUSE, FIX
✕Bug triagePaste the report. The agent reproduces, bisects and proposes the fix; you approve at Review.BUG CARD · REPRODUCE, BISECT, FIX
?Decisions to researchAsk the question instead of the change: which mail provider, where a limiter belongs, why a page got slow. It reads the repo and reports back, and writes no code.RESEARCH CARD · NO CODE, A VERDICT
≣Work too big for one cardHand over the whole job. A masterplan splits it into subcards, runs them, keeps their status, and only asks you what the plan itself needs.MASTERPLAN CARD · SPLITS AND TRACKS
↻Migrations and refactorsLong, mechanical, dangerous. Worktree isolation and stage gates make them boring: the agent grinds, you approve.CHORE CARD · ISOLATED WORKTREE
↻Docs and test coverageCards update the docs they touched at Close. Point it at coverage gaps and it writes the specs, Verify runs them, and the diff shows what is covered.CHORE CARD · VERIFY IS THE GATE