@leeovery/claude-technical-workflows 2.1.40 → 2.1.41

package/skills/start-specification/references/confirm-continue.md

@@ -11,7 +11,7 @@
 ```
 Continuing specification: {Title Case Name}
 
-Existing: docs/workflow/specification/{kebab-case-name}/specification.md (in-progress)
+Existing: .workflows/specification/{kebab-case-name}/specification.md (in-progress)
 
 Sources to extract:
   • {discussion-name} (pending)
@@ -37,7 +37,7 @@ Proceed?
 ```
 Continuing specification: {Title Case Name}
 
-Existing: docs/workflow/specification/{kebab-case-name}/specification.md (in-progress)
+Existing: .workflows/specification/{kebab-case-name}/specification.md (in-progress)
 
 All sources extracted:
   • {discussion-name}
@@ -61,7 +61,7 @@ Proceed?
 ```
 Continuing specification: {Title Case Name}
 
-Existing: docs/workflow/specification/{kebab-case-name}/specification.md (concluded)
+Existing: .workflows/specification/{kebab-case-name}/specification.md (concluded)
 
 New sources to extract:
   • {discussion-name} (pending)

package/skills/start-specification/references/confirm-create.md

@@ -15,7 +15,7 @@ Sources:
   • {discussion-name}
   • {discussion-name}
 
-Output: docs/workflow/specification/{kebab-case-name}/specification.md
+Output: .workflows/specification/{kebab-case-name}/specification.md
 ```
 
 > *Output the next fenced block as markdown (not a code block):*
@@ -41,7 +41,7 @@ Sources:
   • {discussion-name} (has individual spec — will be incorporated)
   • {discussion-name}
 
-Output: docs/workflow/specification/{kebab-case-name}/specification.md
+Output: .workflows/specification/{kebab-case-name}/specification.md
 
 After completion:
   specification/{discussion-name}/specification.md → marked as superseded

package/skills/start-specification/references/confirm-refine.md

@@ -9,7 +9,7 @@
 ```
 Refining specification: {Title Case Name}
 
-Existing: docs/workflow/specification/{kebab-case-name}/specification.md (concluded)
+Existing: .workflows/specification/{kebab-case-name}/specification.md (concluded)
 
 All sources extracted:
   • {discussion-name}

package/skills/start-specification/references/confirm-unify.md

@@ -20,7 +20,7 @@ Existing specifications to incorporate:
   • {spec-name}/specification.md → will be superseded
   • {spec-name}/specification.md → will be superseded
 
-Output: docs/workflow/specification/unified/specification.md
+Output: .workflows/specification/unified/specification.md
 ```
 
 > *Output the next fenced block as markdown (not a code block):*
@@ -45,7 +45,7 @@ Sources:
   • {discussion-name}
   ...
 
-Output: docs/workflow/specification/unified/specification.md
+Output: .workflows/specification/unified/specification.md
 ```
 
 > *Output the next fenced block as markdown (not a code block):*

package/skills/start-specification/references/display-analyze.md

@@ -87,7 +87,7 @@ Proceed with analysis?
 
 If cache is stale, delete it first:
 ```bash
-rm docs/workflow/.state/discussion-consolidation-analysis.md
+rm .workflows/.state/discussion-consolidation-analysis.md
 ```
 
 → Load **[analysis-flow.md](analysis-flow.md)** and follow its instructions.

package/skills/start-specification/references/display-groupings.md

@@ -8,7 +8,7 @@ Shows when cache is valid (directly from routing) or after analysis completes. T
 
 ## A. Load Groupings
 
-Load groupings from `docs/workflow/.state/discussion-consolidation-analysis.md`. Parse the `### {Name}` headings and their discussion lists.
+Load groupings from `.workflows/.state/discussion-consolidation-analysis.md`. Parse the `### {Name}` headings and their discussion lists.
 
 → Proceed to **B. Determine Discussion Status**.
 
@@ -160,7 +160,7 @@ Every meta option (Unify, Re-analyze) MUST include its description lines.
 
 #### If user picks "Unify all"
 
