claude-dev-env 2.3.0 → 2.5.0

package/skills/task-build/CLAUDE.md

@@ -1,28 +1,29 @@
 # task-build
 
-Gathers every open task in the current session and registers each one on the task list with `TaskCreate`.
+Gathers every open task in the current session and registers each one with the best available task or plan tool.
 
 **Trigger:** `/task-build`, "build my task list", "capture these tasks", "add open tasks to the task list", "track these".
 
 ## Purpose
 
-Collects outstanding work from the conversation, `$ARGUMENTS`, and any plan documents or `TodoWrite` items raised this session, then creates one task per open item — skipping anything already tracked or already complete.
+Collects outstanding work from the conversation, `$ARGUMENTS`, and any plan documents or task items raised this session, then registers one item per open task — skipping anything already tracked or already complete.
 
 ## Key files
 
 | File | Purpose |
 |---|---|
-| `SKILL.md` | The complete skill — four steps (read current list, find open tasks, create one task per item, report). No companion files. |
+| `SKILL.md` | Complete task discovery and registration workflow |
+| `reference/tool-routing.md` | Progressive-disclosure routing and fallback rules |
 
 ## How the skill runs
 
-1. Calls `TaskList` to read what is already tracked — prevents duplicates.
+1. Reads the current list or visible plan with the selected host tool — prevents duplicates.
 2. Scans `$ARGUMENTS`, the conversation, and any plan or checklist items for open, actionable work.
-3. Calls `TaskCreate` for each untracked item with a short imperative `subject`, a `description` of what done looks like, and an optional `activeForm` for the spinner.
-4. Reports how many tasks were added and how many were already tracked.
+3. Prefers `update_plan`; otherwise uses `TaskList`/`TaskCreate`, then `TodoWrite` as the fallback. See `reference/tool-routing.md` for field mapping.
+4. Reports the selected tool, how many tasks were added, and how many were already tracked.
 
 ## Conventions
 
 - This skill only records tasks — it does not start, assign, or complete them.
-- Use `TaskUpdate` to set status or owner after the list is built.
+- Use the matching host operation to set status after the list is built.
 - `disable-model-invocation: true` is not set; the skill uses model judgment to classify open vs. complete items.

package/skills/task-build/SKILL.md

@@ -1,16 +1,16 @@
 ---
 name: task-build
-description: "Gather every open task in the current session and register each one on the task list with TaskCreate. Use at the start of work, after a planning discussion, or whenever the user lists several things to do. Triggers: '/task-build', 'build my task list', 'capture these tasks', 'add open tasks to the task list', 'track these'."
+description: "Gather open session tasks and register them with the best available task or plan tool. Triggers: '/task-build', 'build my task list', 'capture these tasks', 'add open tasks to the task list', 'track these', task list, update plan."
 argument-hint: "[optional: a list of tasks to capture, or omit to scan the session]"
 ---
 
 # Task Build
 
-Collect every open task and put it on the session task list. Each open task becomes one `TaskCreate` entry, so all the work is tracked and visible.
+Collect every open task and put it on the session task list or plan using the best available host tool. Read [tool-routing.md](reference/tool-routing.md) only when choosing or adapting the host-tool path.
 
 ## Instructions
 
-1. **Read the current list first.** Call `TaskList` to see what is already tracked. This keeps you from adding the same task twice.
+1. **Read the current list first.** Use the read operation paired with the selected host tool when one exists. If `update_plan` is the selected tool, inspect the current visible plan when available because `update_plan` replaces the full plan.
 
 2. **Find every open task.** Gather all outstanding work from these sources:
    - `$ARGUMENTS`, when the user passed a list.
@@ -19,13 +19,21 @@ Collect every open task and put it on the session task list. Each open task beco
 
    An open task is any concrete, actionable item that is not finished. Skip anything already complete and anything already on the list.
 
-3. **Create one task per item.** For each open task that is not already tracked, call `TaskCreate` with:
-   - `subject` — a short imperative title (e.g. "Fix login redirect").
-   - `description` — what the task involves and how to tell it is done.
-   - `activeForm` — the present-continuous form for the spinner (e.g. "Fixing login redirect"), when it adds clarity.
+3. **Register one item per task.** Prefer `update_plan` when it is available. Otherwise use the first supported task-list method described in [tool-routing.md](reference/tool-routing.md), preserving the complete existing list when the selected tool replaces it.
 
 4. **Report the result.** State how many tasks you added and how many were already tracked, then list the new subjects.
 
 ## Scope
 
-This skill only records tasks. It does not start, assign, or complete them. Use `TaskUpdate` to set an owner or change status once the list is built.
+This skill only records tasks. It does not start, assign, or complete them. Report the selected tool, how many items were added, and how many were already tracked. Use the matching host operation to change status later.
+
+## File index
+
+| File | Purpose |
+|---|---|
+| `SKILL.md` | Task discovery and registration hub |
+| `reference/tool-routing.md` | On-demand host-tool selection and field mapping |
+
+## Folder map
+
+- `reference/` — host-tool routing details loaded only when needed

package/skills/task-build/reference/tool-routing.md

@@ -0,0 +1,19 @@
+# Task Tool Routing
+
+Use the first available path in this order:
+
+1. **`update_plan`** — preferred when exposed. Call it once with the complete plan. Map each task to `{step, status}`. Use `pending`, `in_progress`, or `completed`.
+2. **`TaskList` + `TaskCreate`** — use the existing task-list workflow when `update_plan` is unavailable. Create one task per new item with `subject`, `description`, and optional `activeForm`.
+3. **`TodoWrite`** — use when neither `update_plan` nor `TaskCreate` is exposed. Preserve the host's required schema and register the complete current task set.
+
+Do not invent a tool name. Tool availability means the callable tool is exposed in the current session, not merely mentioned in documentation or in another host's skill.
+
+## Status and replacement rules
+
+- When a tool replaces the complete list, include existing unfinished items in the replacement payload.
+- When a tool supports incremental creation, skip duplicates and completed items.
+- If no task or plan tool is exposed, report that fact and keep the work unregistered; do not use a markdown checklist as a substitute.
+
+## Reporting
+
+State the selected tool, the number of new items, the number already tracked, and the new task subjects. If the fallback path was used, name the unavailable preferred tools briefly.

package/skills/team-advisor/SKILL.md

@@ -17,8 +17,8 @@ One warm, addressable advisor available at the strongest model tier the session
 
 **Detect the host profile first** (Host profiles in
 [`_shared/advisor/advisor-protocol.md`](../../_shared/advisor/advisor-protocol.md)
-— e.g. `ADVISOR_HOST_PROFILE` or `THIRD_PARTY`). Do not start a model-floor
-walk until the host is known.
+— e.g. %USERPROFILE%\.claude\_shared\advisor\advisor-protocol.md). Do not start a model-floor
+walk until the host is known. 
 
 This session is the shared advisor's sole consumer, so its model floor is
 simply this session's own tier — no routing table to take a max against.