implementation-plan

# Implementation Plan Design the smallest sequence of independently verifiable vertical slices that satisfies the accepted intent. ## Authority Boundary Planning is read-only by default. Do not edit source, create issues, install dependencies, commit, push, deploy, or publish while producing a plan unless the user explicitly requested that action. ## Workflow 1. **Read the contract:** Re-read the accepted spec or request. Extract requirements, non-goals, constraints, success criteria, authority limits, and unresolved decisions. 1. **Inspect reality:** Read repository instructions, status, relevant source, tests, manifests, task definitions, recent history, and existing patterns. Preserve staged, unstaged, and untracked user work. 1. **Verify APIs:** Confirm installed dependency versions and read their exact local source plus current authoritative documentation before planning against an unfamiliar API. 1. **Map the change:** Describe the current flow, desired flow, affected components, interfaces, data, trust boundaries, and operational consumers. Record existing code to reuse or delete. 1. **Compare real options:** For a meaningful architectural or tooling choice, present two or three numbered options with complexity, maintenance, security, reversibility, and migration trade-offs. Recommend the simplest adequate option. 1. **Lock boundaries:** Assign each file or package one responsibility. Prefer deep modules that hide decisions over pass-through layers, put tests and ...