-Update the cache: rewrite `docs/workflow/.state/discussion-consolidation-analysis.md` with a single "Unified" grouping containing all concluded discussions. Keep the same checksum, update the generated timestamp. Add note: `Custom groupings confirmed by user (unified).`
+Update the cache: rewrite `.workflows/.state/discussion-consolidation-analysis.md` with a single "Unified" grouping containing all concluded discussions. Keep the same checksum, update the generated timestamp. Add note: `Custom groupings confirmed by user (unified).`
 
 Spec name: "Unified". Sources: all concluded discussions.
 
@@ -170,7 +170,7 @@ Spec name: "Unified". Sources: all concluded discussions.
 
 Delete the cache:
 ```bash
-rm docs/workflow/.state/discussion-consolidation-analysis.md
+rm .workflows/.state/discussion-consolidation-analysis.md
 ```
 
 → Load **[analysis-flow.md](analysis-flow.md)** and follow its instructions.

package/skills/start-specification/references/display-specs-menu.md

@@ -139,7 +139,7 @@ Menu descriptions are wrapped in backticks to visually distinguish them from the
 
 If cache is stale, delete it first:
 ```bash
-rm docs/workflow/.state/discussion-consolidation-analysis.md
+rm .workflows/.state/discussion-consolidation-analysis.md
 ```
 
 → Load **[analysis-flow.md](analysis-flow.md)** and follow its instructions.

package/skills/start-specification/references/handoffs/continue-concluded.md

@@ -18,7 +18,7 @@ Saving session state so Claude can pick up where it left off if the conversation
 .claude/hooks/workflows/write-session-state.sh \
   "{topic}" \
   "skills/technical-specification/SKILL.md" \
-  "docs/workflow/specification/{topic}/specification.md"
+  ".workflows/specification/{topic}/specification.md"
 ```
 
 This skill's purpose is now fulfilled. Invoke the [technical-specification](../../../technical-specification/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded — it contains the instructions for how to proceed.
@@ -26,13 +26,13 @@ This skill's purpose is now fulfilled. Invoke the [technical-specification](../.
 ```
 Specification session for: {Title Case Name}
 
-Continuing existing: docs/workflow/specification/{kebab-case-name}/specification.md (concluded)
+Continuing existing: .workflows/specification/{kebab-case-name}/specification.md (concluded)
 
 New sources to extract:
-- docs/workflow/discussion/{new-discussion-name}.md
+- .workflows/discussion/{new-discussion-name}.md
 
 Previously extracted (for reference):
-- docs/workflow/discussion/{existing-discussion-name}.md
+- .workflows/discussion/{existing-discussion-name}.md
 
 Context: This specification was previously concluded. New source discussions have been identified. Extract and incorporate their content while maintaining consistency with the existing specification.
 

package/skills/start-specification/references/handoffs/continue.md

@@ -18,7 +18,7 @@ Saving session state so Claude can pick up where it left off if the conversation
 .claude/hooks/workflows/write-session-state.sh \
   "{topic}" \
   "skills/technical-specification/SKILL.md" \
-  "docs/workflow/specification/{topic}/specification.md"
+  ".workflows/specification/{topic}/specification.md"
 ```
 
 This skill's purpose is now fulfilled. Invoke the [technical-specification](../../../technical-specification/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded — it contains the instructions for how to proceed.
@@ -26,11 +26,11 @@ This skill's purpose is now fulfilled. Invoke the [technical-specification](../.
 ```
 Specification session for: {Title Case Name}
 
-Continuing existing: docs/workflow/specification/{kebab-case-name}/specification.md
+Continuing existing: .workflows/specification/{kebab-case-name}/specification.md
 
 Sources for reference:
-- docs/workflow/discussion/{discussion-name}.md
-- docs/workflow/discussion/{discussion-name}.md
+- .workflows/discussion/{discussion-name}.md
+- .workflows/discussion/{discussion-name}.md
 
 Context: This specification already exists. Review and refine it based on the source discussions.
 

package/skills/start-specification/references/handoffs/create-with-incorporation.md

@@ -16,7 +16,7 @@ Saving session state so Claude can pick up where it left off if the conversation
 .claude/hooks/workflows/write-session-state.sh \
   "{topic}" \
   "skills/technical-specification/SKILL.md" \
