@leeovery/claude-technical-workflows 2.2.0 → 2.2.1

package/README.md

@@ -134,7 +134,7 @@ Discussion ──▶ Specification ──▶ Planning ──▶ Implementation
 
 **How it works:** After each phase completes, a plan mode bridge clears context and advances to the next phase automatically. You approve each transition with "clear context and continue" — this keeps each phase in a clean context window.
 
-If a session is interrupted, run `/continue-feature` to pick up where you left off. It reads artifact state to determine the next phase.
+If a session is interrupted, run `/workflow-start` to pick up where you left off. It discovers artifact state and routes to the next phase.
 
 ### Under the Hood
 
@@ -233,29 +233,30 @@ skills/
 ├── # Processing skills (model-invocable)
 ├── technical-research/              # Explore and validate ideas
 ├── technical-discussion/            # Document discussions
+├── technical-investigation/         # Investigate bugs (bugfix pipeline)
 ├── technical-specification/         # Build validated specifications
 ├── technical-planning/              # Create implementation plans
 ├── technical-implementation/        # Execute via TDD
 ├── technical-review/                # Validate against artefacts
 │
+├── # Unified entry points
+├── workflow-start/                  # Discovers state, routes by work type
+├── workflow-bridge/                 # Pipeline continuation — next phase routing
+│
 ├── # Entry-point skills (user-invocable)
 ├── migrate/                         # Keep workflow files in sync with system design
 ├── start-feature/                   # Pipeline: discussion → spec → plan → impl → review
-├── continue-feature/                # Pipeline: route feature to next phase
+├── start-bugfix/                    # Pipeline: investigation → spec → plan → impl → review
 ├── link-dependencies/               # Standalone: wire cross-topic deps
 ├── start-research/                  # Begin research
 ├── start-discussion/                # Begin discussions
+├── start-investigation/             # Begin investigation (bugfix)
 ├── start-specification/             # Begin specification
 ├── start-planning/                  # Begin planning
 ├── start-implementation/            # Begin implementation
 ├── start-review/                    # Begin review
 ├── status/                          # Show workflow status
-├── view-plan/                       # View plan tasks
-│
-├── # Bridge skills (model-invocable — pipeline pre-flight)
-├── begin-planning/                  # Pre-flight for planning in pipeline
-├── begin-implementation/            # Pre-flight for implementation in pipeline
-└── begin-review/                    # Pre-flight for review in pipeline
+└── view-plan/                       # View plan tasks
 
 agents/
 ├── review-task-verifier.md           # Verifies single task implementation for review
