Standard Workflow 1. Think through the problem, read the relevant files, and write a plan to where is in format and is kebab case. 2. Make the first screen useful: status, owner, one sentence, current shape, target shape, and proof. 3. Include a checklist of implementation tasks that can be checked off as work lands. 4. Execute autonomously in small checkpoints. Pause for user input only when the plan has competing product or architecture choices, unresolved requirements, destructive actions, or broad scope risk. 5. For non-trivial changes with multiple plausible approaches, 3+ files, or arch…