-  "docs/workflow/specification/{topic}/specification.md"
+  ".workflows/specification/{topic}/specification.md"
 ```
 
 This skill's purpose is now fulfilled. Invoke the [technical-specification](../../../technical-specification/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded — it contains the instructions for how to proceed.
@@ -25,13 +25,13 @@ This skill's purpose is now fulfilled. Invoke the [technical-specification](../.
 Specification session for: {Title Case Name}
 
 Source discussions:
-- docs/workflow/discussion/{discussion-name}.md
-- docs/workflow/discussion/{discussion-name}.md
+- .workflows/discussion/{discussion-name}.md
+- .workflows/discussion/{discussion-name}.md
 
 Existing specifications to incorporate:
-- docs/workflow/specification/{spec-name}/specification.md (covers: {discussion-name} discussion)
+- .workflows/specification/{spec-name}/specification.md (covers: {discussion-name} discussion)
 
-Output: docs/workflow/specification/{kebab-case-name}/specification.md
+Output: .workflows/specification/{kebab-case-name}/specification.md
 
 Context: This consolidates multiple sources. The existing {spec-name}.md specification should be incorporated - extract and adapt its content alongside the discussion material. The result should be a unified specification, not a simple merge.
 

package/skills/start-specification/references/handoffs/create.md

@@ -16,7 +16,7 @@ Saving session state so Claude can pick up where it left off if the conversation
 .claude/hooks/workflows/write-session-state.sh \
   "{topic}" \
   "skills/technical-specification/SKILL.md" \
-  "docs/workflow/specification/{topic}/specification.md"
+  ".workflows/specification/{topic}/specification.md"
 ```
 
 This skill's purpose is now fulfilled. Invoke the [technical-specification](../../../technical-specification/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded — it contains the instructions for how to proceed.
@@ -25,10 +25,10 @@ This skill's purpose is now fulfilled. Invoke the [technical-specification](../.
 Specification session for: {Title Case Name}
 
 Sources:
-- docs/workflow/discussion/{discussion-name}.md
-- docs/workflow/discussion/{discussion-name}.md
+- .workflows/discussion/{discussion-name}.md
+- .workflows/discussion/{discussion-name}.md
 
-Output: docs/workflow/specification/{kebab-case-name}/specification.md
+Output: .workflows/specification/{kebab-case-name}/specification.md
 
 ---
 Invoke the technical-specification skill.

package/skills/start-specification/references/handoffs/unify-with-incorporation.md

@@ -16,7 +16,7 @@ Saving session state so Claude can pick up where it left off if the conversation
 .claude/hooks/workflows/write-session-state.sh \
   "unified" \
   "skills/technical-specification/SKILL.md" \
-  "docs/workflow/specification/unified/specification.md"
+  ".workflows/specification/unified/specification.md"
 ```
 
 This skill's purpose is now fulfilled. Invoke the [technical-specification](../../../technical-specification/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded — it contains the instructions for how to proceed.
@@ -25,15 +25,15 @@ This skill's purpose is now fulfilled. Invoke the [technical-specification](../.
 Specification session for: Unified
 
 Source discussions:
-- docs/workflow/discussion/{discussion-name}.md
-- docs/workflow/discussion/{discussion-name}.md
+- .workflows/discussion/{discussion-name}.md
+- .workflows/discussion/{discussion-name}.md
 ...
 
 Existing specifications to incorporate:
-- docs/workflow/specification/{spec-name}/specification.md
-- docs/workflow/specification/{spec-name}/specification.md
+- .workflows/specification/{spec-name}/specification.md
+- .workflows/specification/{spec-name}/specification.md
 
-Output: docs/workflow/specification/unified/specification.md
+Output: .workflows/specification/unified/specification.md
 
 Context: This consolidates all discussions into a single unified specification. The existing specifications should be incorporated - extract and adapt their content alongside the discussion material.
 

package/skills/start-specification/references/handoffs/unify.md

@@ -16,7 +16,7 @@ Saving session state so Claude can pick up where it left off if the conversation
 .claude/hooks/workflows/write-session-state.sh \
   "unified" \
   "skills/technical-specification/SKILL.md" \
-  "docs/workflow/specification/unified/specification.md"
+  ".workflows/specification/unified/specification.md"
 ```
 
 This skill's purpose is now fulfilled. Invoke the [technical-specification](../../../technical-specification/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded — it contains the instructions for how to proceed.
