Pre Planning

Purpose

Standardize how plans are captured. Every significant piece of work should start with a plan file that persists the what/why/how before coding begins.

When to Use

• Before any multi-phase feature addition
• Before system architecture changes
• Before agent/skill system modifications
• When the user says "plan", "let's plan", "make a plan", "plan out"

Output Location

.docs/planning/plans/#-plan-name.md

Numbering

Auto-increment by scanning existing files: ls .docs/planning/plans/*.md | wc -l + 1

Required Sections

1. Header — Plan #, date, commit hash, status, author
2. Context — what exists now, what's the gap