2026-06-01 00:13:31 -04:00
1 changed files with 9 additions and 5 deletions
@@ -48,11 +48,15 @@ rules via create_rule when you notice a pattern worth codifying — coordinate
 with the operator on whether it belongs in an existing rulebook+topic or a
 new one.
-Plans are tasks with kind=plan. Begin a plan with start_planning(project_id,
+Plans are tasks with kind=plan, and Scribe is the canonical home for them.
-title) — that seeds a plan template and returns the project's applicable_rules.
+When you begin non-trivial work, call start_planning(project_id, title) FIRST —
-Maintain the plan with the normal task tools (update_task for the body,
+before any brainstorming, design, or plan-writing skill runs. start_planning
-add_task_log for progress); its work-logs are the build record. Build plans in
+seeds the plan body, returns the project's applicable_rules, and gives you the
-Scribe via start_planning, not in local .md files.
+task id you'll write into. If a skill or habit tells you to save a plan or spec
 to `docs/superpowers/plans/*.md` or `docs/superpowers/specs/*.md`, that path is
 superseded here: put the spec/plan content in the kind=plan task's body via
 update_task, and record progress with add_task_log. Local .md files are not
 the record — the task is.
 Deletes are recoverable: every delete_* tool moves the entity (and its
 descendants) to the trash and returns a deleted_batch_id. Use list_trash() to