Skip to content

Latest commit

 

History

History
47 lines (31 loc) · 2.08 KB

01-planning.md

File metadata and controls

47 lines (31 loc) · 2.08 KB

01. Planning Phase

Goal: Measure twice, cut once. No code is written without a plan.

1.1 Investigate Before Proposing

Before writing any implementation plan:

  1. Read existing docs: Check docs/, README.md, and VISION.md.
  2. Trace the code: Use search tools to understand the current architecture.
  3. Map the problem: Identify the root cause, not just the symptom. Trace the full call chain.
  4. Check Knowledge: Review existing Knowledge Items (KIs) or wikis.
  5. Assess blast radius: Which other components, tests, or docs will this change affect?

1.2 Implementation Plans

Every non-trivial feature gets a written plan before any code changes.

  • Location: docs/plans/PLAN-{NNN}-{short-slug}.md
  • Registry: docs/plans/README.md

Plan Template

Use the Plan Template for all new plans.

It must cover:

  • Problem Statement: Why this matters.
  • Proposed Changes: File-by-file impact.
  • Execution Order: Priority of tasks.
  • Verification: Exact steps to prove it works.

Solo Mode: For changes under 2 hours, use the Solo Plan Template — a 5-line version that captures intent without ceremony. The plan can live in a commit message or a quick .md file. The point is: think before you type.

1.3 User Approval Gate

CRITICAL RULE: Always show the plan before making code changes.

  1. Create the plan file.
  2. Notify the user/lead.
  3. Wait for explicit approval.
  4. If changes are requested, update the plan and re-request approval.
  5. Only proceed to code when the plan is locked.

Solo Mode: You are your own approver, but the ritual still matters. Write the plan → walk away for 5 minutes → re-read it → then code. This "cool-down review" catches 80% of architecture mistakes that excitement blinds you to.


Related: 00-Mindset · 02-Execution · 04-Documentation · AI Planning · Plan Template