Plan — Persistent Strategic Plans

The Core Idea

Plans capture strategic direction that must survive across sessions. When you start multi-session work or make architectural decisions, save a plan immediately — the reasoning is fresh now and won't be available later. When work is done, mark the plan complete so future sessions don't waste effort on finished goals. A stale plan actively misleads; it's worse than having no plan at all.

When to Create a Plan

Plans matter most when context needs to survive session boundaries. Without a plan, the next session starts from scratch.

• Starting multi-session work — save a plan with goals and approach so the next session knows where to pick up
• After architectural decisions — capture the direction immediately so future sessions don't re-derive or contradict it
• After brainstorming/design sessions — the approved design should outlive the conversation that produced it
• New features spanning multiple sessions — a plan keeps the thread when context compacts or sessions end
• User describes project direction or roadmap — that strategic context is exactly what plans are for

How to Create a Plan