---
plan_id: <short-kebab-slug>
created: <YYYY-MM-DD>
created_by: <planner identity — "Claude (cloud)" | "Claude (minimax)" | operator name>
target_session: claude | minimax | any
status: draft | ready | in_progress | complete | blocked | abandoned
branch: <git branch name, if any>
related_issue: <URL or id, optional>
---

# <Plan title — short, action-oriented>

> Copy this file to `.claude/plans/<slug>.md` and fill in. Use the `superpowers:writing-plans` skill if available.

## Goal

<One sentence. What does "done" look like from the operator's perspective?>

## Background (from planner's conversation)

**This is the most important section for the implementer.** The chat history doesn't transfer between sessions, so anything the planner and the operator discussed but didn't write down goes here.

Cover, in free form:
- **Why this work** — the operator's stated intent, the user story, the bug report
- **Decisions made in chat** — "we agreed to use X over Y because…", "the operator vetoed Z"
- **Dead ends** — "we tried `<approach>` but it failed because…"
- **Constraints** — backwards compat, must-not-break, deadlines, who's affected
- **Links** — relevant commits, prior plans in this folder, external docs, Slack threads

## Context (links the implementer needs)

- **AGENTS.md rules that apply:** <bulleted list, e.g. "PB select fields are not self-service", "file URLs go through `/api/v1/files/`">
- **PB schema fields touched:** <relation ids, new select values needed, new collections>
- **MCP tools involved:** <e.g. `mcp__wfdash-mcp__quote_items_create`, `mcp__wfdash-mcp__orders_update`>
- **Prior art in repo:** <`file:line` refs to similar code to copy from>
- **External references:** <URLs>

## Scope

**In scope:**
-

**Out of scope:**
- (explicitly call these out so the implementer doesn't drift)

## Files to touch

- `src/path/to/file.ts` — create | modify | delete — <one-line: what changes>
- `src/path/to/another.tsx` — modify — <what changes>

## Steps

<Numbered. Each step: action verb + target + a way to verify it landed.>

1. <Step>
   - verify: <command or check>
2. <Step>
   - verify: <command or check>
3. <Step>
   - verify: <command or check>

## Verification

- `pnpm test` — full suite green (or specific test file: `pnpm test src/lib/foo.test.ts`)
- Manual: `<http://localhost:4001/path>` renders <expected>
- Acceptance: <business-level check the operator will care about>

## Risks / open questions

- <Anything the implementer should surface rather than decide alone>
- <Assumptions that might be wrong — call them out so they get validated>

---

## Status (filled by implementer)

<!-- Implementer: update this section as you work. Don't edit anything above this line without writing a status file first. -->

- [ ] Plan read end-to-end + AGENTS.md / CLAUDE.md loaded
- [ ] Branch / working tree confirmed
- [ ] Steps 1..N complete with their verify checks passing
- [ ] `pnpm test` green
- [ ] Manual verification at `http://localhost:4001/...` done
- [ ] Status frontmatter flipped to `complete`

### Report

<Free text. Blockers, surprises, things the planner should know. Link to commits / PRs.>

### Commits / PRs

- `<sha>` — `<message>`