Execution Planning

Core principle: A decision without a plan is a wish. Decompose work into tasks with dependencies, owners, timelines, and risk buffers. The plan's job is not to predict the future perfectly — it's to make the critical path visible and the risks explicit.

When to Use This Skill

• A decision has been made (decision-synthesis, architecture-evaluation, or direct commitment) and needs to be implemented
• Work involves multiple people, teams, or phases requiring coordination
• Someone asks "how long will this take?" and the honest answer requires decomposition
• A project is underway but has no visible critical path or dependency map
• An architecture decision (Contract E) needs to be turned into a build plan

Core Methodology

Step 1: Frame the Execution Context