planning

Structured task decomposition and tracking.

⭐4stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill facilitates structured task decomposition and dynamic progress tracking through living documents. It enables users to transform complex, high-level goals into actionable steps with built-in dependency management. Unlike static planning tools, it focuses on adaptability, allowing plans to evolve in real-time as new information is discovered during execution.

Use Cases

  • Software Development: Breaking down complex feature implementations into granular subtasks, managing blockers, and tracking implementation status in a structured YAML format.
  • Research and Discovery: Managing exploratory projects where the next steps are contingent on initial findings, allowing the plan to serve as a living record of progress and decisions.
  • Operational Workflow Optimization: Documenting and executing multi-stage business processes that require flexible adjustment and clear visibility into task ownership and completion.
nameplanning
description"Structured task decomposition and tracking."
licenseMIT
tier1
related[play-learn-lift, scratchpad, plan-then-execute, action-queue, sister-script, debugging, session-log]
tags[moollm, decomposition, tracking, tasks, strategy]

Planning

Structured task decomposition and tracking.

Turn complex goals into actionable steps.

[!TIP] Plans here are living documents. Unlike plan-then-execute, these evolve as you learn.


What This Is

A flexible planning system for:

  • Breaking down large tasks
  • Tracking progress
  • Adapting as you learn
  • Documenting decisions

Unlike plan-then-execute/: Plans here are living documents that evolve.


Structure

# PLAN.yml
plan:
  goal: "Implement authentication system"
  status: in_progress
  
  tasks:
    - id: 1
      name: "Design auth flow"
      status: done
      
    - id: 2
      name: "Implement login endpoint"
      status: in_progress
      subtasks:
        - "Create route handler"
        - "Add validation"
        - "Write tests"
        
    - id: 3
      name: "Add session management"
      status: blocked
      blocked_by: 2

Key Difference from plan-then-execute

Planning Plan-Then-Execute
Plans evolve Plans are frozen
Flexible Auditable
For exploration For security
Adapts to findings Requires approval gate

Use planning/ when you need to adapt. Use plan-then-execute/ when you need control.


Contents

File Purpose
SKILL.md Full protocol documentation
PLAN.yml.tmpl Plan template
PROGRESS.md.tmpl Progress template

The Intertwingularity

Planning is play-learn-lift applied to task decomposition.

graph LR
    PL[🗂️ planning] -->|LEARN stage of| PLL[🎮📚🚀 play-learn-lift]
    PL -->|frozen variant| PTE[📋 plan-then-execute]
    PL -->|thinking in| SP[📝 scratchpad]
    PL -->|logs to| SL[📜 session-log]

Dovetails With

Sister Skills

Skill Relationship
plan-then-execute/ Frozen, auditable plans
play-learn-lift/ Planning IS LEARN stage
scratchpad/ For freeform thinking
session-log/ Track planning progress
roberts-rules/ Structured deliberation for planning decisions
adversarial-committee/ Multiple perspectives on plan viability

Protocol Symbols

Symbol Link
PLAY-LEARN-LIFT PROTOCOLS.yml
Direction Destination
⬆️ Up skills/
⬆️⬆️ Root Project Root
📋 Sister plan-then-execute/
🎮 Sister play-learn-lift/