@leeovery/claude-technical-workflows 2.1.40 → 2.1.42

package/skills/technical-specification/SKILL.md

@@ -1,6 +1,6 @@
 ---
 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 docs/workflow/specification/{topic}/specification.md that can be used to build implementation plans."
+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
 ---
 
@@ -35,7 +35,7 @@ Either way: Transform unvalidated reference material into a specification that's
 
 ```
 I need source material to build a specification from. Could you point me to the
-source files (e.g., docs/workflow/discussion/{topic}.md), or provide the content
+source files (e.g., .workflows/discussion/{topic}.md), or provide the content
 directly?
 ```
 
@@ -47,7 +47,7 @@ directly?
 
 ```
 What should the specification be named? This determines the output file:
-docs/workflow/specification/{name}/specification.md
+.workflows/specification/{name}/specification.md
 ```
 
 **STOP.** Wait for user response.
@@ -97,7 +97,7 @@ When announcing a new step, output `── ── ── ── ──` on its o
 
 ## Step 0: Resume Detection
 
-Check if `docs/workflow/specification/{topic}/specification.md` exists.
+Check if `.workflows/specification/{topic}/specification.md` exists.
 
 #### If no file exists
 
@@ -147,7 +147,7 @@ Load **[verify-source-material.md](references/verify-source-material.md)** and f
 
 Load **[specification-format.md](references/specification-format.md)** for the template.
 
-Create the specification file at `docs/workflow/specification/{topic}/specification.md`:
+Create the specification file at `.workflows/specification/{topic}/specification.md`:
 
 1. Use the frontmatter template from specification-format.md
 2. Set `topic` to the kebab-case topic name

package/skills/technical-specification/references/dependencies.md

@@ -12,9 +12,9 @@ The same workflow applies: present the dependencies section for approval, then l
 
 Dependencies are **blockers** — things that must exist before implementation can begin.
 
-Think of it like building a house: if you're specifying the roof, the walls are a dependency. You cannot build a roof without walls to support it. The walls must exist first.
+If feature B requires data that feature A produces, then feature A is a dependency — B cannot function without A's output existing first.
 
-**The test**: "If system X doesn't exist, can we still build this feature?"
+**The test**: "If system X doesn't exist, can we still deliver this?"
 - If **no** → X is a dependency
 - If **yes** → X is not a dependency (even if the systems work together)
 

package/skills/technical-specification/references/review-tracking-format.md

@@ -8,7 +8,7 @@ Review tracking files capture analysis findings so work persists across context
 
 ## Location
 
-Store tracking files in the specification topic directory (`docs/workflow/specification/{topic}/`), cycle-numbered:
+Store tracking files in the specification topic directory (`.workflows/specification/{topic}/`), cycle-numbered:
 - `review-input-tracking-c{N}.md` — Phase 1 findings for cycle N
 - `review-gap-analysis-tracking-c{N}.md` — Phase 2 findings for cycle N
 

package/skills/technical-specification/references/specification-format.md

@@ -4,7 +4,7 @@
 
 ---
 
-This file defines the canonical structure for specification files (`docs/workflow/specification/{topic}/specification.md`).
+This file defines the canonical structure for specification files (`.workflows/specification/{topic}/specification.md`).
 
 The specification is a single file per topic. Structure is **flexible** — organize around phases and subject matter, not rigid sections. This is a working document.
 

package/skills/technical-specification/references/verify-source-material.md

@@ -15,6 +15,6 @@ Verify that all source material exists and is accessible before beginning specif
 ### Example
 
 ```bash
-ls docs/workflow/discussion/auth-flow.md
-ls docs/workflow/research/api-patterns.md
+ls .workflows/discussion/auth-flow.md
+ls .workflows/research/api-patterns.md
 ```

package/skills/view-plan/SKILL.md

@@ -17,14 +17,14 @@ Display a readable summary of a plan's phases, tasks, and status.
 If no topic is specified, list available plans:
 
 ```bash
-ls docs/workflow/planning/
+ls .workflows/planning/
 ```
 
 Ask the user which plan to view.
 
 ## Step 2: Read the Plan Index
 
-Read the plan file from `docs/workflow/planning/{topic}/plan.md` and check the `format:` field in the frontmatter.
+Read the plan file from `.workflows/planning/{topic}/plan.md` and check the `format:` field in the frontmatter.
 
 ## Step 3: Load Format Reading Reference