@theglitchking/persistent-planning 3.0.1 → 3.1.0

package/templates/lg/phase.md

@@ -21,6 +21,17 @@ Tasks with no inter-dependencies can be marked `parallelizable: true` in their f
 so subagent teams can pick them up concurrently.]
 
 - [ ] (no tasks yet — run `/start-task "Task name" --parent PHASE_SLUG_PLACEHOLDER`)
+- [ ] **Validate success through comprehensive testing** (MANDATORY — second-to-last)
+- [ ] **Documentation pass — create/update/deprecate docs** (MANDATORY — last)
+
+> The two mandatory closing tasks above MUST remain the last two tasks of this phase.
+> Add new tasks above them; never after. A phase cannot be marked `done` until both are
+> `done`, and neither may be `parallelizable` — they gate on everything before them.
+>
+> - **Validate success**: prove the phase's work with tests that fail if it breaks.
+> - **Documentation pass**: create/update/deprecate every doc this phase touches —
+>   what it is, where it lives, how to fix it, how to operate it, why it matters.
+>   If hit-em-with-the-docs is installed, use it for this pass.
 
 ## Decisions Made
 [Phase-level decisions that affect multiple tasks. Format: `**Decision**: rationale`.]
@@ -30,8 +41,13 @@ so subagent teams can pick them up concurrently.]
 
 Status enum: `draft | active | paused | done | archived`
 
-When all tasks are `done`, mark this phase `done`. When archived, this directory and
-its tasks/atoms move to `.planning/archive/PHASE_SLUG_PLACEHOLDER/`.
+When all tasks are `done`, mark this phase `done`. Checking every box in this phase
+IS the completion signal — `/plan-status` reads it straight off the artifacts.
+
+When complete, retire it with `/archive-plan PHASE_SLUG_PLACEHOLDER`: the whole
+directory (tasks and atoms with it) moves to the gitignored
+`.planning/.archive/PHASE_SLUG_PLACEHOLDER/` and the frontmatter above is stamped
+`status: archived` + `archived_on`. Nothing is destroyed.
 
 ---
 

package/templates/lg/task.md

@@ -27,7 +27,7 @@ via `/start-atom "Atom name" --parent TASK_SLUG_PLACEHOLDER` — these become fi
 under `atoms/` that subagents read via the planning MCP.
 
 Inline checkbox vs. standalone atom file — see anti-pattern doc:
-docs/atom-granularity.md.]
+.documentation/standards/atom-granularity.md.]
 
 - [ ] (no atoms yet — add inline checkboxes here for simple atoms,
       or run `/start-atom "Atom name" --parent TASK_SLUG_PLACEHOLDER` for complex ones)