@@ -25,11 +25,11 @@ This skill's purpose is now fulfilled. Invoke the [technical-specification](../.
 Specification session for: Unified
 
 Sources:
-- docs/workflow/discussion/{discussion-name}.md
-- docs/workflow/discussion/{discussion-name}.md
+- .workflows/discussion/{discussion-name}.md
+- .workflows/discussion/{discussion-name}.md
 ...
 
-Output: docs/workflow/specification/unified/specification.md
+Output: .workflows/specification/unified/specification.md
 
 ---
 Invoke the technical-specification skill.

package/skills/start-specification/scripts/discovery.sh

@@ -8,9 +8,9 @@
 
 set -eo pipefail
 
-DISCUSSION_DIR="docs/workflow/discussion"
-SPEC_DIR="docs/workflow/specification"
-CACHE_FILE="docs/workflow/.state/discussion-consolidation-analysis.md"
+DISCUSSION_DIR=".workflows/discussion"
+SPEC_DIR=".workflows/specification"
+CACHE_FILE=".workflows/.state/discussion-consolidation-analysis.md"
 
 # Helper: Extract a frontmatter field value from a file
 # Usage: extract_field <file> <field_name>

package/skills/status/SKILL.md

@@ -72,7 +72,7 @@ Only show lines for phases that have content. If a phase has zero items but a la
 ```
 Workflow Status
 
-No workflow files found in docs/workflow/
+No workflow files found in .workflows/
 
 Start with /start-research to explore ideas,
 or /start-discussion if you already know what to build.

package/skills/status/scripts/discovery.sh

@@ -8,11 +8,11 @@
 
 set -eo pipefail
 
-RESEARCH_DIR="docs/workflow/research"
-DISCUSSION_DIR="docs/workflow/discussion"
-SPEC_DIR="docs/workflow/specification"
-PLAN_DIR="docs/workflow/planning"
-IMPL_DIR="docs/workflow/implementation"
+RESEARCH_DIR=".workflows/research"
+DISCUSSION_DIR=".workflows/discussion"
+SPEC_DIR=".workflows/specification"
+PLAN_DIR=".workflows/planning"
+IMPL_DIR=".workflows/implementation"
 
 # Helper: Extract a frontmatter field value from a file
 # Usage: extract_field <file> <field_name>

package/skills/technical-discussion/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: technical-discussion
-description: "Document technical discussions as expert architect and meeting assistant. Capture context, decisions, edge cases, debates, and rationale without jumping to specification or implementation. Use when: (1) Users discuss/explore/debate architecture or design, (2) Working through edge cases before specification, (3) Need to document technical decisions and their rationale, (4) Capturing competing solutions and why choices were made. Creates documentation in docs/workflow/discussion/{topic}.md that can be used to build validated specifications."
+description: "Document technical discussions as expert architect and meeting assistant. Capture context, decisions, edge cases, debates, and rationale without jumping to specification or implementation. Use when: (1) Users discuss/explore/debate architecture or design, (2) Working through edge cases before specification, (3) Need to document technical decisions and their rationale, (4) Capturing competing solutions and why choices were made. Creates documentation in .workflows/discussion/{topic}.md that can be used to build validated specifications."
 user-invocable: false
 ---
 
@@ -76,7 +76,7 @@ See **[meeting-assistant.md](references/meeting-assistant.md)** for detailed app
 
 ## Structure
 
-**Output**: `docs/workflow/discussion/{topic}.md`
+**Output**: `.workflows/discussion/{topic}.md`
 
 Use **[template.md](references/template.md)** for structure:
 
@@ -135,7 +135,7 @@ Incorporate the user's context into the discussion, commit, then re-present the
 
 1. Update frontmatter `status: concluded`
 2. Final commit
-3. Check for remaining in-progress discussions in `docs/workflow/discussion/`
+3. Check for remaining in-progress discussions in `.workflows/discussion/`
 
 **If other in-progress discussions exist:**
 

package/skills/technical-discussion/references/template.md

@@ -4,7 +4,7 @@
 
 ---
 
-Standard structure for `docs/workflow/discussion/{topic}.md`. DOCUMENT only - no plans or code.
+Standard structure for `.workflows/discussion/{topic}.md`. DOCUMENT only - no plans or code.
 
 This is a single file per topic.
 
@@ -98,7 +98,7 @@ What we chose, why, the deciding factor, trade-offs accepted, confidence level.
 ## Usage Notes
 
 **When creating**:
-1. Ensure discussion directory exists: `docs/workflow/discussion/`
+1. Ensure discussion directory exists: `.workflows/discussion/`
 2. Create file: `{topic}.md`
 3. Fill frontmatter: topic, status, date
 4. Start with context: why discussing?

package/skills/technical-implementation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: technical-implementation
-description: "Orchestrate implementation of plans using agent-based TDD workflow with per-task review and approval gate (auto mode available). Use when: (1) Implementing a plan from docs/workflow/planning/{topic}/plan.md, (2) User says 'implement', 'build', or 'code this' with a plan available, (3) Ad hoc coding that should follow TDD and quality standards, (4) Bug fixes or features benefiting from structured implementation. Dispatches executor and reviewer agents per task, commits after review approval."
+description: "Orchestrate implementation of plans using agent-based TDD workflow with per-task review and approval gate (auto mode available). Use when: (1) Implementing a plan from .workflows/planning/{topic}/plan.md, (2) User says 'implement', 'build', or 'code this' with a plan available, (3) Ad hoc coding that should follow TDD and quality standards, (4) Bug fixes or features benefiting from structured implementation. Dispatches executor and reviewer agents per task, commits after review approval."
 user-invocable: false
 ---
 
@@ -36,7 +36,7 @@ Either way: dispatch agents per task — executor implements via TDD, reviewer v
 
 ```
 I need an implementation plan to execute. Could you point me to the plan file
