@leeovery/claude-technical-workflows 2.1.41 → 2.2.0

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

@@ -4,26 +4,7 @@
 
 ---
 
-This step constructs the complete plan — defining phases, designing task lists, and authoring every task. It operates as a nested structure:
-
-    ┌─────────────────────────────────────────────────────┐
-    │                                                     │
-    │  Phase Structure — define or review all phases      │
-    │                                                     │
-    │  ┌─────────────────────────────────────────────┐    │
-    │  │  For each phase:                            │    │
-    │  │                                             │    │
-    │  │    Step A → Define tasks for the phase      │    │
-    │  │                                             │    │
-    │  │      ┌─────────────────────────────────┐    │    │
-    │  │      │  For each task in the phase:    │    │    │
-    │  │      │                                 │    │    │
-    │  │      │    Step B → Author the task     │    │    │
-    │  │      └─────────────────────────────────┘    │    │
-    │  │                                             │    │
-    │  └─────────────────────────────────────────────┘    │
-    │                                                     │
-    └─────────────────────────────────────────────────────┘
+This step constructs the complete plan — defining phases, designing task lists, and authoring every task.
 
 ---
 
@@ -65,9 +46,9 @@ every stage.
 
 This phase needs task design.
 
-→ Go to **Step A** with this phase.
+→ Proceed to **A. Define Tasks** with this phase.
 
-After Step A returns with an approved task table, continue to **Author Tasks for the Phase** below.
+After **A. Define Tasks** returns with an approved task table, proceed to **Author Tasks for the Phase** below.
 
 #### If the phase has a task table
 
@@ -89,7 +70,7 @@ Check `task_list_gate_mode` in the Plan Index File frontmatter.
 Phase {N}: {Phase Name} — task list confirmed. Proceeding to authoring.
 ```
 
-→ Continue to **Author Tasks for the Phase** below.
+→ Proceed to **Author Tasks for the Phase** below.
 
 #### If `task_list_gate_mode: gated` (existing task table)
 
@@ -108,11 +89,11 @@ Phase {N}: {Phase Name} — task list confirmed. Proceeding to authoring.
 
 #### If the user wants changes
 
-→ Go to **Step A** with this phase for revision.
+→ Proceed to **A. Define Tasks** with this phase for revision.
 
 #### If confirmed
 
-→ Continue to **Author Tasks for the Phase** below.
+→ Proceed to **Author Tasks for the Phase** below.
 
 ---
 
@@ -130,13 +111,13 @@ All tasks already written.
 Phase {N}: {Phase Name} — all tasks already authored.
 ```
 
-→ Continue to the next phase.
+→ Proceed to the next phase.
 
 #### If any tasks in the phase have status `pending`
 
-→ Go to **Step B** for the entire phase.
+→ Proceed to **B. Author Tasks** for the entire phase.
 
-After Step B returns, all tasks in the phase are authored.
+After **B. Author Tasks** returns, all tasks in the phase are authored.
 
 If the user navigates mid-approval, the scratch file preserves approval state. On return, resume from the first non-approved task.
 
@@ -166,12 +147,12 @@ All phases are complete. The plan has **{N} phases** with **{M} tasks** total.
 
 ---
 
-## Step A: Define Tasks
+## A. Define Tasks
 
 Load **[define-tasks.md](define-tasks.md)** and follow its instructions as written. This step designs and approves a task list for **one phase**.
 
 ---
 
-## Step B: Author Tasks
+## B. Author Tasks
 
 Load **[author-tasks.md](author-tasks.md)** and follow its instructions as written. This step authors **all tasks for the phase** via a batch agent and returns.

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

@@ -50,7 +50,7 @@ Record the current cycle number — passed to both review agents for tracking fi
 
 #### If no findings were surfaced in this cycle
 
-→ Proceed directly to **E. Completion**.
+→ Proceed to **E. Completion**.
 
 #### If findings were surfaced
 
