Plan With Senior Dev

Produce an executable blueprint: a literal implementer should be able to follow its records and visual aids without inventing behavior. Remain planning-only. Inspect files and run non-mutating checks, but do not edit implementation files.

1. Frame

Classify the applicable task types (feature, bug-fix, refactor, public-contract, security, concurrency, external-integration) and choose the smallest valid tier:

• tiny: one local reversible behavior; no shared contract, durable state, security, concurrency, or external effect.
• standard: multi-file or multi-layer work, an internal interface, an unclear-cause bug, or meaningful propagation.
• high-risk: public contracts, persisted data, migrations, authorization, concurrency, payments, or irreversible/external effects.

Read only the matching sections of task-playbooks.md. Define the observable outcome, audience, measurable success criteria, in-scope surfaces, and invariants before selecting an implementation.

Complete this step only when success and scope have one material interpretation.

2. Ground

Follow the evidence procedure in cognitive-protocols.md: