Rigor

Take one concrete code change from request to evidence.

Boundary. Rigor changes code, or diagnoses a defect or slowdown on the way to changing it. Open product questions belong to /interview-me; recommend it and stop when the decisions that define the task are still unknown.

1. Frame and route

Resolve from the request and repository:

• Finish line: the observable condition that ends the task. "Figure out what is wrong" stops at diagnosis; "fix it" continues through implementation and proof. The same split applies to performance diagnosis versus optimization.
• Scope: the affected system and the smallest plausible problem boundary.
• Risk: security, permissions, money, data loss, migrations, concurrency, external compatibility, production access, or a one-way architectural choice.

Then load exactly one playbook: