@leeovery/claude-technical-workflows 2.1.42 → 2.2.1

package/skills/begin-implementation/SKILL.md

@@ -1,162 +0,0 @@
----
-name: begin-implementation
-description: "Bridge skill for the feature pipeline. Runs pre-flight checks for implementation and invokes the technical-implementation skill. Called by continue-feature — not directly by users."
-user-invocable: false
-allowed-tools: Bash(.claude/skills/start-implementation/scripts/discovery.sh)
----
-
-Invoke the **technical-implementation** skill for this conversation with pre-flight context.
-
-> **⚠️ 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
-
-Follow these steps EXACTLY as written. Do not skip steps or combine them.
-
-This skill is a **bridge** — it runs pre-flight checks for implementation and hands off to the processing skill. The topic has already been selected by the caller.
-
-**CRITICAL**: This guidance is mandatory.
-
-- After each user interaction, STOP and wait for their response before proceeding
-- Never assume or anticipate user choices
-- Complete each step fully before moving to the next
-
----
-
-## Step 1: Run Discovery
-
-!`.claude/skills/start-implementation/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/start-implementation/scripts/discovery.sh
-```
-
-If YAML content is already displayed, it has been run on your behalf.
-
-Parse the output to find the plan matching the provided topic. Extract:
-
-- **Plan details**: status, format, plan_id, specification, specification_exists
-- **External dependencies**: external_deps, has_unresolved_deps
-- **Dependency resolution**: deps_satisfied, deps_blocking
-- **Implementation tracking**: from `implementation.files` matching the topic
-- **Environment**: setup_file_exists, requires_setup
-
-If the plan is missing or not concluded, this is an error — report it and stop.
-
-→ Proceed to **Step 2**.
-
----
-
-## Step 2: Check External Dependencies
-
-Check the plan's `external_deps` and `dependency_resolution` from the discovery output.
-
-#### If all deps satisfied (or no deps)
-
-> *Output the next fenced block as a code block:*
-
-```
-External dependencies satisfied.
-```
-
-→ Proceed to **Step 3**.
-
-#### If any deps are blocking
-
-> *Output the next fenced block as a code block:*
-
-```
-Missing Dependencies
-
-Unresolved (not yet planned):
-  • {topic}: {description}
-    No plan exists. Create with /start-planning or mark as
-    satisfied externally.
-
-Incomplete (planned but not implemented):
-  • {topic}: {plan}:{task-id} not yet completed
-    This task must be completed first.
-```
-
-> *Output the next fenced block as markdown (not a code block):*
-
-```
-· · · · · · · · · · · ·
-- **`i`/`implement`** — Implement the blocking dependencies first
-- **`s`/`satisfied`** — Mark a dependency as satisfied externally
-- **`c`/`continue`** — Continue anyway (at your own risk)
-· · · · · · · · · · · ·
-```
-
-**STOP.** Wait for user response.
-
-If the user chooses `implement`, end here — suggest running `/start-implementation` for the blocking topic. If `satisfied`, update the plan frontmatter (`state: satisfied_externally`) and continue. If `continue`, proceed.
-
-→ Proceed to **Step 3**.
-
----
-
-## Step 3: Check Environment Setup
-
-Use the `environment` section from the discovery output:
-
-**If `setup_file_exists: true` and `requires_setup: false`:**
-
-> *Output the next fenced block as a code block:*
-
-```
-Environment: No special setup required.
-```
-
-→ Proceed to **Step 4**.
-
-**If `setup_file_exists: true` and `requires_setup: true`:**
-
-> *Output the next fenced block as a code block:*
-
-```
-Environment setup file found: .workflows/environment-setup.md
-```
-
-→ Proceed to **Step 4**.
-
-**If `setup_file_exists: false` or `requires_setup: unknown`:**
-
-> *Output the next fenced block as a code block:*
-
-```
-Are there any environment setup instructions I should follow before implementation?
-(Or "none" if no special setup is needed)
-```
-
-**STOP.** Wait for user response.
-
-- If the user provides instructions, save them to `.workflows/environment-setup.md`, commit
-- If the user says no/none, create `.workflows/environment-setup.md` with "No special setup required." and commit
-
-→ Proceed to **Step 4**.
-
----
-
-## Step 4: Invoke the Skill
-
-Determine the implementation tracking state:
-- If a tracking file exists for this topic → use its status
-- If no tracking file → status is "not-started"
-
-Construct the handoff and invoke the [technical-implementation](../technical-implementation/SKILL.md) skill:
-
-```
-Implementation session for: {topic}
-Plan: .workflows/planning/{topic}/plan.md
-Format: {format}
-Plan ID: {plan_id} (if applicable)
-Specification: .workflows/specification/{topic}/specification.md (exists: {true|false})
-Implementation tracking: {exists | new} (status: {status})
-Dependencies: {All satisfied | notes}
-Environment: {Setup required | No special setup required}
-
-Invoke the technical-implementation skill.
-```

