taskplane 0.22.18 → 0.23.0

package/skills/create-taskplane-task/SKILL.md

@@ -1,45 +1,51 @@
 ---
 name: create-taskplane-task
-version: 1.1.0
-description: Creates structured Taskplane task packets (PROMPT.md, STATUS.md) for autonomous agent execution via the task-runner and task-orchestrator extensions. Use when asked to "create a task", "create a taskplane task", "stage a task", "prepare a task for execution", "write a PROMPT.md", "set up work for the agent", "queue a task", or whenever the user wants to define work that will be executed autonomously by another agent instance.
+version: 1.2.0
+description: Creates structured Taskplane task packets (PROMPT.md, STATUS.md) for autonomous agent execution via the task-orchestrator extension (/orch). Use when asked to "create a task", "create a taskplane task", "stage a task", "prepare a task for execution", "write a PROMPT.md", "set up work for the agent", "queue a task", or whenever the user wants to define work that will be executed autonomously by another agent instance.
 ---
 
 # Create Taskplane Task
 
 Creates structured task packets (PROMPT.md + STATUS.md) for autonomous execution
-via the **task-runner extension** and parallel batch execution via the
-**task-orchestrator extension**. The extensions handle the execution loop,
-fresh-context management, cross-model reviews, wave scheduling, and live
-dashboard — so PROMPT.md stays focused on WHAT to do, not HOW to execute.
+via the **task-orchestrator extension** (`/orch`). The orchestrator handles the
+execution loop, fresh-context management, cross-model reviews, wave scheduling,
+and live dashboard — so PROMPT.md stays focused on WHAT to do, not HOW to execute.
 
 ## Architecture
 
 ```
 create-taskplane-task skill       → Creates PROMPT.md + STATUS.md
-task-runner extension            → Executes the task autonomously
+task-orchestrator extension      → Executes tasks (single or batch)
   ├─ task-worker.md agent        → Worker system prompt (checkpoint discipline, resume logic)
   ├─ task-reviewer.md agent      → Reviewer system prompt (review formats, criteria)
-  └─ task-runner.yaml config     → Project-specific settings, paths, standards
+  └─ taskplane-config.json       → Project-specific settings, paths, standards
 ```
 
-The skill only creates files. All execution behavior lives in the extension and agents.
+The skill only creates files. All execution behavior lives in the orchestrator
+and the current execution engine (orchestrator + agent-host, direct process
+hosting, no TMUX).
 
 ## Prerequisites
 
-**If `.pi/task-runner.yaml` does not exist**, the project has not been initialized.
-Tell the user to run `taskplane init` first — the skill cannot create tasks
-without knowing where task areas live.
+**If `.pi/taskplane-config.json` does not exist** (and `.pi/task-runner.yaml`
+is also absent), the project has not been initialized. Tell the user to run
+`taskplane init` first — the skill cannot create tasks without knowing where
+task areas live.
 
 ## Configuration
 
-**Read `.pi/task-runner.yaml` before creating any task.** It contains:
-- `task_areas` — folder paths, prefixes, CONTEXT.md locations per area
-- `reference_docs` — available Tier 3 docs for "Context to Read First"
-- `standards` — project coding rules and standards docs
-- `testing.commands` — how to run tests
-- `self_doc_targets` — where agents log discoveries
-- `protected_docs` — docs requiring user approval to modify
-- `never_load` — docs to exclude from task execution context
+**Read `.pi/taskplane-config.json` first** (JSON, canonical). Fall back to
+`.pi/task-runner.yaml` only if the JSON config does not exist. Use canonical
+JSON keys when documenting behavior; YAML keys are compatibility aliases.
+
+Primary keys to read:
+- `taskRunner.taskAreas` (legacy alias: `task_areas`) — folder paths, prefixes, CONTEXT.md locations per area
+- `taskRunner.referenceDocs` (legacy alias: `reference_docs`) — available Tier 3 docs for "Context to Read First"
+- `taskRunner.standards` — project coding rules and standards docs
+- `taskRunner.testing.commands` — how to run tests
+- `taskRunner.selfDocTargets` (legacy alias: `self_doc_targets`) — where agents log discoveries
+- `taskRunner.protectedDocs` (legacy alias: `protected_docs`) — docs requiring user approval to modify
+- `taskRunner.neverLoad` (legacy alias: `never_load`) — docs to exclude from task execution context
 
 ---
 
@@ -53,7 +59,7 @@ The user will rarely specify which area to use — **figure it out from context.
 
 **When there are multiple areas**, match the task to the right area:
 
-1. Read `.pi/task-runner.yaml` → `task_areas` to get all areas
+1. Read the project config (`taskplane-config.json` or `task-runner.yaml`) → `taskRunner.taskAreas` (or `task_areas` in fallback YAML) to get all areas
 2. Read each area's `CONTEXT.md` — the "Current State" section describes what
    that area owns (its domain, services, file scope)
 3. Match the task description to the area whose scope best fits:
@@ -71,7 +77,7 @@ The user will rarely specify which area to use — **figure it out from context.
 
 **Note:** Task area structures evolve over time. A new project starts with a
 single `taskplane-tasks/` folder and one area. As the project grows, users add
-domains and platform areas in `task-runner.yaml`. The skill adapts — it always
+domains and platform areas in the config. The skill adapts — it always
 reads the config to discover what areas exist rather than assuming a layout.
 
 ### Step 2: Assess Complexity & Size
