kata-plan-phase

Generate executable PLAN.md prompts with wave-based task dependencies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gannonh/kata-orchestrator --skill kata-plan-phase
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kata-plan-phase
Source: https://github.com/gannonh/kata-orchestrator/tree/main/skills/kata-plan-phase
Command: npx skills add https://github.com/gannonh/kata-orchestrator --skill kata-plan-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill provides a structured approach to breaking down complex phases into executable PLAN.md prompts, ensuring dependencies, waves, and must-haves are captured for reliable execution.

Core Features & Use Cases

  • Decomposes a phase into parallelizable tasks with clearly defined actions, verifications, and done criteria.
  • Builds a wave-based execution plan with 2-3 tasks per plan to balance context and throughput.
  • Generates frontmatter, prompts for researchers and planners, and updates ROADMAP.

Quick Start

Use this skill to plan Phase 01-Foundation: provide the phase name and goals; the skill will output PLAN.md prompts ready for Claude's executors.

Frequently Asked Questions about kata-plan-phase

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

FAQPage Schema
How do I turn roadmap goals into executable phase plans?▼

To turn roadmap goals into executable phase plans, you provide the phase name and objectives to generate actionable PLAN.md prompts. The skill analyzes dependencies and must-haves to output optimized wave execution plans ready for orchestrator execution.

What is wave-based execution planning for software phases?▼

Wave-based execution planning groups phase tasks into parallelizable execution batches to balance context and throughput. It limits plans to 2-3 tasks per wave, ensuring dependencies are mapped and execution context remains manageable for the orchestrator.

How do I decompose a complex phase into parallelizable tasks?▼

Decomposing a complex phase into parallelizable tasks involves translating phase goals into specific actions with defined verifications and done criteria. The skill builds a dependency graph to optimize parallelism while constraining task counts to 2-3 per plan.

Do I need an orchestrator to execute the generated PLAN.md files?▼

Yes, an orchestrator is required to execute the generated PLAN.md files. The skill outputs phase PLAN files containing frontmatter and prompts for researchers and planners, designed specifically to be picked up and run by the downstream orchestrator.

Can I include more than three tasks in a single phase plan?▼

No, phase plans are intentionally limited to 2-3 tasks to balance context and throughput. This constraint ensures reliable execution by preventing the orchestrator from being overwhelmed by excessive task context within a single execution wave.