@leeovery/claude-technical-workflows 2.1.42 → 2.2.1

package/skills/continue-feature/references/invoke-planning.md

@@ -1,43 +0,0 @@
-# Invoke Planning
-
-*Reference for **[continue-feature](../SKILL.md)***
-
----
-
-Invoke the begin-planning bridge skill for this topic.
-
-## Save Session State
-
-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 and continue the feature pipeline if the conversation is compacted.
-```
-
-```bash
-.claude/hooks/workflows/write-session-state.sh \
-  "{topic}" \
-  "skills/technical-planning/SKILL.md" \
-  ".workflows/planning/{topic}/plan.md" \
-  --pipeline "This session is part of the feature pipeline. After the plan concludes, return to the continue-feature skill and execute Step 7 (Phase Bridge). Load: skills/continue-feature/references/phase-bridge.md"
-```
-
-## Handoff
-
-Invoke the [begin-planning](../../begin-planning/SKILL.md) skill:
-
-```
-Planning pre-flight for: {topic}
-Specification: .workflows/specification/{topic}/specification.md
-
-PIPELINE CONTINUATION — When planning concludes (plan status: concluded),
-you MUST return to the continue-feature skill and execute Step 7 (Phase Bridge).
-Load: skills/continue-feature/references/phase-bridge.md
-Do not end the session after planning — the feature pipeline continues.
-
-Invoke the begin-planning skill.
-```
-
-The bridge skill handles cross-cutting context, additional context gathering, and the handoff to technical-planning.

package/skills/continue-feature/references/invoke-review.md

@@ -1,43 +0,0 @@
-# Invoke Review
-
-*Reference for **[continue-feature](../SKILL.md)***
-
----
-
-Invoke the begin-review bridge skill for this topic.
-
-## Save Session State
-
-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 and continue the feature pipeline if the conversation is compacted.
-```
-
-```bash
-.claude/hooks/workflows/write-session-state.sh \
-  "{topic}" \
-  "skills/technical-review/SKILL.md" \
-  ".workflows/review/{topic}/r{N}/review.md" \
-  --pipeline "This session is part of the feature pipeline. After the review concludes, return to the continue-feature skill and execute Step 7 (Phase Bridge). Load: skills/continue-feature/references/phase-bridge.md"
-```
-
-## Handoff
-
-Invoke the [begin-review](../../begin-review/SKILL.md) skill:
-
-```
-Review pre-flight for: {topic}
-Plan: .workflows/planning/{topic}/plan.md
-
-PIPELINE CONTINUATION — When review concludes,
-you MUST return to the continue-feature skill and execute Step 7 (Phase Bridge).
-Load: skills/continue-feature/references/phase-bridge.md
-Do not end the session after review — the feature pipeline continues.
-
-Invoke the begin-review skill.
-```
-
-The bridge skill handles discovery, validation, version detection, and the handoff to technical-review.

package/skills/continue-feature/references/invoke-specification.md

