@leeovery/claude-technical-workflows 2.1.17 → 2.1.19

package/package.json

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

package/skills/link-dependencies/SKILL.md

@@ -161,11 +161,11 @@ UPDATED FILES:
 If any files were updated:
 
 ```
-· · ·
-
+· · · · · · · · · · · ·
 Shall I commit these dependency updates?
 - **`y`/`yes`** — Commit the changes
 - **`n`/`no`** — Skip
+· · · · · · · · · · · ·
 ```
 
 If yes, commit with message:

package/skills/start-discussion/SKILL.md

@@ -228,35 +228,35 @@ Discussions:
 
 **If research AND discussions exist:**
 ```
-· · ·
-
+· · · · · · · · · · · ·
 How would you like to proceed?
 
 - **`r`/`refresh`** — Force fresh research analysis
 - From research — pick a topic number above (e.g., "1" or "research 1")
 - Continue discussion — name one above (e.g., "continue {topic}")
 - Fresh topic — describe what you want to discuss
+· · · · · · · · · · · ·
 ```
 
 **If ONLY research exists:**
 ```
-· · ·
-
+· · · · · · · · · · · ·
 How would you like to proceed?
 
 - **`r`/`refresh`** — Force fresh research analysis
 - From research — pick a topic number above (e.g., "1" or "research 1")
 - Fresh topic — describe what you want to discuss
+· · · · · · · · · · · ·
 ```
 
 **If ONLY discussions exist:**
 ```
-· · ·
-
+· · · · · · · · · · · ·
 How would you like to proceed?
 
 - Continue discussion — name one above (e.g., "continue {topic}")
 - Fresh topic — describe what you want to discuss
+· · · · · · · · · · · ·
 ```
 
 **STOP.** Wait for user response before proceeding.

package/skills/start-implementation/SKILL.md

@@ -210,8 +210,7 @@ Then re-run /start-implementation.
 
 **Otherwise (multiple selectable plans, or implemented plans exist):**
 ```
-· · ·
-
+· · · · · · · · · · · ·
 Select a plan (enter number):
 ```
 
@@ -260,11 +259,11 @@ INCOMPLETE (planned but not implemented):
 - {topic}: task {task_id} not yet completed
   -> This task must be completed first.
 
-· · ·
-
+· · · · · · · · · · · ·
 - **`i`/`implement`** — Implement the blocking dependencies first
 - **`l`/`link`** — Run /link-dependencies to wire up recently completed plans
 - Mark as "satisfied externally" — tell me which dependency was implemented outside this workflow
+· · · · · · · · · · · ·
 ```
 
 **STOP.** Wait for user response.

package/skills/start-planning/SKILL.md

@@ -155,8 +155,7 @@ Omit either section entirely if it has no entries.
 
 **If multiple actionable items:**
 ```
-· · ·
-
+· · · · · · · · · · · ·
 Select a specification (enter number):
 ```
 
@@ -232,10 +231,10 @@ Note: The following cross-cutting specifications are still in-progress:
 
 These may contain architectural decisions relevant to this plan.
 
-· · ·
-
+· · · · · · · · · · · ·
 - **`c`/`continue`** — Plan without them
 - **`s`/`stop`** — Complete them first (/start-specification)
+· · · · · · · · · · · ·
 ```
 
 **STOP.** Wait for user response.

package/skills/start-research/SKILL.md

@@ -10,14 +10,14 @@ Invoke the **technical-research** skill for this conversation.
 
 This is **Phase 1** of the six-phase workflow:
 
-| Phase | Focus | You |
-|-------|-------|-----|
-| **1. Research** | EXPLORE - ideas, feasibility, market, business | ◀ HERE |
-| 2. Discussion | WHAT and WHY - decisions, architecture, edge cases | |
-| 3. Specification | REFINE - validate into standalone spec | |
-| 4. Planning | HOW - phases, tasks, acceptance criteria | |
-| 5. Implementation | DOING - tests first, then code | |
-| 6. Review | VALIDATING - check work against artifacts | |
+| Phase             | Focus                                              | You    |
+|-------------------|----------------------------------------------------|--------|
+| **1. Research**   | EXPLORE - ideas, feasibility, market, business     | ◀ HERE |
+| 2. Discussion     | WHAT and WHY - decisions, architecture, edge cases |        |
+| 3. Specification  | REFINE - validate into standalone spec             |        |
+| 4. Planning       | HOW - phases, tasks, acceptance criteria           |        |
+| 5. Implementation | DOING - tests first, then code                     |        |
+| 6. Review         | VALIDATING - check work against artifacts          |        |
 
 **Stay in your lane**: Explore freely. This is the time for broad thinking, feasibility checks, and learning. Surface options and tradeoffs — don't make decisions. When a topic converges toward a conclusion, that's a signal it's ready for discussion phase, not a cue to start deciding. Park it and move on.
 
@@ -43,95 +43,20 @@ Follow these steps EXACTLY as written. Do not skip steps or combine them. Presen
 
 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 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.
 
 **If no updates needed**: Proceed to Step 1.
 
 ---
 