package/skills/begin-planning/SKILL.md

@@ -1,92 +0,0 @@
----
-name: begin-planning
-description: "Bridge skill for the feature pipeline. Runs pre-flight checks for planning and invokes the technical-planning skill. Called by continue-feature — not directly by users."
-user-invocable: false
-allowed-tools: Bash(.claude/skills/start-planning/scripts/discovery.sh)
----
-
-Invoke the **technical-planning** skill for this conversation with pre-flight context.
-
-> **⚠️ 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
-
-Follow these steps EXACTLY as written. Do not skip steps or combine them.
-
-This skill is a **bridge** — it runs pre-flight checks for planning and hands off to the processing skill. The topic has already been selected by the caller.
-
-**CRITICAL**: This guidance is mandatory.
-
-- After each user interaction, STOP and wait for their response before proceeding
-- Never assume or anticipate user choices
-- Complete each step fully before moving to the next
-
----
-
-## Step 1: Run Discovery
-
-!`.claude/skills/start-planning/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/start-planning/scripts/discovery.sh
-```
-
-If YAML content is already displayed, it has been run on your behalf.
-
-Parse the output to extract:
-
-- **Cross-cutting specifications** from `specifications.crosscutting` (name, status)
-- **Common format** from `plans.common_format`
-
-The topic was provided by the caller. Confirm the specification exists and is concluded:
-
-- Check `specifications.feature` for the topic
-- If the spec is missing or not concluded, this is an error — report it and stop
-
-→ Proceed to **Step 2**.
-
----
-
-## Step 2: Handle Cross-Cutting Context
-
-Load **[cross-cutting-context.md](../start-planning/references/cross-cutting-context.md)** and follow its instructions as written.
-
-→ Proceed to **Step 3**.
-
----
-
-## Step 3: Gather Additional Context
-
-> *Output the next fenced block as markdown (not a code block):*
-
-```
-· · · · · · · · · · · ·
-Any additional context for planning?
-
-- **`c`/`continue`** — Continue with the specification as-is
-- Or provide additional context (priorities, constraints, new considerations)
-· · · · · · · · · · · ·
-```
-
-**STOP.** Wait for user response.
-
-→ Proceed to **Step 4**.
-
----
-
-## Step 4: Invoke the Skill
-
-Construct the handoff and invoke the [technical-planning](../technical-planning/SKILL.md) skill:
-
-```
-Planning session for: {topic}
-Specification: .workflows/specification/{topic}/specification.md
-Work type: feature
-Additional context: {summary of user's answer from Step 3, or "none"}
-Cross-cutting references: {list of applicable cross-cutting specs with brief summaries, or "none"}
-Recommended output format: {common_format from discovery if non-empty, otherwise "none"}
-
-Invoke the technical-planning skill.
-```

package/skills/begin-review/SKILL.md

@@ -1,90 +0,0 @@
----
-name: begin-review
-description: "Bridge skill for the feature pipeline. Runs pre-flight checks for review and invokes the technical-review skill. Called by continue-feature — not directly by users."
-user-invocable: false
-allowed-tools: Bash(.claude/skills/start-review/scripts/discovery.sh)
----
-
-Invoke the **technical-review** skill for this conversation with pre-flight context.
-
-> **⚠️ 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
-
-Follow these steps EXACTLY as written. Do not skip steps or combine them.
-
-This skill is a **bridge** — it runs pre-flight checks for review and hands off to the processing skill. The topic has already been selected by the caller.
-
-**CRITICAL**: This guidance is mandatory.
-
-- After each user interaction, STOP and wait for their response before proceeding
-- Never assume or anticipate user choices
-- Complete each step fully before moving to the next
-
----
-
-## Step 1: Run Discovery
-
-!`.claude/skills/start-review/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/start-review/scripts/discovery.sh
-```
-
-If YAML content is already displayed, it has been run on your behalf.
-
-Parse the output to find the plan matching the provided topic. Extract:
-
-- **Plan details**: status, format, plan_id, specification, specification_exists
-- **Implementation status**: implementation_status
-- **Review state**: review_count, latest_review_version
-
-If the plan is missing, this is an error — report it and stop.
-
-If `implementation_status` is `"none"`, this is an error:
-
-> *Output the next fenced block as a code block:*
-
-```
-Review Pre-Flight Failed
-
-"{topic:(titlecase)}" has no implementation to review.
-
-Implementation must be completed or in-progress before review.
-```
-
-**STOP.** Do not proceed — terminal condition.
-
-→ Proceed to **Step 2**.
-
----
-
-## Step 2: Determine Review Version
-
-Check the topic's review state from discovery output:
-
-- If `review_count` is 0 → review version is `r1`
-- If `review_count` > 0 → review version is `r{latest_review_version + 1}`
-
-→ Proceed to **Step 3**.
-
----
-
-## Step 3: Invoke the Skill
-
-Construct the handoff and invoke the [technical-review](../technical-review/SKILL.md) skill:
-
-```
-Review session
-Plans to review:
-  - topic: {topic}
-    plan: .workflows/planning/{topic}/plan.md
-    format: {format}
-    plan_id: {plan_id} (if applicable)
-    specification: {specification} (exists: {true|false})
-    review_version: r{N}
-
-Invoke the technical-review skill.
-```

package/skills/continue-feature/SKILL.md

