execution-planning

Convert decisions into execution plans with tasks, dependencies, and timelines.

7|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AndurilCode/craftwork --skill execution-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execution-planning
Source: https://github.com/AndurilCode/craftwork/tree/main/skills/execution-planning
Command: npx skills add https://github.com/AndurilCode/craftwork --skill execution-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execution planning prevents stalled delivery by transforming a committed decision into a concrete, coordinated roadmap with tasks, dependencies, timelines, and ownership.

Core Features & Use Cases

  • Work breakdown structure (deliverables → packages → tasks): Decomposes the work into verifiable outputs that fit within one-person-week task sizes.
  • Dependency mapping and critical path: Builds a DAG of task relationships to reveal the true schedule risk chain and quantify slack (float).
  • Three-point duration estimates and milestones: Uses reference-class estimation with O/M/P (PERT-style) timing and defines observable completion proofs, plus risk buffers and resource asks.

Quick Start

Ask: Plan the execution of this decision for a cross-team build, including the work breakdown, dependency DAG with critical path, O/M/P timelines, milestones, ownership, and top execution risks.

Frequently Asked Questions about execution-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn an architecture decision into an actionable execution plan?

To turn an architecture decision into an execution plan, decompose deliverables into a work breakdown structure of verifiable tasks, map dependencies into a DAG, estimate PERT timelines, and assign ownership for coordinated delivery.

What is the best way to map task dependencies and find the critical path for a project roadmap?

Mapping task dependencies to find the critical path requires building a directed acyclic graph (DAG) of task relationships to reveal the schedule risk chain and quantify slack or float for your project roadmap.

How do I use PERT estimation for work breakdown structures?

PERT estimation for work breakdown structures uses reference-class estimation with Optimistic, Most likely, and Pessimistic (O/M/P) durations to calculate three-point estimates, define observable milestones, and allocate risk buffers.

Can I plan execution for a multi-phase engineering delivery across cross-functional teams?

Yes, you can plan execution for multi-phase engineering delivery by creating a prioritized execution risk matrix with RACI-style ownership, ensuring cross-functional teams have clear task assignments and resource asks.

What is the ideal task size when decomposing deliverables for project scheduling?

The ideal task size when decomposing deliverables for project scheduling is one-person-week, which ensures outputs remain verifiable and manageable within the work breakdown structure and dependency graph.

How do I assign RACI ownership for execution risks and milestones?

To assign RACI ownership for execution risks and milestones, map specific team members to task packages within the work breakdown structure, clarifying who is Responsible, Accountable, Consulted, and Informed for each delivery phase.