@@ -1,55 +0,0 @@
-# Invoke Specification
-
-*Reference for **[continue-feature](../SKILL.md)***
-
----
-
-Invoke the specification skill for this topic.
-
-## Check Source Material
-
-The specification needs source material. Check what's available:
-
-1. **Discussion document**: `.workflows/discussion/{topic}.md`
-   - If exists and concluded → use as primary source
-   - If exists and in-progress → this shouldn't happen (detect-phase would have routed to discussion)
-
-2. If no discussion exists, this is an error — the pipeline expects a concluded discussion before specification. Report it and stop.
-
-## Save Session State
-
-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 and continue the feature pipeline if the conversation is compacted.
-```
-
-```bash
-.claude/hooks/workflows/write-session-state.sh \
-  "{topic}" \
-  "skills/technical-specification/SKILL.md" \
-  ".workflows/specification/{topic}/specification.md" \
-  --pipeline "This session is part of the feature pipeline. After the specification concludes, return to the continue-feature skill and execute Step 7 (Phase Bridge). Load: skills/continue-feature/references/phase-bridge.md"
-```
-
-## Handoff
-
-Invoke the [technical-specification](../../technical-specification/SKILL.md) skill:
-
-```
-Specification session for: {topic}
-
-Source material:
-- Discussion: .workflows/discussion/{topic}.md
-
-Topic name: {topic}
-
-PIPELINE CONTINUATION — When this specification concludes (status: concluded),
-you MUST return to the continue-feature skill and execute Step 7 (Phase Bridge).
-Load: skills/continue-feature/references/phase-bridge.md
-Do not end the session after the specification — the feature pipeline continues.
-
-Invoke the technical-specification skill.
-```

package/skills/continue-feature/references/phase-bridge.md

@@ -1,57 +0,0 @@
-# Phase Bridge
-
-*Reference for **[continue-feature](../SKILL.md)***
-
----
-
-The phase bridge clears context between pipeline phases using plan mode. This is necessary because each phase can consume significant context, and starting fresh prevents degradation.
-
-## Determine Next Phase
-
-Check which step just completed to determine what continue-feature will route to next:
-
-- Just completed **specification** (Step 3) → next session routes to planning
-- Just completed **planning** (Step 4) → next session routes to implementation
-- Just completed **implementation** (Step 5) → next session routes to review
-- Just completed **review** (Step 6) → pipeline is done
-
-#### If review just completed
-
-> *Output the next fenced block as a code block:*
-
-```
-Feature Complete
-
-"{topic:(titlecase)}" has completed all pipeline phases.
-```
-
-**STOP.** Do not proceed — terminal condition.
-
-## Enter Plan Mode
-
-Enter plan mode and write the following plan:
-
-```
-# Continue Feature: {topic}
-
-The previous phase for "{topic}" has concluded. The next session should
-continue the feature pipeline.
-
-## Instructions
-
-1. Invoke the `/continue-feature` skill for topic "{topic}"
-2. The skill will detect the current phase and route accordingly
-
-## Context
-
-- Topic: {topic}
-- Previous phase: {phase that just completed}
-- Expected next phase: {next phase based on routing above}
-
-## How to proceed
-
-Clear context and continue. Claude will invoke continue-feature
-with the topic above and route to the next phase automatically.
-```
-
-Exit plan mode. The user will approve and clear context, and the fresh session will pick up with continue-feature routing to the correct phase.

package/skills/continue-feature/scripts/discovery.sh

@@ -1,233 +0,0 @@
-#!/bin/bash
-#
-# Cross-phase discovery script for /continue-feature.
-#
-# Scans all workflow directories (discussion, specification, planning,
-# implementation) and builds a unified topic list with phase state
-# and next_phase computation.
-#
-# Outputs structured YAML that the command can consume directly.
-#
-
-set -eo pipefail
-
-DISC_DIR=".workflows/discussion"
-SPEC_DIR=".workflows/specification"
-PLAN_DIR=".workflows/planning"
-IMPL_DIR=".workflows/implementation"
-REVIEW_DIR=".workflows/review"
-
-# Helper: Extract a frontmatter field value from a file
-# Usage: extract_field <file> <field_name>
-extract_field() {
-    local file="$1"
-    local field="$2"
-    local value=""
-
-    # Extract from YAML frontmatter (file must start with ---)
-    if head -1 "$file" 2>/dev/null | grep -q "^---$"; then
-        value=$(sed -n '2,/^---$/p' "$file" 2>/dev/null | \
-            grep -i -m1 "^${field}:" | \
-            sed -E "s/^${field}:[[:space:]]*//i" || true)
-    fi
-
-    echo "$value"
-}
-
-# Start YAML output
-echo "# Continue-Feature Cross-Phase Discovery"
-echo "# Generated: $(date -Iseconds)"
-echo ""
-
-#
-# Collect all unique topic names from discussion + specification
-#
-declare -a all_topics=()
-declare -A topic_seen=()
-
-# Scan discussions
-if [ -d "$DISC_DIR" ]; then
-    for file in "$DISC_DIR"/*.md; do
-        [ -f "$file" ] || continue
-        name=$(basename "$file" .md)
-        if [ -z "${topic_seen[$name]+x}" ]; then
-            all_topics+=("$name")
-            topic_seen[$name]=1
-        fi
-    done
-fi
-
-# Scan specifications
-if [ -d "$SPEC_DIR" ]; then
-    for dir in "$SPEC_DIR"/*/; do
-        [ -d "$dir" ] || continue
-        [ -f "${dir}specification.md" ] || continue
-        name=$(basename "$dir")
-        if [ -z "${topic_seen[$name]+x}" ]; then
-            all_topics+=("$name")
-            topic_seen[$name]=1
-        fi
-    done
-fi
-
-#
-# Build topic entries
-#
-echo "topics:"
-
-topic_count=0
-actionable_count=0
-
-if [ ${#all_topics[@]} -eq 0 ]; then
-    echo "  []"
-else
-    for topic in "${all_topics[@]}"; do
-        # Discussion state
-        disc_exists="false"
-        disc_status=""
-        disc_file="$DISC_DIR/${topic}.md"
-        if [ -f "$disc_file" ]; then
-            disc_exists="true"
-            disc_status=$(extract_field "$disc_file" "status")
-            disc_status=${disc_status:-"in-progress"}
-        fi
-
-        # Specification state
-        spec_exists="false"
-        spec_status=""
-        spec_type=""
-        spec_file="$SPEC_DIR/${topic}/specification.md"
-        if [ -f "$spec_file" ]; then
-            spec_exists="true"
-            spec_status=$(extract_field "$spec_file" "status")
-            spec_status=${spec_status:-"in-progress"}
-            spec_type=$(extract_field "$spec_file" "type")
-            spec_type=${spec_type:-"feature"}
-        fi
-
-        # Skip cross-cutting specs — they aren't features
-        if [ "$spec_type" = "cross-cutting" ]; then
-            continue
-        fi
-
-        # Plan state
-        plan_exists="false"
-        plan_status=""
-        plan_format=""
-        plan_file="$PLAN_DIR/${topic}/plan.md"
-        if [ -f "$plan_file" ]; then
-            plan_exists="true"
-            plan_status=$(extract_field "$plan_file" "status")
-            plan_status=${plan_status:-"in-progress"}
-            plan_format=$(extract_field "$plan_file" "format")
-            plan_format=${plan_format:-"unknown"}
-        fi
-
-        # Implementation state
-        impl_exists="false"
-        impl_status=""
-        impl_file="$IMPL_DIR/${topic}/tracking.md"
-        if [ -f "$impl_file" ]; then
-            impl_exists="true"
-            impl_status=$(extract_field "$impl_file" "status")
-            impl_status=${impl_status:-"in-progress"}
-        fi
-
-        # Review state
-        review_exists="false"
-        if [ -d "$REVIEW_DIR/${topic}" ]; then
-            for rdir in "$REVIEW_DIR/${topic}"/r*/; do
-                [ -d "$rdir" ] || continue
-                [ -f "${rdir}review.md" ] || continue
-                review_exists="true"
-                break
-            done
-        fi
-
-        #
-        # Compute next_phase (check from top down, first match wins)
-        #
-        next_phase=""
-
-        if [ "$impl_exists" = "true" ] && [ "$impl_status" = "completed" ] && [ "$review_exists" = "true" ]; then
-            next_phase="done"
-        elif [ "$impl_exists" = "true" ] && [ "$impl_status" = "completed" ] && [ "$review_exists" = "false" ]; then
-            next_phase="review"
-        elif [ "$impl_exists" = "true" ] && [ "$impl_status" = "in-progress" ]; then
-            next_phase="implementation"
-        elif [ "$plan_exists" = "true" ] && [ "$plan_status" = "concluded" ]; then
-            next_phase="implementation"
-        elif [ "$plan_exists" = "true" ] && [ "$plan_status" != "concluded" ]; then
-            next_phase="planning"
-        elif [ "$spec_exists" = "true" ] && [ "$spec_status" = "concluded" ]; then
-            next_phase="planning"
-        elif [ "$spec_exists" = "true" ] && [ "$spec_status" != "concluded" ]; then
-            next_phase="specification"
-        elif [ "$disc_exists" = "true" ] && [ "$disc_status" = "concluded" ]; then
-            next_phase="specification"
-        elif [ "$disc_exists" = "true" ]; then
-            next_phase="discussion"
-        else
-            next_phase="unknown"
-        fi
-
-        # Actionable = can continue in the pipeline (not done, not unknown)
-        actionable="false"
-        if [ "$next_phase" != "done" ] && [ "$next_phase" != "unknown" ]; then
-            actionable="true"
-            actionable_count=$((actionable_count + 1))
-        fi
-
-        echo "  - name: \"$topic\""
-
-        echo "    discussion:"
-        echo "      exists: $disc_exists"
-        if [ "$disc_exists" = "true" ]; then
-            echo "      status: \"$disc_status\""
-        fi
-
-        echo "    specification:"
-        echo "      exists: $spec_exists"
-        if [ "$spec_exists" = "true" ]; then
-            echo "      status: \"$spec_status\""
-        fi
-
-        echo "    plan:"
-        echo "      exists: $plan_exists"
-        if [ "$plan_exists" = "true" ]; then
-            echo "      status: \"$plan_status\""
-            echo "      format: \"$plan_format\""
-        fi
-
-        echo "    implementation:"
-        echo "      exists: $impl_exists"
-        if [ "$impl_exists" = "true" ]; then
-            echo "      status: \"$impl_status\""
-        fi
-
-        echo "    review:"
-        echo "      exists: $review_exists"
-
-        echo "    next_phase: \"$next_phase\""
-        echo "    actionable: $actionable"
-
-        topic_count=$((topic_count + 1))
-    done
-fi
-
-echo ""
-
-#
-# STATE SUMMARY
-#
-echo "state:"
-echo "  topic_count: $topic_count"
-echo "  actionable_count: $actionable_count"
-
-if [ "$topic_count" -eq 0 ]; then
-    echo "  scenario: \"no_topics\""
-elif [ "$topic_count" -eq 1 ]; then
-    echo "  scenario: \"single_topic\""
-else
-    echo "  scenario: \"multiple_topics\""
-fi

package/skills/start-feature/references/phase-bridge.md

@@ -1,37 +0,0 @@
-# Phase Bridge
-
-*Reference for **[start-feature](../SKILL.md)***
-
----
-
-The phase bridge clears context between the discussion phase and the rest of the pipeline. This is necessary because discussion can consume significant context, and starting fresh prevents degradation.
-
-## Enter Plan Mode
-
-Enter plan mode and write the following plan:
-
-```
-# Continue Feature: {topic}
-
-The discussion for "{topic}" has concluded. The next session should
-continue the feature pipeline from specification onwards.
-
-## Instructions
-
-1. Invoke the `/continue-feature` skill for topic "{topic}"
-2. The skill will detect that a concluded discussion exists and route to specification
-
-## Context
-
-- Topic: {topic}
-- Completed phase: discussion
-- Expected next phase: specification
-- Discussion: .workflows/discussion/{topic}.md
-
-## How to proceed
-
-Clear context and continue. Claude will invoke continue-feature
-with the topic above and route to the specification phase automatically.
-```
-
-Exit plan mode. The user will approve and clear context, and the fresh session will pick up with continue-feature routing to specification.