@dreki-gg/pi-plan-mode 0.23.0 → 0.24.0

package/skills/planning-context/SKILL.md

@@ -37,6 +37,17 @@ Caveman-lite: professional, tight, no filler. Bullet points over prose. Update i
 
 `context.md` is the input to `submit_plan`, not a duplicate of it. Before finalizing, re-read it: every open question resolved, every decision justified. The handoff is the distilled conclusion; `context.md` is the reasoning that earned it.
 
+## Large work: initiatives
+
+When the work is too large for a single coherent execution session, or spans several
+subsystems with dependencies between chunks, do not force it into one general plan. Create
+an **initiative** (`submit_initiative`) and decompose the work into multiple plans, each
+linked with `initiative` and ordered with `depends_on_plans`. The initiative's status is a
+projection of its member plans; `initiative_status` shows which plans are *ready* (all
+dependencies done) so work can be divided across sessions or subagents. Keep the
+initiative-level deliberation (why this breakdown, the ordering, what each plan owns) in
+the initiative's `INITIATIVE.md` overview; each member plan keeps its own `context.md`.
+
 ## Relationship to prototypes
 
 For visual/UI work, a prototype is the visual sibling of `context.md` — see the `visual-prototype` skill. Both are deliberation artifacts. Written reasoning lives here; visual reasoning lives in the prototype.