-(e.g., docs/workflow/planning/{topic}/plan.md)?
+(e.g., .workflows/planning/{topic}/plan.md)?
 ```
 
 **STOP.** Wait for user response.
@@ -73,7 +73,7 @@ Context refresh (compaction) summarizes the conversation, losing procedural deta
 
 1. **Re-read this skill file completely.** Do not rely on your summary of it. The full process, steps, and rules must be reloaded.
 2. **Check task progress in the plan** — use the plan adapter's instructions to read the plan's current state. Also read the implementation tracking file and any other working documents for additional context.
-3. **Check `task_gate_mode`, `fix_gate_mode`, `fix_attempts`, and `analysis_cycle`** in the tracking file — if gates are `auto`, the user previously opted out. If `fix_attempts` > 0, you're mid-fix-loop for the current task. If `analysis_cycle` > 0, you've completed analysis cycles — check for findings files on disk (`analysis-*-c{cycle-number}.md` in `{topic}/`) to determine mid-analysis state.
+3. **Check `task_gate_mode`, `fix_gate_mode`, `analysis_gate_mode`, `fix_attempts`, and `analysis_cycle`** in the tracking file — if gates are `auto`, the user previously opted out. If `fix_attempts` > 0, you're mid-fix-loop for the current task. If `analysis_cycle` > 0, you've completed analysis cycles — check for findings files on disk (`analysis-*-c{cycle-number}.md` in `{topic}/`) to determine mid-analysis state.
 4. **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.
 5. **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.
 
@@ -101,7 +101,7 @@ Complete ALL setup steps before proceeding.
 
 Load **[environment-setup.md](references/environment-setup.md)** and follow its instructions.
 
-#### If `docs/workflow/environment-setup.md` states "No special setup required"
+#### If `.workflows/environment-setup.md` states "No special setup required"
 
 → Proceed to **Step 2**.
 
@@ -122,7 +122,7 @@ I should follow before implementing?
 
 **STOP.** Wait for user response.
 
-Save their instructions to `docs/workflow/environment-setup.md` (or "No special setup required." if none needed). Commit.
+Save their instructions to `.workflows/environment-setup.md` (or "No special setup required." if none needed). Commit.
 
 → Proceed to **Step 2**.
 
@@ -130,7 +130,7 @@ Save their instructions to `docs/workflow/environment-setup.md` (or "No special
 
 ## Step 2: Read Plan + Load Plan Adapter
 
-1. Read the plan from the provided location (typically `docs/workflow/planning/{topic}/plan.md`)
+1. Read the plan from the provided location (typically `.workflows/planning/{topic}/plan.md`)
 2. Plans can be stored in various formats. The `format` field in the plan's frontmatter identifies which format this plan uses.
 3. Load the format's per-concern adapter files from `../technical-planning/references/output-formats/{format}/`:
    - **reading.md** — how to read tasks from the plan
@@ -145,15 +145,15 @@ Save their instructions to `docs/workflow/environment-setup.md` (or "No special
 
 ## Step 3: Initialize Implementation Tracking
 
-#### If `docs/workflow/implementation/{topic}/tracking.md` already exists
+#### If `.workflows/implementation/{topic}/tracking.md` already exists
 
-Reset `task_gate_mode` and `fix_gate_mode` to `gated`, `fix_attempts` to `0`, and `analysis_cycle` to `0` (fresh session = fresh gates/cycles).
+Reset `task_gate_mode`, `fix_gate_mode`, and `analysis_gate_mode` to `gated`, `fix_attempts` to `0`, and `analysis_cycle` to `0` (fresh session = fresh gates/cycles).
 
 → Proceed to **Step 4**.
 
 #### If no tracking file exists
 
-Create `docs/workflow/implementation/{topic}/tracking.md`:
+Create `.workflows/implementation/{topic}/tracking.md`:
 
 ```yaml
 ---
