I built a set of commands that enforce a simple discipline: no code gets written until you've reviewed and approved a written plan. The workflow: /bt-research → /bt-plan → /bt-review (repeat 1-6x) → /bt-implement The key insight (from Boris Tane's workflow): plans are shared mutable state. Instead of steering the AI through chat, you both edit the same markdown file. You add inline notes like "NOTE: this should be a PATCH, not PUT" and the AI updates the plan accordingly. Blog post with full details: https://ekadetov.github.io/2026/02/23/bt-plan-first-workflow... GitHub: https://github.com/ekadetov/bt-opencode-commands