@@ -1,186 +0,0 @@
----
-name: continue-feature
-description: "Continue a feature through the pipeline. Routes to the next phase (specification, planning, or implementation) based on artifact state. Can be invoked manually or from plan mode bridges."
-allowed-tools: Bash(.claude/skills/continue-feature/scripts/discovery.sh), Bash(.claude/hooks/workflows/write-session-state.sh), Bash(.claude/skills/start-review/scripts/discovery.sh)
-hooks:
-  PreToolUse:
-    - hooks:
-        - type: command
-          command: "$CLAUDE_PROJECT_DIR/.claude/hooks/workflows/system-check.sh"
-          once: true
----
-
-Route a feature to its next pipeline phase.
-
-> **⚠️ 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
-
-Follow these steps EXACTLY as written. Do not skip steps or combine them.
-
-**CRITICAL**: This guidance is mandatory.
-
-- After each user interaction, STOP and wait for their response before proceeding
-- Never assume or anticipate user choices
-- Complete each step fully before moving to the next
-
----
-
-## Resuming After Context Refresh
-
-Context refresh (compaction) summarizes the conversation, losing procedural detail. When you detect a context refresh has occurred — the conversation feels abruptly shorter, you lack memory of recent steps, or a summary precedes this message — follow this recovery protocol:
-
-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. **Identify the topic.** Check conversation history for the topic name. If unknown, ask the user.
-3. **Determine current step from artifacts** (check top-down, first match wins):
-   - Review exists for topic → resume at **Step 7** (phase bridge — pipeline complete)
-   - Implementation tracking exists with `status: completed`, no review → resume at **Step 6** (invoke begin-review)
-   - Implementation tracking exists with `status: in-progress` → resume at **Step 5** (re-invoke begin-implementation)
-   - Plan exists with `status: concluded` → resume at **Step 5** (invoke begin-implementation)
-   - Plan exists with other status → resume at **Step 4** (re-invoke begin-planning)
-   - Specification exists with `status: concluded` → resume at **Step 4** (invoke begin-planning)
-   - Specification exists with other status → resume at **Step 3** (re-invoke technical-specification)
-   - Discussion exists with `status: concluded` → resume at **Step 3** (invoke technical-specification)
-   - Discussion exists with other status → terminal — suggest `/start-discussion`
-4. **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.
-
-Do not guess at progress or continue from memory. The files on disk and git history are authoritative — your recollection is not.
-
----
-
-## Step 0: Run Migrations
-
-**This step is mandatory. You must complete it before proceeding.**
-
-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. Do not continue automatically.
-
-**If no updates needed**: Proceed to Step 1.
-
----
-
-## Step 1: Determine Topic
-
-Check whether a topic was provided by the caller (e.g., from a plan mode bridge: "invoke continue-feature for {topic}").
-
-#### If topic was provided
-
-Use the provided topic directly.
-
-→ Proceed to **Step 2**.
-
-#### If no topic provided (bare invocation)
-
-Run the discovery script to gather current state:
-
-```bash
-.claude/skills/continue-feature/scripts/discovery.sh
-```
-
-Parse the output to understand:
-
-**From `topics` array:** Each topic's name, discussion/specification/plan/implementation state, next_phase, and actionable flag.
-
-**From `state` section:** topic_count, actionable_count, scenario.
-
-**IMPORTANT**: Use ONLY this script for discovery. Do NOT run additional bash commands (ls, head, cat, etc.) to gather state.
-
-#### If scenario is "no_topics"
-
-> *Output the next fenced block as a code block:*
-
-```
-Continue Feature
-
-No workflow topics found.
-
-Start a new feature with /start-feature.
-```
-
-**STOP.** Do not proceed — terminal condition.
-
-#### If topics exist
-
-Present the discovered state as context, then ask the user to select:
-
-> *Output the next fenced block as a code block:*
-
-```
-Continue Feature
-
-This skill continues a feature through the pipeline phases:
-Discussion → Specification → Planning → Implementation → Review
-
-It's designed for features started with /start-feature, but works
-with any topic that has workflow artifacts.
-
-Topics found:
-
-1. {topic:(titlecase)}
-   └─ Next: {next_phase}
-
-2. ...
-```
-
-> *Output the next fenced block as markdown (not a code block):*
-
-```
-· · · · · · · · · · · ·
-Which topic would you like to continue?
-
-Select by number, or enter a topic name directly:
-· · · · · · · · · · · ·
-```
-
-**STOP.** Wait for user response.
-
-→ Proceed to **Step 2**.
-
----
-
-## Step 2: Detect Phase and Route
-
-Load **[detect-phase.md](references/detect-phase.md)** and follow its instructions.
-
-→ The reference file will route you to **Step 3**, **Step 4**, **Step 5**, **Step 6**, or a terminal condition. Follow its routing.
-
----
-
-## Step 3: Specification Phase
-
-Load **[invoke-specification.md](references/invoke-specification.md)** and follow its instructions.
-
-**CRITICAL**: When the specification concludes (status becomes "concluded"), you MUST proceed to **Step 7** below. Do not end the session — the feature pipeline continues to the phase bridge.
-
----
-
-## Step 4: Planning Phase
-
-Load **[invoke-planning.md](references/invoke-planning.md)** and follow its instructions.
-
-**CRITICAL**: When the plan concludes (status becomes "concluded"), you MUST proceed to **Step 7** below. Do not end the session — the feature pipeline continues to the phase bridge.
-
----
-
-## Step 5: Implementation Phase
-
-Load **[invoke-implementation.md](references/invoke-implementation.md)** and follow its instructions.
-
-**CRITICAL**: When implementation completes (tracking status becomes "completed"), you MUST proceed to **Step 7** below. Do not end the session — the feature pipeline continues to the phase bridge.
-
----
-
-## Step 6: Review Phase
-
-Load **[invoke-review.md](references/invoke-review.md)** and follow its instructions.
-
-**CRITICAL**: When review concludes, you MUST proceed to **Step 7** below. Do not end the session — the feature pipeline continues to the phase bridge.
-
----
-
-## Step 7: Phase Bridge
-
-Load **[phase-bridge.md](references/phase-bridge.md)** and follow its instructions.
-
-The bridge will enter plan mode with instructions to invoke continue-feature for the topic in the next session, or show a terminal message if the pipeline is complete.

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

