plan-templatelisted

# Plan template Trusted plan; no downstream product decisions required. **Kind** template · **Used by** [architect](../../agents/architect.md) · **When** the ticket is understood and the code is read (develop-flow step 1f, or 1b for the [bug brief](#bug-brief)) · **Ends with** `$TROIKA_SCRATCHPAD/plans/<TICKET>.md`, ready for the [plan-review](../plan-review/SKILL.md) gate or the [reproduction](../qa-verify/SKILL.md#reproduce) gate **One file, two shapes.** A feature ticket fills the full template below and is approved by plan review. A bug ticket fills the shorter [bug brief](#bug-brief) and is approved by a reproduction on the base checkout. Both are written to the same path, because every later role — reviewer, tester, qa, releaser — reads the requirements from `plans/<TICKET>.md` and must not care which path produced them. ## Fill rules - Delete sections that don't apply; never leave a placeholder in. - Requirements are numbered and testable — every later role cites them by number, so the numbers stay stable across rewrites. - Repo order follows PROFILE.md › Dependency order (`#dependency-order`). - Pin cross-repo contracts or mark sequential. - Map every requirement to unit/QA proof. - Name stack limits and alternate coverage. - Make out-of-scope explicit, including forbidden repos. - Block on scope/behavior questions; record other assumptions for PR body. ## Template ````markdown # <TICKET> — <title> Ticket: <link> Status: draft | awaiting approval | approved <d