@leeovery/claude-technical-workflows 2.1.30 → 2.1.31

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leeovery/claude-technical-workflows",
-  "version": "2.1.30",
+  "version": "2.1.31",
   "description": "Technical workflow skills & commands for Claude Code",
   "license": "MIT",
   "author": "Lee Overy <me@leeovery.com>",

package/skills/technical-planning/SKILL.md

@@ -62,7 +62,7 @@ Context refresh (compaction) summarizes the conversation, losing procedural deta
 2. **Read all tracking and state files** for the current topic — plan index files, review tracking files, implementation tracking files, or any working documents this skill creates. These are your source of truth for progress.
 3. **Check git state.** Run `git status` and `git log --oneline -10` to see recent commits. Commit messages follow a conventional pattern that reveals what was completed.
 4. **Announce your position** to the user before continuing: what step you believe you're at, what's been completed, and what comes next. Wait for confirmation.
-5. **Check `author_gate_mode` and `finding_gate_mode`** in the Plan Index File frontmatter — if `auto`, the user previously opted in during this session. Preserve these values.
+5. **Check `task_list_gate_mode`, `author_gate_mode`, and `finding_gate_mode`** in the Plan Index File frontmatter — if `auto`, the user previously opted in during this session. Preserve these values.
 
 Do not guess at progress or continue from memory. The files on disk and git history are authoritative — your recollection is not.
 
@@ -118,7 +118,7 @@ Found existing plan for **{topic}** (previously reached phase {N}, task {M}).
 
 If the specification changed, update `spec_commit` in the Plan Index File frontmatter to the current commit hash.
 
-Reset `author_gate_mode` and `finding_gate_mode` to `gated` in the Plan Index File frontmatter (fresh invocation = fresh gates).
+Reset `task_list_gate_mode`, `author_gate_mode`, and `finding_gate_mode` to `gated` in the Plan Index File frontmatter (fresh invocation = fresh gates).
 
 → Proceed to **Step 1**.
 

package/skills/technical-planning/references/author-tasks.md

@@ -55,7 +55,7 @@ Task {M} of {total}: {Task Name} — authored. Logging to plan.
 · · · · · · · · · · · ·
 **To proceed:**
 - **`y`/`yes`** — Approved. I'll log it to the plan.
-- **`a`/`auto`** — Approve this and all remaining tasks automatically
+- **`a`/`auto`** — Approve this and all remaining task authoring gates automatically
 - **Or tell me what to change.**
 - **Or navigate** — a different phase or task, or the leading edge.
 · · · · · · · · · · · ·

package/skills/technical-planning/references/define-tasks.md

@@ -43,7 +43,31 @@ planning:
 
 Commit: `planning({topic}): draft Phase {N} task list`
 
-Present the task overview to the user as rendered markdown (not in a code block). Then, separately, present the choices:
+Present the task overview to the user:
+
+> *Output the next fenced block as markdown (not a code block):*
+
+```
+{task overview from planning-task-designer agent}
+```
+
+Then check the gate mode.
+
+### Check Gate Mode
+
+Check `task_list_gate_mode` in the Plan Index File frontmatter.
+
+#### If `task_list_gate_mode: auto`
+
+> *Output the next fenced block as a code block:*
+
+```
+Phase {N}: {Phase Name} — task list approved. Proceeding to authoring.
+```
+
+→ Skip to **If approved** below.
+
+#### If `task_list_gate_mode: gated`
 
 **STOP.** Ask:
 
@@ -53,6 +77,7 @@ Present the task overview to the user as rendered markdown (not in a code block)
 · · · · · · · · · · · ·
 **To proceed:**
 - **`y`/`yes`** — Approved.
+- **`a`/`auto`** — Approve this and all remaining task list gates automatically
 - **Or tell me what to change** — reorder, split, merge, add, edit, or remove tasks.
 - **Or navigate** — a different phase or task, or the leading edge.
 · · · · · · · · · · · ·
@@ -66,12 +91,19 @@ Re-invoke `planning-task-designer` with all original inputs PLUS:
 
 Update the Plan Index File with the revised task table, re-present, and ask again. Repeat until approved.
 
-#### If approved
+#### If `auto`
+
+Note that `task_list_gate_mode` should be updated to `auto` during the commit step below.
+
+→ Proceed to **If approved** below.
+
+#### If approved (`y`/`yes` or `auto`)
 
 **If the task list is new or was amended:**
 
 1. Advance the `planning:` block to the first task in this phase
-2. Commit: `planning({topic}): approve Phase {N} task list`
+2. If user chose `auto` at this gate: update `task_list_gate_mode: auto` in the Plan Index File frontmatter
+3. Commit: `planning({topic}): approve Phase {N} task list`
 
 **If the task list was already approved and unchanged:** No updates needed.
 

package/skills/technical-planning/references/plan-construction.md

@@ -79,6 +79,20 @@ After Step A returns with an approved task table, continue to **Author Tasks for
 {task list from the phase's task table}
 ```
 
+Check `task_list_gate_mode` in the Plan Index File frontmatter.
+
+#### If `task_list_gate_mode: auto` (existing task table)
+
+> *Output the next fenced block as a code block:*
+
+```
+Phase {N}: {Phase Name} — task list confirmed. Proceeding to authoring.
+```
+
+→ Continue to **Author Tasks for the Phase** below.
+
+#### If `task_list_gate_mode: gated` (existing task table)
+
 > *Output the next fenced block as markdown (not a code block):*
 
 ```

package/skills/technical-planning/references/plan-index-schema.md

@@ -23,6 +23,7 @@ spec_commit: {commit-hash}
 created: YYYY-MM-DD
 updated: YYYY-MM-DD
 external_dependencies: []
+task_list_gate_mode: gated
 author_gate_mode: gated
 finding_gate_mode: gated
 planning:
@@ -43,6 +44,7 @@ planning:
 | `created` | Plan creation — today's date |
 | `updated` | Plan creation — today's date; update on each commit |
 | `external_dependencies` | Dependency resolution (Step 6) |
+| `task_list_gate_mode` | Plan creation → `gated`; user opts in → `auto` |
 | `author_gate_mode` | Plan creation → `gated`; user opts in → `auto` |
 | `finding_gate_mode` | Plan creation → `gated`; user opts in → `auto` |
 | `planning.phase` | Tracks current phase position |