ctx-leanlisted

# CTX Lean Hold a context-restraint contract while completing settled work. Lean is not a lightweight planning ceremony; it investigates and executes when authorized. ## Route Use Lean when the desired outcome is settled, regardless of code size. Technical uncertainty, architectural depth, or a difficult bug does not require a PRD. Escalate to `ctx-prd` only when progress requires an unresolved consequential product decision about user behavior, scope, visual direction, safety, or staged acceptance. Preserve the original verb: - “Build,” “fix,” “change,” or equivalent authorizes execution. - “Analyze,” “explain,” “review,” or “plan” authorizes only that result. ## 1. Align silently Inspect the prompt and available sources for intent, observable success, constraints, and current truth. Ask only when one missing technical answer blocks safe execution or a destructive choice requires authorization. Resolve ordinary choices from repository evidence and established patterns. Hold this ephemeral slice in session state: ```text Goal: <one settled outcome> Boundaries: <in scope / out of scope / preserve> Acceptance: <observable proof> Current slice: <smallest complete vertical change> ``` Resolve whether an existing canonical PRD encompasses the work. Prefer explicit project context and already-linked artifacts; never scan unrelated notes. When exactly one PRD owns the work, use it for lifecycle continuity. If ownership is materially ambiguous, call `AskOne`. Do not create