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.

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

Navigation

Direction	Destination
⬆️ Up	skills/
⬆️⬆️ Root	Project Root
📋 Sister	plan-then-execute/
🎮 Sister	play-learn-lift/

planning

Planning

What This Is

More from simhacker/moollm

self-repair

probability

memory-palace

persona

dog

storytelling-tools