@@ -1,99 +0,0 @@
-# Detect Phase
-
-*Reference for **[continue-feature](../SKILL.md)***
-
----
-
-Determine the next phase for the selected topic using its artifact state.
-
-## Phase Detection
-
-Either use the `next_phase` from discovery output (if discovery was run), or compute it by checking artifacts directly:
-
-### If discovery was not run (topic provided by caller)
-
-Check artifacts in this order (first match wins):
-
-1. Check `.workflows/review/{topic}/r*/review.md`
-   - If any review exists → next_phase is **"done"**
-
-2. Read `.workflows/implementation/{topic}/tracking.md`
-   - If exists with `status: completed` → next_phase is **"review"**
-   - If exists with `status: in-progress` → next_phase is **"implementation"**
-
-3. Read `.workflows/planning/{topic}/plan.md`
-   - If exists with `status: concluded` → next_phase is **"implementation"**
-   - If exists with other status → next_phase is **"planning"**
-
-4. Read `.workflows/specification/{topic}/specification.md`
-   - If exists with `status: concluded` → next_phase is **"planning"**
-   - If exists with other status → next_phase is **"specification"**
-
-5. Check `.workflows/discussion/{topic}.md`
-   - If exists with `status: concluded` → next_phase is **"specification"**
-   - If exists with other status → next_phase is **"discussion"**
-
-6. If none found → next_phase is **"unknown"**
-
-## Routing
-
-#### If next_phase is "specification"
-
-→ Proceed to **Step 3**.
-
-#### If next_phase is "planning"
-
-→ Proceed to **Step 4**.
-
-#### If next_phase is "implementation"
-
-→ Proceed to **Step 5**.
-
-#### If next_phase is "review"
-
-→ Proceed to **Step 6**.
-
-#### If next_phase is "done"
-
-> *Output the next fenced block as a code block:*
-
-```
-Pipeline Complete
-
-"{topic:(titlecase)}" has completed all pipeline phases
-(implementation and review).
-
-Use /start-review to re-review or synthesize findings.
-```
-
-**STOP.** Do not proceed — terminal condition.
-
-#### If next_phase is "discussion"
-
-> *Output the next fenced block as a code block:*
-
-```
-Discussion In Progress
-
-"{topic:(titlecase)}" has a discussion that is not yet concluded.
-
-Resume the discussion with /start-discussion, or use /start-feature
-to start a new feature from scratch.
-```
-
-**STOP.** Do not proceed — terminal condition.
-
-#### If next_phase is "unknown"
-
-> *Output the next fenced block as a code block:*
-
-```
-No Artifacts Found
-
-No workflow artifacts found for "{topic}".
-
-Start a new feature with /start-feature or begin a discussion
-with /start-discussion.
-```
-
-**STOP.** Do not proceed — terminal condition.

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

@@ -1,43 +0,0 @@
-# Invoke Implementation
-
-*Reference for **[continue-feature](../SKILL.md)***
-
----
-
-Invoke the begin-implementation 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-implementation/SKILL.md" \
-  ".workflows/implementation/{topic}/tracking.md" \
-  --pipeline "This session is part of the feature pipeline. After implementation completes, return to the continue-feature skill and execute Step 7 (Phase Bridge). Load: skills/continue-feature/references/phase-bridge.md"
-```
-
-## Handoff
-
-Invoke the [begin-implementation](../../begin-implementation/SKILL.md) skill:
-
-```
-Implementation pre-flight for: {topic}
-Plan: .workflows/planning/{topic}/plan.md
-
-PIPELINE CONTINUATION — When implementation completes (tracking status: completed),
-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 implementation — the feature pipeline continues.
-
-Invoke the begin-implementation skill.
-```
-
-The bridge skill handles dependency checking, environment setup, and the handoff to technical-implementation.