@@ -322,7 +323,7 @@ Independent skills that gather inputs flexibly (inline context, files, or prompt
 | Skill                                                   | Description                                                                                                                                 |
 |---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
 | [**/start-feature**](skills/start-feature/)              | Start a new feature through the full pipeline. Gathers context, creates a discussion, then bridges through specification → planning → implementation → review. |
-| [**/continue-feature**](skills/continue-feature/)        | Continue a feature through its next pipeline phase. Routes automatically based on artifact state. Used manually or from plan mode bridges.  |
+| [**/start-bugfix**](skills/start-bugfix/)                | Start a bugfix through the pipeline. Gathers bug context, creates an investigation, then bridges through specification → planning → implementation → review. |
 | [**/link-dependencies**](skills/link-dependencies/)      | Link external dependencies across topics. Scans plans and wires up unresolved cross-topic dependencies.                                    |
 
 ### Creating Custom Skills

package/hooks/workflows/compact-recovery.sh

@@ -49,7 +49,7 @@ Skill: ${skill}
 
 The files on disk are authoritative — not the conversation summary.
 
-When the processing skill concludes, it will invoke workflow:bridge automatically
+When the processing skill concludes, it will invoke workflow-bridge automatically
 if the artifact has a work_type set. Do not manually handle pipeline continuation."
 
 # Escape context for JSON output

package/package.json

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

package/skills/start-bugfix/references/invoke-investigation.md

@@ -43,4 +43,4 @@ The investigation frontmatter should include:
 Invoke the technical-investigation skill.
 ```
 
-When the investigation concludes, the processing skill will detect `work_type: bugfix` in the artifact and invoke workflow:bridge automatically.
+When the investigation concludes, the processing skill will detect `work_type: bugfix` in the artifact and invoke workflow-bridge automatically.

package/skills/start-feature/references/invoke-discussion.md

@@ -25,4 +25,4 @@ The discussion frontmatter should include:
 Invoke the technical-discussion skill.
 ```
 
-When the discussion concludes, the processing skill will detect `work_type: feature` in the artifact and invoke workflow:bridge automatically.
+When the discussion concludes, the processing skill will detect `work_type: feature` in the artifact and invoke workflow-bridge automatically.

package/skills/start-feature/references/invoke-research.md

@@ -26,4 +26,4 @@ The research frontmatter should include:
 Invoke the technical-research skill.
 ```
 
-When a research topic is parked as discussion-ready, the processing skill will offer pipeline continuation via workflow:bridge.
+When a research topic is parked as discussion-ready, the processing skill will offer pipeline continuation via workflow-bridge.

package/skills/technical-discussion/SKILL.md

@@ -138,14 +138,14 @@ Incorporate the user's context into the discussion, commit, then re-present the
 
 **If work_type is set** (feature, bugfix, or greenfield):
 
-This discussion is part of a pipeline. Invoke the `/workflow:bridge` skill:
+This discussion is part of a pipeline. Invoke the `/workflow-bridge` skill:
 
 ```
 Pipeline bridge for: {topic}
 Work type: {work_type from artifact frontmatter}
 Completed phase: discussion
 
-Invoke the workflow:bridge skill to enter plan mode with continuation instructions.
+Invoke the workflow-bridge skill to enter plan mode with continuation instructions.
 ```
 
 **If work_type is not set and other in-progress discussions exist:**

package/skills/technical-implementation/SKILL.md

@@ -336,14 +336,14 @@ Commit: `impl({topic}): complete implementation`
 
 **If work_type is set** (feature, bugfix, or greenfield):
 
-This implementation is part of a pipeline. Invoke the `/workflow:bridge` skill:
+This implementation is part of a pipeline. Invoke the `/workflow-bridge` skill:
 
 ```
 Pipeline bridge for: {topic}
 Work type: {work_type from plan frontmatter}
 Completed phase: implementation
 
-Invoke the workflow:bridge skill to enter plan mode with continuation instructions.
+Invoke the workflow-bridge skill to enter plan mode with continuation instructions.
 ```
 
 **If work_type is not set:**

package/skills/technical-investigation/SKILL.md

@@ -224,14 +224,14 @@ detail the exact fix approach, acceptance criteria, and testing plan.
 
 **If work_type is set** (bugfix):
 
-This investigation is part of a pipeline. Invoke the `/workflow:bridge` skill:
+This investigation is part of a pipeline. Invoke the `/workflow-bridge` skill:
 
 ```
 Pipeline bridge for: {topic}
 Work type: bugfix
 Completed phase: investigation
 
-Invoke the workflow:bridge skill to enter plan mode with continuation instructions.
+Invoke the workflow-bridge skill to enter plan mode with continuation instructions.
 ```
 
 **If work_type is not set:**

package/skills/technical-planning/SKILL.md

@@ -268,14 +268,14 @@ Status has been marked as `concluded`. The plan is ready for implementation.
 
 **If work_type is set** (feature, bugfix, or greenfield):
 
-This plan is part of a pipeline. Invoke the `/workflow:bridge` skill:
+This plan is part of a pipeline. Invoke the `/workflow-bridge` skill:
 
 ```
 Pipeline bridge for: {topic}
 Work type: {work_type from artifact frontmatter}
 Completed phase: planning
 
-Invoke the workflow:bridge skill to enter plan mode with continuation instructions.
+Invoke the workflow-bridge skill to enter plan mode with continuation instructions.
 ```
 
 **If work_type is not set:**

package/skills/technical-research/SKILL.md

@@ -147,14 +147,14 @@ Continue with whatever's next — another topic, a different angle, or wrapping
 
 #### If discuss
 
-Invoke the `/workflow:bridge` skill:
+Invoke the `/workflow-bridge` skill:
 
 ```
 Pipeline bridge for: {topic}
 Work type: {work_type from artifact frontmatter}
 Completed phase: research
 
-Invoke the workflow:bridge skill to enter plan mode with continuation instructions.
+Invoke the workflow-bridge skill to enter plan mode with continuation instructions.
 ```
 
 **If work_type is not set:**

package/skills/technical-review/references/review-actions-loop.md

@@ -34,14 +34,14 @@ No actionable findings. All reviews passed with no required changes.
 
 **If work_type is set** (feature, bugfix, or greenfield):
 
-This review is part of a pipeline. The pipeline is complete. Invoke the `/workflow:bridge` skill:
+This review is part of a pipeline. The pipeline is complete. Invoke the `/workflow-bridge` skill:
 
 ```
 Pipeline bridge for: {topic}
 Work type: {work_type from plan frontmatter}
 Completed phase: review
 
-Invoke the workflow:bridge skill to enter plan mode with completion confirmation.
+Invoke the workflow-bridge skill to enter plan mode with completion confirmation.
 ```
 
 **If work_type is not set:**
@@ -92,14 +92,14 @@ User has chosen to skip synthesis. This is a terminal condition, but check for p
 
 **If work_type is set** (feature, bugfix, or greenfield):
 
-This review is part of a pipeline. Invoke the `/workflow:bridge` skill:
+This review is part of a pipeline. Invoke the `/workflow-bridge` skill:
 
 ```
 Pipeline bridge for: {topic}
 Work type: {work_type from plan frontmatter}
 Completed phase: review
 
-Invoke the workflow:bridge skill to enter plan mode with continuation instructions.
+Invoke the workflow-bridge skill to enter plan mode with continuation instructions.
 ```
 
 **If work_type is not set:**

package/skills/technical-specification/references/spec-completion.md

@@ -121,14 +121,14 @@ Check the specification frontmatter for `work_type`.
 
 #### If work_type is set (feature, bugfix, or greenfield)
 
-This specification is part of a pipeline. Invoke the `/workflow:bridge` skill:
+This specification is part of a pipeline. Invoke the `/workflow-bridge` skill:
 
 ```
 Pipeline bridge for: {topic}
 Work type: {work_type from artifact frontmatter}
 Completed phase: specification
 
-Invoke the workflow:bridge skill to enter plan mode with continuation instructions.
+Invoke the workflow-bridge skill to enter plan mode with continuation instructions.
 ```
 
 #### If work_type is not set

package/skills/{workflow/bridge → workflow-bridge}/SKILL.md

@@ -1,7 +1,7 @@
 ---
-name: workflow:bridge
+name: workflow-bridge
 user-invocable: false
-allowed-tools: Bash(.claude/skills/workflow/bridge/scripts/discovery.sh)
+allowed-tools: Bash(.claude/skills/workflow-bridge/scripts/discovery.sh)
 ---
 
 Enter plan mode with deterministic continuation instructions.
@@ -26,13 +26,13 @@ Determine the next phase by running discovery.
 #### If work type is "feature"
 
 ```bash
-.claude/skills/workflow/bridge/scripts/discovery.sh --feature --topic "{topic}"
+.claude/skills/workflow-bridge/scripts/discovery.sh --feature --topic "{topic}"
 ```
 
 #### If work type is "bugfix"
 
 ```bash
-.claude/skills/workflow/bridge/scripts/discovery.sh --bugfix --topic "{topic}"
+.claude/skills/workflow-bridge/scripts/discovery.sh --bugfix --topic "{topic}"
 ```
 
 Parse the output to extract:
@@ -41,7 +41,7 @@ Parse the output to extract:
 #### If work type is "greenfield"
 
 ```bash
-.claude/skills/workflow/bridge/scripts/discovery.sh --greenfield
+.claude/skills/workflow-bridge/scripts/discovery.sh --greenfield
 ```
 
 Parse the output to extract:

package/skills/{workflow/bridge → workflow-bridge}/references/bugfix-continuation.md

@@ -1,6 +1,6 @@
 # Bugfix Continuation
 
-*Reference for **[workflow:bridge](../SKILL.md)***
+*Reference for **[workflow-bridge](../SKILL.md)***
 
 ---
 

package/skills/{workflow/bridge → workflow-bridge}/references/feature-continuation.md

@@ -1,6 +1,6 @@
 # Feature Continuation
 
-*Reference for **[workflow:bridge](../SKILL.md)***
+*Reference for **[workflow-bridge](../SKILL.md)***
 
 ---
 

package/skills/{workflow/bridge → workflow-bridge}/references/greenfield-continuation.md

@@ -1,6 +1,6 @@
 # Greenfield Continuation
 
-*Reference for **[workflow:bridge](../SKILL.md)***
+*Reference for **[workflow-bridge](../SKILL.md)***
 
 ---
 
@@ -120,7 +120,7 @@ What would you like to do next?
 7. Continue research
 8. Start new research
 9. Start new discussion
-10. Stop here — resume later with /workflow:start
+10. Stop here — resume later with /workflow-start
 
 Select an option (enter number):
 · · · · · · · · · · · ·
@@ -143,7 +143,7 @@ Recreate with actual topics and states from discovery. Only include options that
 ```
 Session Paused
 
-To resume later, run /workflow:start — it will discover your
+To resume later, run /workflow-start — it will discover your
 current state and present all available options.
 ```
 

package/skills/{workflow/bridge → workflow-bridge}/scripts/discovery.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 #
-# Topic-specific discovery script for /workflow:bridge.
+# Topic-specific discovery script for /workflow-bridge.
 #
 # Usage:
 #   discovery.sh --feature --topic <topic>

package/skills/{workflow/start → workflow-start}/SKILL.md

@@ -1,7 +1,7 @@
 ---
-name: workflow:start
+name: workflow-start
 disable-model-invocation: true
-allowed-tools: Bash(.claude/skills/workflow/start/scripts/discovery.sh)
+allowed-tools: Bash(.claude/skills/workflow-start/scripts/discovery.sh)
 hooks:
   PreToolUse:
     - hooks:
@@ -44,12 +44,12 @@ Invoke the `/migrate` skill and assess its output.
 
 ## Step 1: Run Discovery
 
-!`.claude/skills/workflow/start/scripts/discovery.sh`
+!`.claude/skills/workflow-start/scripts/discovery.sh`
 
 If the above shows a script invocation rather than YAML output, the dynamic content preprocessor did not run. Execute the script before continuing:
 
 ```bash
-.claude/skills/workflow/start/scripts/discovery.sh
+.claude/skills/workflow-start/scripts/discovery.sh
 ```
 
 Parse the output to understand the current workflow state:

package/skills/{workflow/start → workflow-start}/references/bugfix-routing.md

@@ -1,6 +1,6 @@
 # Bugfix Routing
 
-*Reference for **[workflow:start](../SKILL.md)***
+*Reference for **[workflow-start](../SKILL.md)***
 
 ---
 

package/skills/{workflow/start → workflow-start}/references/feature-routing.md

@@ -1,6 +1,6 @@
 # Feature Routing
 
-*Reference for **[workflow:start](../SKILL.md)***
+*Reference for **[workflow-start](../SKILL.md)***
 
 ---
 

package/skills/{workflow/start → workflow-start}/references/greenfield-routing.md

@@ -1,6 +1,6 @@
 # Greenfield Routing
 
-*Reference for **[workflow:start](../SKILL.md)***
+*Reference for **[workflow-start](../SKILL.md)***
 
 ---
 

package/skills/{workflow/start → workflow-start}/references/work-type-selection.md

@@ -1,6 +1,6 @@
 # Work Type Selection
 
-*Reference for **[workflow:start](../SKILL.md)***
+*Reference for **[workflow-start](../SKILL.md)***
 
 ---
 

package/skills/{workflow/start → workflow-start}/scripts/discovery.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 #
-# Comprehensive workflow discovery for /workflow:start.
+# Comprehensive workflow discovery for /workflow-start.
 #
 # Scans all workflow directories and groups artifacts by work_type:
 # - greenfield: phase-centric, all topics (work_type: greenfield or unset)