@@ -101,7 +101,7 @@ with fresh context — 2-3 cycles typically surface anything cascading.
 
 #### If proceed
 
-→ Continue to **E. Completion**.
+→ Proceed to **E. Completion**.
 
 ---
 
@@ -119,4 +119,4 @@ with fresh context — 2-3 cycles typically surface anything cascading.
 Plan review complete — {N} cycle(s), all tracking files finalised.
 ```
 
-→ Return to **[technical-planning SKILL.md](../SKILL.md)** for **Step 8**.
+→ Return to **[the skill](../SKILL.md)** for **Step 8**.

package/skills/technical-research/SKILL.md

@@ -1,6 +1,5 @@
 ---
 name: technical-research
-description: "Explore ideas, validate concepts, and research broadly across technical, business, and market domains. Use when: (1) User has a new idea to explore, (2) Need to research a topic deeply, (3) Validating feasibility - technical, business, or market, (4) Learning and exploration without necessarily building anything, (5) User says 'research this' or 'explore this idea', (6) Brain dumping early thoughts before formal discussion. Creates research documents in .workflows/research/ that may feed into discussion or specification."
 user-invocable: false
 ---
 
@@ -123,7 +122,44 @@ Document the convergence point in the research file using this marker:
 > **Discussion-ready**: {Brief summary of what was explored and why it's ready for decision-making. Key tradeoffs or options identified.}
 ```
 
-Then continue with whatever's next — another topic, a different angle, or wrapping up the session.
+Commit the file.
+
+Check the research artifact frontmatter for `work_type`.
+
+**If work_type is set** (feature or greenfield):
+
+> *Output the next fenced block as markdown (not a code block):*
+
+```
+· · · · · · · · · · · ·
+This topic is marked discussion-ready. Would you like to:
+
+- **`c`/`continue`** — Continue exploring
+- **`d`/`discuss`** — Transition to discussion phase
+· · · · · · · · · · · ·
+```
+
+**STOP.** Wait for user response.
+
+#### If continue
+
+Continue with whatever's next — another topic, a different angle, or wrapping up the session.
+
+#### If discuss
+
+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.
+```
+
+**If work_type is not set:**
+
+Continue with whatever's next — another topic, a different angle, or wrapping up the session.
 
 ### If the user keeps digging
 

package/skills/technical-review/SKILL.md

@@ -1,6 +1,5 @@
 ---
 name: technical-review
-description: "Validate completed implementation against plan tasks and acceptance criteria. Use when: (1) Implementation is complete, (2) User wants validation before merging/shipping, (3) Quality gate check needed after implementation. Reviews ALL plan tasks for implementation correctness, test adequacy, and code quality. Produces structured feedback (approve, request changes, or comments) - does NOT fix code."
 user-invocable: false
 ---
 
@@ -53,7 +52,7 @@ The specification is optional — the review can proceed with just the plan.
 
 Analysis of existing review findings was requested. The review has already been completed.
 
-→ Go directly to **Step 6**.
+→ Proceed to **Step 6**.
 
 ---
 

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

@@ -30,6 +30,30 @@ Check the verdict(s) from the review(s) being analyzed.
 No actionable findings. All reviews passed with no required changes.
 ```
 
+**Check for pipeline continuation** — Read the plan file (`.workflows/planning/{topic}/plan.md`) and check for `work_type`
+
+**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:
+
+```
+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.
+```
+
+**If work_type is not set:**
+
+> *Output the next fenced block as a code block:*
+
+```
+Review complete: {topic}
+
+All checks passed. The implementation has been validated.
+```
+
 **STOP.** Do not proceed — terminal condition.
 
 #### If any verdict is "Request Changes"
@@ -62,6 +86,24 @@ Proceed with synthesis?
 
 #### If no
 
