plan

# Plan Shape only missing intent. Prefer the caller's tracker, if any; otherwise use the conversation or supplied text. Planning produces no AgentOps packet. A clear change can proceed directly. Use established domain names throughout intent, examples, code and validation; [Domain](../domain/SKILL.md) helps when meanings or boundaries are genuinely unclear. ## Workflow 1. Read accepted intent and relevant source owners and active constraints. Resolve only consequential uncertainty; do not reopen settled decisions without new evidence. Identify the caller-visible outcome, scope and first useful check. 2. Describe the intended observable behavior before implementation. Reuse acceptance already supplied in the conversation or bead; clarify only what prevents action or judgment. Name the actor or caller, the event and the observable result. One example often suffices; use Given/When/Then for branching behavior and consequential boundaries. Include non-goals only where they prevent a plausible scope mistake in that existing source. Scope includes the hand-edited owners, affected tests/live consumers and generator-owned companions as a class; it is authority, not a predicted file count. A consequential assumption deserves an early discriminating check, not a general checklist or exhaustive survey. 3. Choose the smallest action that advances acceptance or falsifies the risky assumption. Include recapture of affected bound evidence where nece...