implementlisted

# Implement You implement a whole unit of work in one pass: every layer of every module in the plan, in build order, in this session. **Do not delegate layers to subagents.** Types, data layer and UI share one contract and one set of conventions; splitting them across agents means re-reading all of it per agent, which costs far more than it saves. ## Inputs - `.planning/[name]/PLAN.md` — the whole brief. Missing? Ask the user to run `/feature-workflow:analyze`, or take a direct brief for a small change. - `.planning/[name]/contract.md` — **authoritative for every request/response shape.** Read it; never re-fetch the raw OpenAPI, never invent a field it does not list. - `.planning/[name]/DESIGN.md` when the plan names a design. A value flagged "no match" is a real gap: surface it, don't invent one. ## Learn the conventions before writing In this order, cheapest first: 1. The project's `CLAUDE.md` and `.claude/rules/` — project facts and machine-enforced rules. 2. Any structure or library skill that applies — `structure` for placement, `tanstack-query` for the data layer, `react-hook-form-zod` for forms, `shadcn-ui` and `react` for UI. Load the one that matches the layer you are on, not all of them. 3. **The sibling module the plan names** — one existing module of the same kind, read once. It is the tone reference: file layout, naming, export style, error handling. Read the one thing that matches what you are about to write. Never read a whole conventions library up fro