+User has chosen to skip synthesis. This is a terminal condition, but check for pipeline continuation first.
+
+**Check for pipeline continuation** — Read the plan file (`.workflows/planning/{topic}/plan.md`) and check for `work_type`
+
+**If work_type is set** (feature, bugfix, or greenfield):
+
+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.
+```
+
+**If work_type is not set:**
+
 **STOP.** Do not proceed — terminal condition.
 
 #### If verdict is "Comments Only"
@@ -279,7 +321,7 @@ Review findings have been synthesized into {N} implementation tasks.
 
 ## Instructions
 
-1. Invoke `/start-implementation`
+1. Invoke `start-implementation`
 2. The skill will detect the new tasks and start executing them
 
 ## Context

package/skills/technical-specification/SKILL.md

@@ -1,6 +1,5 @@
 ---
 name: technical-specification
-description: "Build validated specifications from source material through collaborative refinement. Use when: (1) User asks to create/build a specification from source material, (2) User wants to validate and refine content before planning, (3) Converting source material (discussions, research, requirements) into standalone specifications, (4) User says 'specify this' or 'create a spec', (5) Need to filter hallucinations and enrich gaps before formal planning. Creates specifications in .workflows/specification/{topic}/specification.md that can be used to build implementation plans."
 user-invocable: false
 ---
 
@@ -124,7 +123,7 @@ Found existing specification for **{topic}**.
 
 Reset `finding_gate_mode` to `gated` in the specification frontmatter (fresh invocation = fresh gates).
 
-→ Skip Steps 1–2, proceed to **Step 3**.
+→ Proceed to **Step 3** (skipping Steps 1–2).
 
 #### If `restart`
 

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

@@ -4,7 +4,7 @@
 
 ---
 
-## Step 1: Determine Specification Type
+## A. Determine Specification Type
 
 Before asking for sign-off, assess whether this is a **feature** or **cross-cutting** specification. See **[specification-format.md](specification-format.md)** for type definitions.
 
@@ -37,7 +37,7 @@ Does this assessment seem correct?
 
 ---
 
-## Step 2: Verify Tracking Files Complete
+## B. Verify Tracking Files Complete
 
 Before proceeding to sign-off, confirm that all review tracking files across all cycles have `status: complete`:
 
@@ -50,7 +50,7 @@ If any tracking file still shows `status: in-progress`, mark it complete now.
 
 ---
 
-## Step 3: Sign-Off
+## C. Sign-Off
 
 > *Output the next fenced block as markdown (not a code block):*
 
@@ -69,11 +69,11 @@ Discuss the user's context, apply any changes, then re-present the sign-off prom
 
 #### If yes
 
-→ Proceed to **Step 4**.
+→ Proceed to **D. Update Frontmatter and Conclude**.
 
 ---
 
-## Step 4: Update Frontmatter and Conclude
+## D. Update Frontmatter and Conclude
 
 Update the specification frontmatter:
 
@@ -101,7 +101,7 @@ Commit: `spec({topic}): conclude specification`
 
 ---
 
-## Step 5: Handle Source Specifications
+## E. Handle Source Specifications
 
 If any of your sources were **existing specifications** (as opposed to discussions, research, or other reference material), these have now been consolidated into the new specification.
 
@@ -112,3 +112,31 @@ If any of your sources were **existing specifications** (as opposed to discussio
    ```
 2. Inform the user which files were updated
 3. Commit: `spec({topic}): mark source specifications as superseded`
+
+---
+
+## F. Pipeline Continuation
+
+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:
+
+```
+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.
+```
+
+#### If work_type is not set
+
+> *Output the next fenced block as a code block:*
+
+```
+Specification concluded: {topic}
+
+The specification is ready for planning. Run /start-planning to begin.
+```

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

@@ -106,4 +106,4 @@ This is the end of this iteration.
 
 #### If all topics are covered
 
-→ Return to **[technical-specification SKILL.md](../SKILL.md)** for **Step 5**.
+→ Return to **[the skill](../SKILL.md)** for **Step 5**.

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

