Planning Doc

Create and maintain PLAN.md files tied to git branches. The plan serves two audiences:

• Agent: determine where things are at and continue from where they left off.
• Human: quickly see the plan, changes, and current status.

Plan Steering

• Always read PLAN.md before making changes.
• On resumed sessions, read the latest Status Updates entry and run git diff --stat to detect drift.
• If the user says "continue", use the newest status update to determine what changed last and what to do next.
• Treat PLAN.md as a resume log, not a task tracker — keep entries short and factual.
• Use checkboxes in the Plan section to track progress.

Workflow

1. Determine the current branch: git rev-parse --abbrev-ref HEAD.
2. If on the default branch (usually main):
   • Stop and prompt the user to create and check out a feature branch before proceeding.