ExecPlan Authoring

Write plans the way a strong software designer would: not as a task list for rearranging code, but as a path to a simpler system with clearer boundaries.

Required inputs

• The user must provide a PRD, RFC, or a detailed problem statement. If missing or unclear, ask for clarification before writing the plan.

Source of truth

• Read {baseDir}/.agent/PLANS.md in full before drafting.
• If {baseDir}/.agent/PLANS.md is missing, copy this skill's PLANS.md to {baseDir}/.agent/PLANS.md, then read that copy as the source of truth.
• Follow PLANS.md exactly. If any instruction conflicts with this skill, PLANS.md wins.

Ousterhout lens

Use John Ousterhout's design philosophy as the default planning lens: