@leeovery/claude-technical-workflows 2.1.42 → 2.2.1

package/skills/workflow-start/references/bugfix-routing.md

@@ -0,0 +1,117 @@
+# Bugfix Routing
+
+*Reference for **[workflow-start](../SKILL.md)***
+
+---
+
+Bugfix work is investigation-centric. A topic flows through: Investigation → Specification → Planning → Implementation → Review. Investigation replaces discussion by combining symptom gathering + code analysis. This reference shows in-progress bugfixes and offers options to continue or start new.
+
+## Display Bugfix State
+
+Using the discovery output, check if there are any bugfixes in progress.
+
+#### If no bugfixes exist
+
+> *Output the next fenced block as a code block:*
+
+```
+Bugfixes
+
+No bugfixes in progress.
+```
+
+> *Output the next fenced block as markdown (not a code block):*
+
+```
+· · · · · · · · · · · ·
+Ready to start a new bugfix.
+
+- **`y`/`yes`** — Start a new bugfix
+- **`n`/`no`** — Go back to work type selection
+· · · · · · · · · · · ·
+```
+
+**STOP.** Wait for user response.
+
+#### If yes
+
+Invoke `start-bugfix`. It will set `work_type: bugfix` automatically.
+
+#### If no
+
+→ Return to **[the skill](../SKILL.md)** for **Step 2** (work type selection).
+
+#### If bugfixes exist
+
+> *Output the next fenced block as a code block:*
+
+```
+Bugfixes
+
+{bugfix_count} bugfix(es) in progress:
+
+1. {topic:(titlecase)}
+   └─ Next: {next_phase}
+
+2. ...
+```
+
+Build tree from `bugfixes.topics` array. Each topic shows `name` (titlecased) and `next_phase`.
+
+## Build Menu Options
+
+Build a numbered menu with all in-progress bugfixes plus option to start new. The description maps `next_phase`:
+
+| next_phase | Description |
+|------------|-------------|
+| investigation | investigation in-progress |
+| specification | ready for specification |
+| planning | ready for planning |
+| implementation | ready for implementation |
+| review | ready for review |
+| done | pipeline complete |
+
+> *Output the next fenced block as markdown (not a code block):*
+
+```
+· · · · · · · · · · · ·
+What would you like to do?
+
+1. Continue "Login Timeout" — investigation in-progress
+2. Continue "Memory Leak" — ready for specification
+3. Continue "Race Condition" — ready for planning
+4. Start new bugfix
+
+Select an option (enter number):
+· · · · · · · · · · · ·
+```
+
+Recreate with actual topics and states from discovery.
+
+**STOP.** Wait for user response.
+
+## Route Based on Selection
+
+Parse the user's selection, then follow the instructions below.
+
+#### If "start new bugfix"
+
+Invoke `/start-bugfix`. It will set `work_type: bugfix` and begin the investigation phase.
+
+#### If continuing existing bugfix
+
+Map `next_phase` to the appropriate skill:
+
+| next_phase | Skill | Work Type | Topic |
+|------------|-------|-----------|-------|
+| investigation | `/start-investigation` | bugfix | {topic} |
+| specification | `/start-specification` | bugfix | {topic} |
+| planning | `/start-planning` | bugfix | {topic} |
+| implementation | `/start-implementation` | bugfix | {topic} |
+| review | `/start-review` | bugfix | {topic} |
+
+Skills receive positional arguments: `$0` = work_type, `$1` = topic.
+
+**Example**: `/start-specification bugfix {topic}` — skill skips discovery, validates topic, proceeds to processing.
+
+Invoke the skill from the table with the work type and topic as positional arguments.

package/skills/workflow-start/references/feature-routing.md

@@ -0,0 +1,117 @@
+# Feature Routing
+
+*Reference for **[workflow-start](../SKILL.md)***
+
+---
+
+Feature development is topic-centric. A single topic flows through the pipeline: Discussion → Specification → Planning → Implementation → Review. This reference shows in-progress features and offers options to continue or start new.
+
+## Display Feature State
+
+Using the discovery output, check if there are any features in progress.
+
+#### If no features exist
+
+> *Output the next fenced block as a code block:*
+
+```
+Features
+
+No features in progress.
+```
+
+> *Output the next fenced block as markdown (not a code block):*
+
+```
+· · · · · · · · · · · ·
+Ready to start a new feature.
+
+- **`y`/`yes`** — Start a new feature
+- **`n`/`no`** — Go back to work type selection
+· · · · · · · · · · · ·
+```
+
+**STOP.** Wait for user response.
+
+#### If yes
+
+Invoke `start-feature`. It will set `work_type: feature` automatically.
+
+#### If no
+
+→ Return to **[the skill](../SKILL.md)** for **Step 2** (work type selection).
+
+#### If features exist
+
+> *Output the next fenced block as a code block:*
+
+```
+Features
+
+{feature_count} feature(s) in progress:
+
+1. {topic:(titlecase)}
+   └─ Next: {next_phase}
+
+2. ...
+```
+
+Build tree from `features.topics` array. Each topic shows `name` (titlecased) and `next_phase`.
+
+## Build Menu Options
+
+Build a numbered menu with all in-progress features plus option to start new. The description maps `next_phase`:
+
+| next_phase | Description |
+|------------|-------------|
+| discussion | discussion in-progress |
+| specification | ready for specification |
+| planning | ready for planning |
+| implementation | ready for implementation |
+| review | ready for review |
+| done | pipeline complete |
+
+> *Output the next fenced block as markdown (not a code block):*
+
+```
+· · · · · · · · · · · ·
+What would you like to do?
+
+1. Continue "Auth Flow" — discussion in-progress
+2. Continue "Caching" — ready for specification
+3. Continue "Notifications" — ready for planning
+4. Start new feature
+
+Select an option (enter number):
+· · · · · · · · · · · ·
+```
+
+Recreate with actual topics and states from discovery.
+
+**STOP.** Wait for user response.
+
+## Route Based on Selection
+
+Parse the user's selection, then follow the instructions below.
+
+#### If "start new feature"
+
+Invoke `/start-feature`. It will set `work_type: feature` automatically.
+
+#### If continuing existing feature
+
+Map `next_phase` to the appropriate skill:
+
+| next_phase | Skill | Work Type | Topic |
+|------------|-------|-----------|-------|
+| discussion | `/start-discussion` | feature | {topic} |
+| specification | `/start-specification` | feature | {topic} |
+| planning | `/start-planning` | feature | {topic} |
+| implementation | `/start-implementation` | feature | {topic} |
+| review | `/start-review` | feature | {topic} |
+
+Skills receive positional arguments: `$0` = work_type, `$1` = topic.
+
+**Example**: `/start-specification feature {topic}` — skill skips discovery, validates topic, proceeds to processing.
+
+Invoke the skill from the table with the work type and topic as positional arguments.

package/skills/workflow-start/references/greenfield-routing.md

@@ -0,0 +1,140 @@
+# Greenfield Routing
+
+*Reference for **[workflow-start](../SKILL.md)***
+
+---
+
+Greenfield development is phase-centric. All artifacts in a phase complete before moving to the next. This reference shows what's actionable in each phase and offers options to continue existing work or start new.
+
+## Display Greenfield State
+
+Using the discovery output, build the phase-centric view.
+
+> *Output the next fenced block as a code block:*
+
+```
+Greenfield Overview
+
+Research:
+@if(research_count > 0)
+  @foreach(file in research.files)
+  └─ {file}
+  @endforeach
+@else
+  (none)
+@endif
+
+Discussions:
+@if(greenfield.discussions.count > 0)
+  @foreach(disc in greenfield.discussions.files)
+  └─ {disc.name:(titlecase)} ({disc.status})
+  @endforeach
+@else
+  (none)
+@endif
+
+Specifications:
+@if(greenfield.specifications.count > 0)
+  @foreach(spec in greenfield.specifications.files)
+  └─ {spec.name:(titlecase)}
+     └─ Spec: {spec.status} ({spec.type})
+  @endforeach
+@else
+  (none)
+@endif
+
+Plans:
+@if(greenfield.plans.count > 0)
+  @foreach(plan in greenfield.plans.files)
+  └─ {plan.name:(titlecase)}
+     └─ Plan: {plan.status}
+  @endforeach
+@else
+  (none)
+@endif
+
+Implementation:
+@if(greenfield.implementation.count > 0)
+  @foreach(impl in greenfield.implementation.files)
+  └─ {impl.topic:(titlecase)}
+     └─ Implementation: {impl.status}
+  @endforeach
+@else
+  (none)
+@endif
+```
+
+## Build Menu Options
+
+Build a numbered menu of actionable items. The verb depends on the state:
+
+| State | Verb |
+|-------|------|
+| In-progress discussion | Continue |
+| In-progress specification | Continue |
+| Concluded spec (feature), no plan | Start planning for |
+| In-progress plan | Continue |
+| Concluded plan, no implementation | Start implementation of |
+| In-progress implementation | Continue |
+| Completed implementation, no review | Start review for |
+| Research exists | Continue research |
+| No discussions yet | Start research / Start new discussion |
+
+**Specification phase is different in greenfield**: Don't offer "Start specification from {topic}". Instead, when concluded discussions exist, offer "Start specification" which invokes `/start-specification`. The specification skill will analyze ALL concluded discussions and suggest groupings — multiple discussions may become one spec, or split differently.
+
+**Specification readiness:**
+- All discussions concluded → "Start specification" (recommended)
+- Some discussions still in-progress → "Start specification" with note: "(some discussions still in-progress)"
+
+Always include "Start new discussion" as a final option.
+
+> *Output the next fenced block as markdown (not a code block):*
+
+```
+· · · · · · · · · · · ·
+What would you like to do?
+
+1. Continue "Auth Flow" discussion — in-progress
+2. Continue "Data Model" specification — in-progress
+3. Start planning for "User Profiles" — spec concluded
+4. Continue "Caching" plan — in-progress
+5. Start implementation of "Notifications" — plan concluded
+6. Start specification — 3 discussions concluded (recommended)
+7. Continue research
+8. Start new discussion
+
+Select an option (enter number):
+· · · · · · · · · · · ·
+```
+
+Recreate with actual topics and states from discovery. Only include options that apply based on current state.
+
+**STOP.** Wait for user response.
+
+## Route Based on Selection
+
+Parse the user's selection, then follow the instructions below the table to invoke the appropriate skill.
+
+| Selection | Skill | Work Type | Topic |
+|-----------|-------|-----------|-------|
+| Continue discussion | `/start-discussion` | greenfield | {topic} |
+| Continue specification | `/start-specification` | greenfield | — |
+| Continue plan | `/start-planning` | greenfield | {topic} |
+| Continue implementation | `/start-implementation` | greenfield | {topic} |
+| Continue research | `/start-research` | greenfield | — |
+| Start specification | `/start-specification` | greenfield | — |
+| Start planning | `/start-planning` | greenfield | {topic} |
+| Start implementation | `/start-implementation` | greenfield | {topic} |
+| Start review | `/start-review` | greenfield | {topic} |
+| Start research | `/start-research` | greenfield | — |
+| Start new discussion | `/start-discussion` | greenfield | — |
+
+Skills receive positional arguments: `$0` = work_type, `$1` = topic.
+
+**With arguments** (bridge mode): `/start-discussion greenfield {topic}` — skill skips discovery, validates topic, proceeds to processing.
+
+**Without arguments** (discovery mode): `/start-discussion greenfield` — skill runs discovery with work_type context.
+
+**Note on specification**: Unlike feature/bugfix pipelines, greenfield specification is NOT topic-centric. Don't pass a topic. Always route through discovery mode so analysis can detect changed discussions.
+
+Invoke the skill from the table with the topic and work type as positional arguments. If no topic or work type is shown, invoke the skill bare.

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

@@ -0,0 +1,83 @@
+# Work Type Selection
+
+*Reference for **[workflow-start](../SKILL.md)***
+
+---
+
+Present the current state and ask the user which work type they want to work on.
+
+## Display State Overview
+
+Using the discovery output, render the appropriate state display.
+
+#### If `state.has_any_work` is false
+
+> *Output the next fenced block as a code block:*
+
+```
+Workflow Overview
+
+No existing work found. Ready to start fresh.
+```
+
+#### If `state.has_any_work` is true
+
+Build the summary from `state` counts. Only show sections with work.
+
+> *Output the next fenced block as a code block:*
+
+```
+Workflow Overview
+
+@if(state.greenfield has any counts > 0)
+Greenfield:
+  @if(research_count > 0)└─ Research: {research_count} @if(research_count == 1)file@else files@endif
+  @endif
+  @if(discussion_count > 0)└─ Discussions: {discussion_count} @if(discussion_concluded > 0)({discussion_concluded} concluded)@endif
+  @endif
+  @if(specification_count > 0)└─ Specifications: {specification_count} @if(specification_concluded > 0)({specification_concluded} concluded)@endif
+  @endif
+  @if(plan_count > 0)└─ Plans: {plan_count} @if(plan_concluded > 0)({plan_concluded} concluded)@endif
+  @endif
+  @if(implementation_count > 0)└─ Implementations: {implementation_count} @if(implementation_completed > 0)({implementation_completed} completed)@endif
+  @endif
+@endif
+
+@if(feature_count > 0)
+Features: {feature_count} in progress
+@endif
+
+@if(bugfix_count > 0)
+Bugfixes: {bugfix_count} in progress
+@endif
+```
+
+Use values from `state.greenfield.*`, `state.feature_count`, `state.bugfix_count`.
+
+## Ask Work Type
+
+> *Output the next fenced block as markdown (not a code block):*
+
+```
+· · · · · · · · · · · ·
+What would you like to work on?
+
+1. **Build the product** — Greenfield development (phase-centric, multi-session)
+2. **Add a feature** — Feature work (topic-centric, linear pipeline)
+3. **Fix a bug** — Bugfix (investigation-centric, focused pipeline)
+· · · · · · · · · · · ·
+```
+
+**STOP.** Wait for user response.
+
+## Process Selection
+
+Map the user's response to a work type:
+
+- "1", "build", "greenfield", "product" → work type is **greenfield**
+- "2", "feature", "add" → work type is **feature**
+- "3", "bug", "fix", "bugfix" → work type is **bugfix**
+
+If the response doesn't map clearly, ask for clarification.
+
+→ Return to **[the skill](../SKILL.md)** with the selected work type.