@@ -56,11 +56,11 @@ were still found last cycle) or skip to completion.
 
 #### If `proceed`
 
-→ Continue to **B. Phase 1 — Input Review**.
+→ Proceed to **B. Phase 1 — Input Review**.
 
 #### If `skip`
 
-→ Jump to **E. Completion**.
+→ Proceed to **E. Completion**.
 
 ---
 
@@ -86,7 +86,7 @@ were still found last cycle) or skip to completion.
 
 #### If no findings were surfaced in either phase of this cycle
 
-→ Skip the re-loop prompt and proceed directly to **E. Completion** (nothing to re-analyse).
+→ Proceed to **E. Completion** (nothing to re-analyse).
 
 #### If findings were surfaced
 
@@ -133,7 +133,7 @@ Auto-review has not converged after 5 cycles — escalating for human review.
 
 #### If proceed
 
-→ Continue to **E. Completion**.
+→ Proceed to **E. Completion**.
 
 ---
 
@@ -151,4 +151,4 @@ Auto-review has not converged after 5 cycles — escalating for human review.
 Specification review complete — {N} cycle(s), all tracking files finalised.
 ```
 
-→ Return to **[technical-specification SKILL.md](../SKILL.md)** for **Step 7**.
+→ Return to **[the skill](../SKILL.md)** for **Step 7**.

package/skills/view-plan/SKILL.md

@@ -1,6 +1,5 @@
 ---
 name: view-plan
-description: "View a plan's tasks and progress, regardless of output format."
 disable-model-invocation: true
 hooks:
   PreToolUse:

package/skills/workflow/bridge/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: workflow:bridge
+user-invocable: false
+allowed-tools: Bash(.claude/skills/workflow/bridge/scripts/discovery.sh)
+---
+
+Enter plan mode with deterministic continuation instructions.
+
+This skill is invoked by processing skills (technical-discussion, technical-specification, etc.) when a pipeline phase concludes. It discovers the next phase and creates a plan mode handoff that survives context compaction.
+
+> **ZERO OUTPUT RULE**: Do not narrate your processing. Produce no output until a step or reference file explicitly specifies display content. No "proceeding with...", no discovery summaries, no routing decisions, no transition text. Your first output must be content explicitly called for by the instructions.
+
+## Instructions
+
+This skill receives context from the calling processing skill:
+- **Topic**: The topic name
+- **Work type**: greenfield, feature, or bugfix
+- **Completed phase**: The phase that just concluded
+
+---
+
+## Step 1: Run Discovery
+
+Determine the next phase by running discovery.
+
+#### If work type is "feature"
+
+```bash
+.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}"
+```
+
+Parse the output to extract:
+- `next_phase`: The computed next phase for this topic
+
+#### If work type is "greenfield"
+
+```bash
+.claude/skills/workflow/bridge/scripts/discovery.sh --greenfield
+```
+
+Parse the output to extract:
+- `state`: Counts of artifacts across all phases
+- Phase-specific file lists with their statuses
+
+→ Proceed to **Step 2**.
+
+---
+
+## Step 2: Route to Continuation Reference
+
+Based on work type, load the appropriate continuation reference:
+
+#### If work type is "feature"
+
+Load **[feature-continuation.md](references/feature-continuation.md)** and follow its instructions as written.
+
+#### If work type is "bugfix"
+
+Load **[bugfix-continuation.md](references/bugfix-continuation.md)** and follow its instructions as written.
+
+#### If work type is "greenfield"
+
+Load **[greenfield-continuation.md](references/greenfield-continuation.md)** and follow its instructions as written.
+
+---
+
+## Notes
+
+**Feature/bugfix** continuation references:
+1. Use discovery output to compute a single `next_phase`
+2. Enter plan mode with instructions to invoke `start-{next_phase}` with topic + work_type
+3. Exit plan mode for user approval
+
+The user will then clear context, and the fresh session will invoke the appropriate start-* skill with the topic and work_type provided, causing it to skip discovery and proceed directly to validation/processing.
+
+**Greenfield** continuation is interactive — greenfield is phase-centric with multiple actionable items, so there is no single next phase. The reference displays state, presents a menu of choices, waits for user selection, then enters plan mode with that specific choice. The plan mode content is deterministic (same as feature/bugfix) once the user has chosen.

package/skills/workflow/bridge/references/bugfix-continuation.md

@@ -0,0 +1,59 @@
+# Bugfix Continuation
+
+*Reference for **[workflow:bridge](../SKILL.md)***
+
+---
+
+Route a bugfix to its next pipeline phase and enter plan mode with continuation instructions.
+
+Bugfix pipeline: Investigation → Specification → Planning → Implementation → Review
+
+## Phase Routing
+
+Use `next_phase` from discovery output to determine the target skill:
+
+| next_phase | Target Skill | Plan Mode Instructions |
+|------------|--------------|------------------------|
+| investigation | start-investigation | Resume investigation for topic |
+| specification | start-specification | Start/resume specification for topic |
+| planning | start-planning | Start/resume planning for topic |
+| implementation | start-implementation | Start/resume implementation for topic |
+| review | start-review | Start review for topic |
+| done | (terminal) | Pipeline complete |
+
+## Generate Plan Mode Content
+
+#### If next_phase is "done"
+
+> *Output the next fenced block as a code block:*
+
+```
+Bugfix Complete
+
+"{topic:(titlecase)}" has completed all pipeline phases.
+```
+
+**STOP.** Do not proceed — terminal condition.
+
+#### Otherwise
+
+Enter plan mode with the following content:
+
+```
+# Continue Bugfix: {topic}
+
+The previous phase has concluded. Continue the pipeline.
+
+## Next Step
+
+Invoke `/start-{next_phase} bugfix {topic}`
+
+Arguments: work_type = bugfix, topic = {topic}
+The skill will skip discovery and proceed directly to validation.
+
+## How to proceed
+
+Clear context and continue.
+```
+
+Exit plan mode. The user will approve and clear context.

package/skills/workflow/bridge/references/feature-continuation.md

@@ -0,0 +1,60 @@
+# Feature Continuation
+
+*Reference for **[workflow:bridge](../SKILL.md)***
+
+---
+
+Route a feature to its next pipeline phase and enter plan mode with continuation instructions.
+
+Feature pipeline: (Research) → Discussion → Specification → Planning → Implementation → Review
+
+## Phase Routing
+
+Use `next_phase` from discovery output to determine the target skill:
+
+| next_phase | Target Skill | Plan Mode Instructions |
+|------------|--------------|------------------------|
+| research | start-research | Resume research for topic |
+| discussion | start-discussion | Start/resume discussion for topic |
+| specification | start-specification | Start/resume specification for topic |
+| planning | start-planning | Start/resume planning for topic |
+| implementation | start-implementation | Start/resume implementation for topic |
+| review | start-review | Start review for topic |
+| done | (terminal) | Pipeline complete |
+
+## Generate Plan Mode Content
+
+#### If next_phase is "done"
+
+> *Output the next fenced block as a code block:*
+
+```
+Feature Complete
+
+"{topic:(titlecase)}" has completed all pipeline phases.
+```
+
+**STOP.** Do not proceed — terminal condition.
+
+#### Otherwise
+
+Enter plan mode with the following content:
+
+```
+# Continue Feature: {topic}
+
+The previous phase has concluded. Continue the pipeline.
+
+## Next Step
+
+Invoke `/start-{next_phase} feature {topic}`
+
+Arguments: work_type = feature, topic = {topic}
+The skill will skip discovery and proceed directly to validation.
+
+## How to proceed
+
+Clear context and continue.
+```
+
+Exit plan mode. The user will approve and clear context.