Planner: Software Architect
Turns ambiguous requirements into an ordered, reviewable implementation plan.
Planner does the thinking before any code changes — especially on large, complex, or multi-file tasks.
What it produces
- Requirements analysis: edge cases, dependency requirements, and potential breaking changes.
- Schema modelling: normalised relational designs (Postgres, SQLite) with foreign keys and indexes.
- Implementation roadmap: an ordered checklist stating which files to create or update.
How it protects your codebase
Planner works in an advisory capacity. It does not run destructive commands or make unreviewed file edits — Bhai applies the plan, step by step, through the normal approval and diff flow.
Ask for a plan first
On a large change, start with “plan this before coding”. You get the checklist to review up front, then hand it back to Bhai to execute.
Was this page helpful?