summaryrefslogtreecommitdiff
path: root/skills/executing-plans/scripts/task-start
diff options
context:
space:
mode:
authorJesse Vincent <jesse@primeradiant.com>2026-09-18 17:28:09 -0700
committerJesse Vincent <jesse@primeradiant.com>2026-09-18 17:28:09 -0700
commitcffb7c95b64524cd59ddb4d1c9d2c2675482315e (patch)
tree38263673a455cdf894f19301aa284009d7edb1d8 /skills/executing-plans/scripts/task-start
parent835c5f951cce3e169b755218a9d8f26b5854f0d5 (diff)
Plans as directories, and a boundary check before each next planplan-directories
A plan is a directory: 00-header.md plus one NN-<task>.md per task. The brief for task N is the header plus that file; sdd-workspace, task-brief, review-package, task-start and task-done take a file or a directory. Before starting the next plan in a set, executors run scripts/plan-boundary, which names every identifier the plan consumes from earlier plans that the code as built does not contain, in the next plan and in every later plan's Plan Set entry, and fix the plan until it prints clean. Measured: the directory form executes the same as the file form (inline 9/9, SDD 6/6, same cost) and plans at the same volume; the gate kept a five-plan set consistent with the code 2/2 against a planted cross-plan naming conflict, where a per-ruling duty managed 0/2.
Diffstat (limited to 'skills/executing-plans/scripts/task-start')
-rwxr-xr-xskills/executing-plans/scripts/task-start2
1 files changed, 1 insertions, 1 deletions
diff --git a/skills/executing-plans/scripts/task-start b/skills/executing-plans/scripts/task-start
index fab75b5..bddb0f5 100755
--- a/skills/executing-plans/scripts/task-start
+++ b/skills/executing-plans/scripts/task-start
@@ -5,7 +5,7 @@
# cut from. One tool call instead of two, because every call in an inline
# session is a turn that re-reads the whole context.
#
-# Usage: task-start PLAN_FILE TASK_NUMBER
+# Usage: task-start PLAN TASK_NUMBER (PLAN: the plan file, or a plan directory)
# Prints:
# brief: <path to the task's brief file>
# base: <full SHA of HEAD>