@leeovery/claude-technical-workflows 2.1.31 → 2.1.33

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

@@ -4,6 +4,21 @@
 
 ---
 
+Before invoking the processing skill, save a session bookmark.
+
+> *Output the next fenced block as a code block:*
+
+```
+Saving session state so Claude can pick up where it left off if the conversation is compacted.
+```
+
+```bash
+.claude/hooks/workflows/write-session-state.sh \
+  "unified" \
+  "skills/technical-specification/SKILL.md" \
+  "docs/workflow/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.
 
 ```

package/skills/status/SKILL.md

@@ -3,6 +3,12 @@ name: status
 description: "Show workflow status - what exists, where you are, and what to do next."
 disable-model-invocation: true
 allowed-tools: Bash(.claude/skills/status/scripts/discovery.sh)
+hooks:
+  PreToolUse:
+    - hooks:
+        - type: command
+          command: "$CLAUDE_PROJECT_DIR/.claude/hooks/workflows/system-check.sh"
+          once: true
 ---
 
 Show the current state of the workflow for this project.
@@ -13,7 +19,7 @@ Show the current state of the workflow for this project.
 
 Invoke the `/migrate` skill and assess its output.
 
-**If files were updated**: STOP and wait for the user to review the changes (e.g., via `git diff`) and confirm before proceeding to Step 1.
+**If files were updated**: STOP and wait for the user to review the changes (e.g., via `git diff`) and confirm before proceeding to Step 1. Do not continue automatically.
 
 **If no updates needed**: Proceed to Step 1.
 

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

@@ -37,6 +37,8 @@ Check `author_gate_mode` in the Plan Index File frontmatter.
 
 #### If `author_gate_mode: auto`
 
+**Auto mode removes the approval pause — not the sequential process.** Each task is still invoked, authored, and logged one at a time, in order. Do not batch, skip ahead, or create multiple tasks concurrently.
+
 > *Output the next fenced block as a code block:*
 
 ```

package/skills/technical-planning/references/output-formats/tick/about.md

@@ -54,6 +54,11 @@ Add to `.gitignore`:
 
 The 3-level hierarchy (topic → phase → task) uses Tick's parent/child system. Parent tasks are implicitly blocked by their children — a parent is not "ready" until all children are complete. Explicit dependencies (`tick dep add`) handle cross-phase and cross-topic blocking.
 
+## Usage Notes
+
+- **Help**: `tick help --all` displays all available commands and flags in a single view.
+- **Output format**: The `--toon` flag is **not needed** — TOON is the default for non-interactive shells, which is what Claude Code uses. Omit it from all commands.
+
 ## Output Location
 
 Tasks are stored in a `.tick/` directory at the project root:

package/skills/technical-planning/references/output-formats/tick/authoring.md

@@ -1,5 +1,23 @@
 # Tick: Authoring
 
+## Descriptions: Inline Only
+
+**CRITICAL**: Always pass descriptions directly as inline quoted strings. Never use workarounds.
+
+```bash
+tick create "Title" --parent <id> --description "Full description here.
+
+Multi-line content works fine inside double quotes."
+```
+
+**Do NOT**:
+- Use heredocs (`<<'EOF'`) — sandbox blocks the temp files they create
+- Use the Write tool to create temp files — triggers approval prompts outside the project directory
+- Use Bash functions, variables, or subshells to construct the description
+- Write temp files anywhere (including `$TMPDIR`, `/tmp`, or the working directory)
+
+If a description contains double quotes, escape them with `\"`. That's it.
+
 ## Task Storage
 
 Tasks are created using the `tick create` command. Before creating individual tasks, establish the topic and phase parent tasks.

package/skills/technical-planning/references/output-formats/tick/updating.md

@@ -16,6 +16,8 @@ Tick uses dedicated commands for each status transition:
 
 ## Updating Task Content
 
+**Sandbox mode**: When updating large descriptions, use the Write tool + cat pattern to avoid sandbox temp file issues. See [authoring.md](authoring.md) for details.
+
 To update a task's properties:
 
 - **Title**: `tick update <task-id> --title "New title"`

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

@@ -120,16 +120,11 @@ Phase {N}: {Phase Name} — task list confirmed. Proceeding to authoring.
 
 Work through each task in the phase's task table, in order.
 
-### Parallel authoring (optional optimization)
+### Sequential authoring (mandatory)
 
-After the first `pending` task in a phase is approved, you may invoke multiple Step B agents concurrently for tasks you judge to be independent — where the authored detail of one would not inform the other. This is an invocation optimization only; the approval flow is unchanged:
+Tasks **must** be authored one at a time, in order. Each task's authored detail builds context for the next — later tasks benefit from decisions, patterns, and structure established by earlier ones. This applies regardless of gate mode. Auto-gate removes the approval pause, not the sequential process.
 
-- Present tasks one at a time, in order
-- Each task still requires explicit user approval before logging
-- If user feedback on a presented task changes context that could affect any already-authored task waiting to be presented, discard those results and re-invoke Step B
-- When uncertain about independence, default to sequential — it is always safe
-
-Never parallelize the first `pending` task in a phase. Never parallelize across phases.
+**Never** invoke multiple Step B agents concurrently. **Never** batch or skip ahead.
 
 #### If the task status is `authored`
 

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

@@ -90,14 +90,15 @@ approved_at: {YYYY-MM-DD}
 
 ```markdown
 #### Tasks
-| ID | Name | Status | Ext ID |
-|----|------|--------|--------|
-| {topic}-{phase}-{seq} | {Task Name} | {status} | |
+| ID | Name | Edge Cases | Status | Ext ID |
+|----|------|------------|--------|--------|
+| {topic}-{phase}-{seq} | {Task Name} | {comma-separated list, or "none"} | {status} | |
 ```
 
 | Field | Set when |
 |-------|----------|
 | `ID` | Task design — format: `{topic}-{phase}-{seq}` |
 | `Name` | Task design — descriptive task name |
+| `Edge Cases` | Task design — curated list scoping which edge cases this task handles |
 | `Status` | Task design → `pending`; authoring → `authored` |
 | `Ext ID` | Task authored — external identifier for the task |

package/skills/view-plan/SKILL.md

@@ -2,6 +2,12 @@
 name: view-plan
 description: "View a plan's tasks and progress, regardless of output format."
 disable-model-invocation: true
+hooks:
+  PreToolUse:
+    - hooks:
+        - type: command
+          command: "$CLAUDE_PROJECT_DIR/.claude/hooks/workflows/system-check.sh"
+          once: true
 ---
 
 Display a readable summary of a plan's phases, tasks, and status.