execution-planner

Decompose complex software tasks into 5-10 verifiable steps with risks and alternatives.

1|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/zzafergok/skills --skill execution-planner-zzafergok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execution-planner
Source: https://github.com/zzafergok/skills/tree/main/09-planning-process/execution-planner
Command: npx skills add https://github.com/zzafergok/skills --skill execution-planner-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex tasks often derail without a clear plan, causing scope creep and misaligned teams. The execution-planner provides a structured approach to decompose work into a concise, verifiable sequence.

Core Features & Use Cases

  • Structured task breakdown to 5-10 discrete steps with explicit verification criteria.
  • Objective-driven planning that aligns teams before implementation.
  • Risk and alternative analysis to surface trade-offs and guardrails for decision-making.
  • Use cases include feature planning, refactoring, bug-fix orchestration, and kickoff planning for new initiatives.

Quick Start

Plan your next task by outlining the objective, breaking it into 5-10 verifiable steps, and listing the verification criteria, risks, and alternatives before you begin.

Frequently Asked Questions about execution-planner

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

FAQPage Schema
How do I break down complex software tasks into actionable steps?

Workflow planning requires decomposing complex objectives into 5-10 discrete steps with explicit verification criteria. This structured approach ensures teams align before implementation, preventing scope creep and misaligned execution across software projects.

What is the best way to plan a refactoring project with clear verification?

Refactoring planning benefits from objective-driven task breakdown that structures work into concise, verifiable sequences. By defining verification criteria, risks, and alternatives upfront, teams surface trade-offs and establish guardrails for decision-making.

Can I use structured task breakdown for bug fix orchestration?

Yes, bug-fix orchestration uses structured task breakdown to define a concise, verifiable sequence of steps. Applying objective-driven planning with risk and alternative analysis surfaces trade-offs and establishes guardrails for resolving software bugs effectively.

Does deterministic output format help with feature planning and kickoff?

Deterministic output format enforces a defined structure for feature planning including objective, task breakdown, verification criteria, risks, and alternatives. This ensures kickoff planning produces aligned, verifiable sequences without scope creep or misaligned teams.

Why does objective-driven planning include risk and alternative analysis?

Risk and alternative analysis is included to surface trade-offs and establish guardrails for decision-making. Structured task breakdown limits work to 5-10 discrete steps, ensuring teams address potential blockers before implementation begins.