@@ -163,6 +163,7 @@ format: {format from plan}
 status: in-progress
 task_gate_mode: gated
 fix_gate_mode: gated
+analysis_gate_mode: gated
 fix_attempts: 0
 linters: []
 analysis_cycle: 0
@@ -325,7 +326,7 @@ Discuss the user's context. If additional work is needed, route back to **Step 6
 
 #### If yes
 
-Update the tracking file (`docs/workflow/implementation/{topic}/tracking.md`):
+Update the tracking file (`.workflows/implementation/{topic}/tracking.md`):
 - Set `status: completed`
 - Set `completed: YYYY-MM-DD` (use today's actual date)
 - Update `updated` date

package/skills/technical-implementation/references/analysis-loop.md

@@ -121,18 +121,26 @@ impl({topic}): analysis cycle {N} — synthesis
 
 ## E. Approval Gate
 
-Read the staging file from `docs/workflow/implementation/{topic}/analysis-tasks-c{cycle-number}.md`.
+Read the staging file from `.workflows/implementation/{topic}/analysis-tasks-c{cycle-number}.md`.
+
+Check `analysis_gate_mode` in the implementation tracking file (`gated` or `auto`).
 
 Present an overview:
 
-**Analysis cycle {N}: {K} proposed tasks**
+> *Output the next fenced block as a code block:*
+
+```
+Analysis cycle {N}: {K} proposed tasks
 
-1. {title} ({severity})
-2. {title} ({severity})
-...
+  1. {title} ({severity})
+  2. {title} ({severity})
+```
 
 Then present each task with `status: pending` individually:
 
+> *Output the next fenced block as markdown (not a code block):*
+
+```
 **Task {current}/{total}: {title}** ({severity})
 Sources: {sources}
 
@@ -148,12 +156,18 @@ Sources: {sources}
 
 **Tests**:
 {tests}
+```
+
+#### If `analysis_gate_mode: gated`
 
 > *Output the next fenced block as markdown (not a code block):*
 
 ```
 · · · · · · · · · · · ·
-- **`a`/`approve`** — Approve this task
+Approve this task?
+
+- **`y`/`yes`** — Approve this task
+- **`a`/`auto`** — Approve this and all remaining tasks automatically
 - **`s`/`skip`** — Skip this task
 - **Comment** — Revise based on feedback
 · · · · · · · · · · · ·
@@ -161,12 +175,34 @@ Sources: {sources}
 
 **STOP.** Wait for user input.
 
-#### If `approve`
+#### If `analysis_gate_mode: auto`
+
+Update `status: approved` in the staging file. Note that `analysis_gate_mode` should be updated to `auto` in the tracking file during the next commit.
+
+> *Output the next fenced block as a code block:*
+
+```
+Task {current} of {total}: {title} — approved (auto).
+```
+
+→ Continue to next task without stopping.
+
+---
+
+Process user input:
+
+#### If `yes`
 
 Update `status: approved` in the staging file.
 
 → Present the next pending task, or proceed to routing below if all tasks processed.
 
+#### If `auto`
+
+Update `status: approved` in the staging file. Note that `analysis_gate_mode` should be updated to `auto` in the tracking file during the next commit.
+
+→ Continue processing remaining tasks without stopping.
+
 #### If `skip`
 
 Update `status: skipped` in the staging file.
@@ -185,7 +221,7 @@ After all tasks processed:
 
 → If all tasks were skipped:
 
-Commit the staging file updates:
+Commit the staging file updates (include tracking file if `analysis_gate_mode` was updated):
 
 ```
 impl({topic}): analysis cycle {N} — tasks skipped
@@ -201,7 +237,7 @@ Load **[invoke-task-writer.md](invoke-task-writer.md)** and follow its instructi
 
 **STOP.** Do not proceed until the task writer has returned.
 
-Commit all analysis and plan changes (staging file, plan tasks, Plan Index File):
+Commit all analysis and plan changes (staging file, plan tasks, Plan Index File, and tracking file if `analysis_gate_mode` was updated):
 
 ```
 impl({topic}): add analysis phase {N} ({K} tasks)

package/skills/technical-implementation/references/environment-setup.md

@@ -17,7 +17,7 @@ Before starting implementation, ensure the environment is ready. This step runs
 
 ## Setup Document Location
 
-Look for: `docs/workflow/environment-setup.md`
+Look for: `.workflows/environment-setup.md`
 
 This file contains natural language instructions for setting up the implementation environment. It's project-specific.
 
@@ -42,9 +42,9 @@ Ask the user:
 
 If they provide instructions, offer to save them:
 
-> "Would you like me to save these instructions to `docs/workflow/environment-setup.md` for future sessions?"
+> "Would you like me to save these instructions to `.workflows/environment-setup.md` for future sessions?"
 
-If they say no setup is needed, create `docs/workflow/environment-setup.md` with "No special setup required." and commit. This prevents asking the same question in future sessions.
+If they say no setup is needed, create `.workflows/environment-setup.md` with "No special setup required." and commit. This prevents asking the same question in future sessions.
 
 ## No Setup Required
 

package/skills/technical-implementation/references/invoke-task-writer.md

@@ -15,7 +15,7 @@ This step invokes the task writer agent to create plan tasks from approved analy
 Pass via the orchestrator's prompt:
 
 1. **Topic name** — the implementation topic
-2. **Staging file path** — `docs/workflow/implementation/{topic}/analysis-tasks-c{cycle-number}.md`
+2. **Staging file path** — `.workflows/implementation/{topic}/analysis-tasks-c{cycle-number}.md`
 3. **Plan path** — the implementation plan path
 4. **Plan format reading adapter path** — `../../technical-planning/references/output-formats/{format}/reading.md`
 5. **Plan format authoring adapter path** — `../../technical-planning/references/output-formats/{format}/authoring.md`

package/skills/technical-implementation/references/task-loop.md

@@ -178,7 +178,7 @@ Check the `task_gate_mode` field in the implementation tracking file.
 - If the format's updating.md includes a **Phase / Parent Status** section, follow its phase completion instructions
 - Append the phase number to `completed_phases` in the tracking file
 
-**Mirror to implementation tracking file** (`docs/workflow/implementation/{topic}/tracking.md`):
+**Mirror to implementation tracking file** (`.workflows/implementation/{topic}/tracking.md`):
 - Append the task ID to `completed_tasks`
 - Update `current_phase` if phase changed
 - Update `current_task` to the next task (or `~` if done)