@@ -91,19 +97,20 @@ Use the template in [references/prompt-template.md](references/prompt-template.m
 ### Step 5: Create STATUS.md
 
 Use the STATUS.md template in [references/prompt-template.md](references/prompt-template.md).
-(If omitted, the task-runner extension auto-generates it from PROMPT.md.)
+(If omitted, the execution engine can auto-generate it from PROMPT.md.)
 
 ### Step 6: Update Tracking
 
 - **CONTEXT.md** — Increment `Next Task ID` (done in Step 1)
-- **PROGRESS.md** — Add row to "Active Tasks" table
 
 ### Step 7: Report Launch Command
 
 ```
-/task {area.path}/{PREFIX-###-slug}/PROMPT.md
+/orch {area.path}/{PREFIX-###-slug}/PROMPT.md
 ```
 
+For batch execution of multiple tasks: `/orch all`
+
 ---
 
 ## Complexity Assessment
@@ -165,9 +172,11 @@ PROMPT.md tells the worker what to load. Less is better.
 | **3** | Specific reference docs | Only the docs this task needs |
 
 Populate "Context to Read First" in PROMPT.md using docs from
-`task-runner.yaml → reference_docs`. List only what the task actually needs.
+the project config → `taskRunner.referenceDocs` (legacy YAML: `reference_docs`).
+List only what the task actually needs.
 
-Docs in `task-runner.yaml → never_load` must NOT appear in any task.
+Docs listed in config → `taskRunner.neverLoad` (legacy YAML: `never_load`)
+must NOT appear in any task.
 
 ---
 
@@ -252,8 +261,8 @@ resumability checkpoint, not a line-by-line implementation journal.
 ### Constraint: No New Steps at Runtime
 
 **Workers MUST NOT add, remove, or renumber steps during execution.** The
-task-runner extension parses the step list from PROMPT.md once at `/task` launch
-and iterates that fixed list. Steps added to STATUS.md at runtime will appear in
+execution engine parses the step list from PROMPT.md once at launch and
+iterates that fixed list. Steps added to STATUS.md at runtime will appear in
 the dashboard but **silently never execute**.
 
 Hydration expands checkboxes *within* existing steps only. If a worker discovers
@@ -302,7 +311,7 @@ Notes:
 Verify every task against this before reporting the launch command:
 
 - [ ] `Next Task ID` read from CONTEXT.md and incremented
-- [ ] Folder created at correct `task_areas` path with name `{PREFIX}-{###}-{slug}`
+- [ ] Folder created at correct `taskRunner.taskAreas` path (or fallback YAML `task_areas`) with name `{PREFIX}-{###}-{slug}`
 - [ ] Complexity assessed, review level assigned (0-3)
 - [ ] Size assessed (S/M/L) — split if XL
 - [ ] PROMPT.md created from template with all required sections:
@@ -319,8 +328,7 @@ Verify every task against this before reporting the launch command:
 - [ ] STATUS.md created with matching step structure
   - [ ] Checkboxes match PROMPT.md granularity (1:1 where items are known)
   - [ ] `⚠️ Hydrate` markers for discovery-dependent steps
-- [ ] PROGRESS.md updated (add to "Active Tasks")
-- [ ] Launch command reported: `/task {path}/PROMPT.md`
+- [ ] Launch command reported: `/orch {path}/PROMPT.md`
 
 ---
 
@@ -339,7 +347,7 @@ is there).
 ## Orchestrator Awareness
 
 Tasks are often executed in parallel batches by the task-orchestrator extension,
-not just individually via task-runner. Two fields in PROMPT.md become load-bearing
+not just as one-off single-task runs. Two fields in PROMPT.md become load-bearing
 in batch mode:
 
 - **`## Dependencies`** — determines wave ordering. Tasks with unmet deps are

package/skills/create-taskplane-task/references/prompt-template.md

@@ -21,7 +21,7 @@ Copy this template when creating a new task. Replace all `[bracketed]` fields.
 [FULL_PATH_TO_TASK_FOLDER]/
 ├── PROMPT.md   ← This file (immutable above --- divider)
 ├── STATUS.md   ← Execution state (worker updates this)
-├── .reviews/   ← Reviewer output (task-runner creates this)
+├── .reviews/   ← Reviewer output (created by the orchestrator runtime)
 └── .DONE       ← Created when complete
 ```
 
@@ -90,7 +90,7 @@ Copy this template when creating a new task. Replace all `[bracketed]` fields.
 > ZERO test failures allowed. This step runs the FULL test suite as a quality gate.
 > (Earlier steps should use targeted tests for fast feedback — see worker prompt.)
 
-- [ ] Run FULL test suite: `[test command from task-runner.yaml]`
+- [ ] Run FULL test suite: `[test command from project config]`
 - [ ] Run integration tests (if applicable)
 - [ ] Fix all failures
 - [ ] Build passes: `[build command]`
@@ -148,7 +148,7 @@ for this task MUST include the task ID for traceability:
 
 # STATUS.md Template
 
-Create alongside PROMPT.md. If omitted, the task-runner extension auto-generates
+Create alongside PROMPT.md. If omitted, the execution engine may auto-generate
 this from PROMPT.md.
 
 ````markdown