-## Step 1: Get the Seed Idea
+## Step 1: Gather Context
 
-Ask:
-
-```
-What's on your mind?
-
-- What idea or topic do you want to explore?
-- What prompted this - a problem, opportunity, curiosity?
-```
-
-**STOP.** Wait for user response before proceeding.
+Load **[gather-context.md](references/gather-context.md)** and follow its instructions as written.
 
 → Proceed to **Step 2**.
 
 ---
 
-## Step 2: Understand Current Knowledge
-
-Ask:
-
-```
-What do you already know?
-
-- Any initial thoughts or research you've done?
-- Constraints or context I should be aware of?
-```
-
-**STOP.** Wait for user response before proceeding.
-
-→ Proceed to **Step 3**.
-
----
-
-## Step 3: Determine Starting Point
-
-Ask:
-
-```
-Where should we start?
-
-- Technical feasibility? Market landscape? Business model?
-- Or just talk it through and see where it goes?
-```
-
-**STOP.** Wait for user response before proceeding.
-
-→ Proceed to **Step 4**.
-
----
-
-## Step 4: Gather Final Context
-
-Ask:
-
-```
-Any constraints or context I should know about upfront?
-
-(Or "none" if we're starting fresh)
-```
-
-**STOP.** Wait for user response before proceeding.
-
-→ Proceed to **Step 5**.
-
----
-
-## Step 5: Invoke the Skill
-
-After completing the steps above, this skill's purpose is fulfilled.
-
-Invoke the [technical-research](../technical-research/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
-
-**Example handoff:**
-```
-Research session for: {topic}
-Output: docs/workflow/research/exploration.md
-
-Context:
-- Prompted by: {problem, opportunity, or curiosity}
-- Already knows: {any initial thoughts or research, or "starting fresh"}
-- Starting point: {technical feasibility, market, business model, or "open exploration"}
-- Constraints: {any constraints mentioned, or "none"}
+## Step 2: Invoke the Skill
 
-Invoke the technical-research skill.
-```
+Load **[invoke-skill.md](references/invoke-skill.md)** and follow its instructions as written.

package/skills/start-research/references/gather-context.md

@@ -0,0 +1,68 @@
+# Gather Context
+
+*Reference for **[start-research](../SKILL.md)***
+
+---
+
+Ask each question below **one at a time**. After each, **STOP** and wait for the user's response before proceeding.
+
+---
+
+## Seed Idea
+
+Ask:
+
+```
+What's on your mind?
+
+- What idea or topic do you want to explore?
+- What prompted this - a problem, opportunity, curiosity?
+```
+
+**STOP.** Wait for user response before proceeding.
+
+---
+
+## Current Knowledge
+
+Ask:
+
+```
+What do you already know?
+
+- Any initial thoughts or research you've done?
+- Constraints or context I should be aware of?
+```
+
+**STOP.** Wait for user response before proceeding.
+
+---
+
+## Starting Point
+
+Ask:
+
+```
+Where should we start?
+
+- Technical feasibility? Market landscape? Business model?
+- Or just talk it through and see where it goes?
+```
+
+**STOP.** Wait for user response before proceeding.
+
+---
+
+## Final Context
+
+Ask:
+
+```
+Any constraints or context I should know about upfront?
+
+(Or "none" if we're starting fresh)
+```
+
+**STOP.** Wait for user response before proceeding.
+
+---

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

@@ -0,0 +1,23 @@
+# Invoke the Skill
+
+*Reference for **[start-research](../SKILL.md)***
+
+---
+
+This skill's purpose is now fulfilled.
+
+Invoke the [technical-research](../../technical-research/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
+
+**Example handoff:**
+```
+Research session for: {topic}
+Output: docs/workflow/research/exploration.md
+
+Context:
+- Prompted by: {problem, opportunity, or curiosity}
+- Already knows: {any initial thoughts or research, or "starting fresh"}
+- Starting point: {technical feasibility, market, business model, or "open exploration"}
+- Constraints: {any constraints mentioned, or "none"}
+
+Invoke the technical-research skill.
+```

package/skills/start-review/SKILL.md

@@ -114,8 +114,7 @@ Available Plans:
   1. {topic-1} ({status}) - format: {format}, spec: {exists|missing}
   2. {topic-2} ({status}) - format: {format}, spec: {exists|missing}
 
-· · ·
-
+· · · · · · · · · · · ·
 Which plan would you like to review the implementation for? (Enter a number or name)
 ```
 
@@ -138,13 +137,13 @@ Auto-selecting: {topic} (only available plan)
 Ask the user what code to review:
 
 ```
-· · ·
-
+· · · · · · · · · · · ·
 What code should I review?
 
 - **`a`/`all`** — All changes since the plan was created
 - **`g`/`git`** — Identify from git status
 - Specific directories or files — tell me which
+· · · · · · · · · · · ·
 ```
 
 **STOP.** Wait for user response.