planzlisted

# planz - Hierarchical Project Planning Binary: `~/.local/bin/planz` | DB: `~/.local/share/planz/plans.db (SQLite WAL) ## Fractal Planning: Refine Until Nothing is Left for Interpretation **The core principle:** Start with a high-level outline, then iteratively refine each node until every leaf task is so specific that executing it requires no further thought or decision-making. ### The Process 1. **Start broad** - Create 3-7 top-level phases that capture the major milestones 2. **Identify ambiguity** - Look at each leaf node and ask: "Could I execute this right now without any decisions?" 3. **Refine the unclear** - Use `planz refine` to break down ambiguous nodes into smaller, clearer steps 4. **Repeat** - Continue until every leaf node is atomic and unambiguous 5. **Execute & update** - Work through leaves, marking done, and refine new ambiguity as it emerges ### ⚠️ Important: No Slashes in Task Names The `/` character is the path separator. **Never use slashes in task titles:** ```bash # ❌ WRONG - creates nested path "API" -> "auth endpoint" planz add myplan "API/auth endpoint" # ✅ CORRECT - use other separators planz add myplan "API - auth endpoint" planz add myplan "API: auth endpoint" planz add myplan "API auth endpoint" ``` ### What "Nothing Left for Interpretation" Means A leaf node is **ready for execution** when: - ✅ You know exactly which file(s) to touch - ✅ You know the specific change to make - ✅ No design decisions remain - ✅ Success criteria is obv