@leeovery/claude-technical-workflows 2.1.24 → 2.1.25

package/skills/start-specification/references/confirm-create.md

@@ -6,6 +6,8 @@
 
 #### If no source discussions have individual specs
 
+> *Output the next fenced block as a code block:*
+
 ```
 Creating specification: {Title Case Name}
 
@@ -16,16 +18,22 @@ Sources:
 Output: docs/workflow/specification/{kebab-case-name}.md
 ```
 
+> *Output the next fenced block as markdown (not a code block):*
+
+```
 · · · · · · · · · · · ·
 Proceed?
 - **`y`/`yes`**
 - **`n`/`no`**
 · · · · · · · · · · · ·
+```
 
 #### If any source discussion has an individual spec
 
 Note the supersession (`has_individual_spec: true`):
 
+> *Output the next fenced block as a code block:*
+
 ```
 Creating specification: {Title Case Name}
 
@@ -39,11 +47,15 @@ After completion:
   specification/{discussion-name}.md → marked as superseded
 ```
 
+> *Output the next fenced block as markdown (not a code block):*
+
+```
 · · · · · · · · · · · ·
 Proceed?
 - **`y`/`yes`**
 - **`n`/`no`**
 · · · · · · · · · · · ·
+```
 
 **STOP.** Wait for user response.
 
@@ -61,12 +73,14 @@ Proceed?
 
 #### If single discussion (no menu to return to)
 
+> *Output the next fenced block as a code block:*
+
 ```
 Understood. You can run /start-discussion to continue working on
 discussions, or re-run this command when ready.
 ```
 
-Command ends.
+**STOP.** Do not proceed — terminal condition.
 
 #### If groupings or specs menu
 

package/skills/start-specification/references/confirm-refine.md

@@ -4,6 +4,8 @@
 
 ---
 
+> *Output the next fenced block as a code block:*
+
 ```
 Refining specification: {Title Case Name}
 
@@ -13,11 +15,15 @@ All sources extracted:
   • {discussion-name}
 ```
 
+> *Output the next fenced block as markdown (not a code block):*
+
+```
 · · · · · · · · · · · ·
 Proceed?
 - **`y`/`yes`**
 - **`n`/`no`**
 · · · · · · · · · · · ·
+```
 
 **STOP.** Wait for user response.
 
@@ -29,12 +35,14 @@ Proceed?
 
 #### If single discussion (no menu to return to)
 
+> *Output the next fenced block as a code block:*
+
 ```
 Understood. You can run /start-discussion to continue working on
 discussions, or re-run this command when ready.
 ```
 
-Command ends.
+**STOP.** Do not proceed — terminal condition.
 
 #### If groupings or specs menu
 

package/skills/start-specification/references/confirm-unify.md

@@ -6,6 +6,8 @@
 
 #### If existing specifications will be superseded
 
+> *Output the next fenced block as a code block:*
+
 ```
 Creating specification: Unified
 
@@ -21,14 +23,20 @@ Existing specifications to incorporate:
 Output: docs/workflow/specification/unified.md
 ```
 
+> *Output the next fenced block as markdown (not a code block):*
+
+```
 · · · · · · · · · · · ·
 Proceed?
 - **`y`/`yes`**
 - **`n`/`no`**
 · · · · · · · · · · · ·
+```
 
 #### If no existing specifications
 
+> *Output the next fenced block as a code block:*
+
 ```
 Creating specification: Unified
 
@@ -40,11 +48,15 @@ Sources:
 Output: docs/workflow/specification/unified.md
 ```
 
+> *Output the next fenced block as markdown (not a code block):*
+
+```
 · · · · · · · · · · · ·
 Proceed?
 - **`y`/`yes`**
 - **`n`/`no`**
 · · · · · · · · · · · ·
+```
 
 **STOP.** Wait for user response.
 

package/skills/start-specification/references/display-analyze.md

@@ -8,6 +8,8 @@ Prompted when multiple concluded discussions exist, no specifications exist, and
 
 ## Display
 
+> *Output the next fenced block as a code block:*
+
 ```
 Specification Overview
 
@@ -23,11 +25,14 @@ List all concluded discussions from discovery output.
 
 ### If in-progress discussions exist
 
+> *Output the next fenced block as a code block:*
+
 ```
 Discussions not ready for specification:
 These discussions are still in progress and must be concluded
 before they can be included in a specification.
-  · {discussion-name} (in-progress)
+
+  • {discussion-name}
 ```
 
 ### Cache-Aware Message
@@ -36,20 +41,28 @@ No `---` separator before these messages.
 
 #### If cache status is "none"
 
+> *Output the next fenced block as a code block:*
+
 ```
 These discussions will be analyzed for natural groupings to determine
 how they should be organized into specifications. Results are cached
 and reused until discussions change.
 ```
 
+> *Output the next fenced block as markdown (not a code block):*
+
+```
 · · · · · · · · · · · ·
 Proceed with analysis?
 - **`y`/`yes`**
 - **`n`/`no`**
 · · · · · · · · · · · ·
+```
 
 #### If cache status is "stale"
 
+> *Output the next fenced block as a code block:*
+
 ```
 A previous grouping analysis exists but is outdated — discussions
 have changed since it was created.
@@ -58,11 +71,15 @@ These discussions will be re-analyzed for natural groupings. Results
 are cached and reused until discussions change.
 ```
 
+> *Output the next fenced block as markdown (not a code block):*
+
+```
 · · · · · · · · · · · ·
 Proceed with analysis?
 - **`y`/`yes`**
 - **`n`/`no`**
 · · · · · · · · · · · ·
+```
 
 **STOP.** Wait for user response.
 
@@ -77,9 +94,11 @@ rm docs/workflow/.cache/discussion-consolidation-analysis.md
 
 #### If user declines (n)
 
+> *Output the next fenced block as a code block:*
+
 ```
 Understood. You can run /start-discussion to continue working on
 discussions, or re-run this command when ready.
 ```
 
-**Command ends.** Control returns to the user.
+**STOP.** Do not proceed — terminal condition.

package/skills/start-specification/references/display-blocks.md

@@ -8,8 +8,10 @@ Two terminal paths — the command stops and cannot proceed.
 
 ## If no discussions exist
 
+> *Output the next fenced block as a code block:*
+
 ```
-Specification Phase
+Specification Overview
 
 No discussions found.
 
@@ -20,18 +22,21 @@ that specifications are built upon.
 Run /start-discussion to begin documenting technical decisions.
 ```
 
-**STOP.** Wait for user acknowledgment. Command ends here.
+**STOP.** Do not proceed — terminal condition.
 
 ## If discussions exist but none concluded
 
+> *Output the next fenced block as a code block:*
+
 ```
-Specification Phase
+Specification Overview
 
 No concluded discussions found.
 
 The following discussions are still in progress:
-  · {discussion-name} (in-progress)
-  · {discussion-name} (in-progress)
+
+  • {discussion-name}
+  • {discussion-name}
 
 Specifications can only be created from concluded discussions.
 Run /start-discussion to continue working on a discussion.
@@ -39,4 +44,4 @@ Run /start-discussion to continue working on a discussion.
 
 List all in-progress discussions from discovery output.
 
-**STOP.** Wait for user acknowledgment. Command ends here.
+**STOP.** Do not proceed — terminal condition.

package/skills/start-specification/references/display-groupings.md

@@ -50,38 +50,40 @@ For each discussion: status is `ready`. Spec status: `none`.
 
 All items are first-class — every grouping (including single-discussion entries) is a numbered item.
 
+> *Output the next fenced block as a code block:*
+
 ```
 Specification Overview
 
 Recommended breakdown for specifications with their source discussions.
 
-1. {Grouping Name}
-   └─ Spec: {status} {(X of Y sources extracted) if applicable}
+1. {grouping_name:(titlecase)}
+   └─ Spec: @if(has_spec) {spec_status:[in-progress|concluded]} ({extraction_summary}) @else (no spec) @endif
    └─ Discussions:
-      ├─ {discussion-name} ({status})
-      └─ {discussion-name} ({status})
+      ├─ {discussion} ({status:[extracted|pending|ready|reopened]})
+      └─ ...
 
-2. {Grouping Name}
-   └─ Spec: none
-   └─ Discussions:
-      └─ {discussion-name} (ready)
+2. ...
 ```
 
-**Output in a fenced code block exactly as shown above.**
-
 ### If in-progress discussions exist
 
+> *Output the next fenced block as a code block:*
+
 ```
 Discussions not ready for specification:
 These discussions are still in progress and must be concluded
 before they can be included in a specification.
-  · {discussion-name} (in-progress)
+
+  • {discussion-name}
 ```
 
 ### Key/Legend
 
 Show only the statuses that appear in the current display. No `---` separator before this section.
 
+> *Output the next fenced block as a code block:*
+
 ```
 Key:
 
@@ -92,7 +94,6 @@ Key:
     reopened  — was extracted but discussion has regressed to in-progress
 
   Spec status:
-    none        — no specification file exists yet
     in-progress — specification work is ongoing
     concluded   — specification is complete
 ```
@@ -101,6 +102,8 @@ Key:
 
 No `---` separator before this section.
 
+> *Output the next fenced block as a code block:*
+
 ```
 Tip: To restructure groupings or pull a discussion into its own
 specification, choose "Re-analyze" and provide guidance.
@@ -127,6 +130,8 @@ After all grouping entries, append meta options:
 
 **Example assembled menu** (2 groupings, specs exist):
 
+> *Output the next fenced block as markdown (not a code block):*
+
 ```
 · · · · · · · · · · · ·
 1. Start "Auth Flow" — 2 ready discussions
@@ -143,7 +148,9 @@ Select an option (enter number):
 · · · · · · · · · · · ·
 ```
 
-**Output in a fenced code block exactly as shown above.** Every meta option (Unify, Re-analyze) MUST include its description lines.
+Recreate with actual topics and states from discovery.
+
+Every meta option (Unify, Re-analyze) MUST include its description lines.
 
 **STOP.** Wait for user response.
 

package/skills/start-specification/references/display-single-grouped.md

@@ -15,33 +15,38 @@ Extraction count: X = sources with `status: incorporated`, Y = total source coun
 
 ## Display
 
+> *Output the next fenced block as a code block:*
+
 ```
 Specification Overview
 
 Single concluded discussion found with existing multi-source specification.
 
-1. {Spec Title Case Name}
-   └─ Spec: {spec_status} ({X} of {Y} sources extracted)
+1. {topic:(titlecase)}
+   └─ Spec: {spec_status:[in-progress|concluded]} ({X} of {Y} sources extracted)
    └─ Discussions:
       ├─ {source-name} (extracted)
       └─ {source-name} (extracted, reopened)
 ```
 
-**Output in a fenced code block exactly as shown above.**
-
 ### If in-progress discussions exist
 
+> *Output the next fenced block as a code block:*
+
 ```
 Discussions not ready for specification:
 These discussions are still in progress and must be concluded
 before they can be included in a specification.
-  · {discussion-name} (in-progress)
+
+  • {discussion-name}
 ```
 
 ### Key/Legend
 
 Show only the statuses that appear in the current display. No `---` separator before this section.
 
+> *Output the next fenced block as a code block:*
+
 ```
 Key:
 
@@ -57,8 +62,10 @@ Key:
 
 ## After Display
 
+> *Output the next fenced block as a code block:*
+
 ```
-Automatically proceeding with "{Spec Title Case Name}".
+Automatically proceeding with "{topic:(titlecase)}".
 ```
 
 Auto-proceed uses the spec name. Verb rule:

package/skills/start-specification/references/display-single-has-spec.md

@@ -10,32 +10,37 @@ Determine extraction count: check the spec's `sources` array from discovery. Cou
 
 ## Display
 
+> *Output the next fenced block as a code block:*
+
 ```
 Specification Overview
 
 Single concluded discussion found with existing specification.
 
-1. {Title Case Name}
-   └─ Spec: {spec_status} ({X} of {Y} sources extracted)
+1. {topic:(titlecase)}
+   └─ Spec: {spec_status:[in-progress|concluded]} ({X} of {Y} sources extracted)
    └─ Discussions:
       └─ {discussion-name} (extracted)
 ```
 
-**Output in a fenced code block exactly as shown above.**
-
 ### If in-progress discussions exist
 
+> *Output the next fenced block as a code block:*
+
 ```
 Discussions not ready for specification:
 These discussions are still in progress and must be concluded
 before they can be included in a specification.
-  · {discussion-name} (in-progress)
+
+  • {discussion-name}
 ```
 
 ### Key/Legend
 
 No `---` separator before this section.
 
+> *Output the next fenced block as a code block:*
+
 ```
 Key:
 
@@ -43,13 +48,16 @@ Key:
     extracted — content has been incorporated into the specification
 
   Spec status:
-    {spec_status} — {in-progress: "specification work is ongoing" | concluded: "specification is complete"}
+    in-progress — specification work is ongoing
+    concluded   — specification is complete
 ```
 
 ## After Display
 
+> *Output the next fenced block as a code block:*
+
 ```
-Automatically proceeding with "{Title Case Name}".
+Automatically proceeding with "{topic:(titlecase)}".
 ```
 
 Auto-proceed. Verb rule:

package/skills/start-specification/references/display-single-no-spec.md

@@ -8,46 +8,50 @@ No specification exists for this discussion.
 
 ## Display
 
+> *Output the next fenced block as a code block:*
+
 ```
 Specification Overview
 
 Single concluded discussion found.
 
-1. {Title Case Name}
-   └─ Spec: none
+1. {topic:(titlecase)}
+   └─ Spec: (no spec)
    └─ Discussions:
       └─ {discussion-name} (ready)
 ```
 
-**Output in a fenced code block exactly as shown above.**
-
 ### If in-progress discussions exist
 
+> *Output the next fenced block as a code block:*
+
 ```
 Discussions not ready for specification:
 These discussions are still in progress and must be concluded
 before they can be included in a specification.
-  · {discussion-name} (in-progress)
+
+  • {discussion-name}
 ```
 
 ### Key/Legend
 
 No `---` separator before this section.
 
+> *Output the next fenced block as a code block:*
+
 ```
 Key:
 
   Discussion status:
     ready — concluded and available to be specified
-
-  Spec status:
-    none — no specification file exists yet
 ```
 
 ## After Display
 
+> *Output the next fenced block as a code block:*
+
 ```
-Automatically proceeding with "{Title Case Name}".
+Automatically proceeding with "{topic:(titlecase)}".
 ```
 
 Auto-proceed with verb **"Creating"**.

package/skills/start-specification/references/display-single.md

@@ -6,8 +6,6 @@
 
 Auto-proceed path — only one concluded discussion exists, so no selection menu is needed.
 
-Convert discussion filename to title case (`auth-flow` → `Auth Flow`).
-
 ## Route by Spec Coverage
 
 Check if a spec covers this discussion — either by name match (`has_individual_spec`) or by listing it in a spec's `sources` array.

package/skills/start-specification/references/display-specs-menu.md

@@ -8,6 +8,8 @@ Shows when multiple concluded discussions exist, specifications exist, and cache
 
 ## A. Display
 
+> *Output the next fenced block as a code block:*
+
 ```
 Specification Overview
 
@@ -18,16 +20,16 @@ Existing specifications:
 
 For each non-superseded specification from discovery output, display as nested tree:
 
+> *Output the next fenced block as a code block:*
+
 ```
-1. {Spec Title Case Name}
-   └─ Spec: {status} ({X} of {Y} sources extracted)
+1. {topic:(titlecase)}
+   └─ Spec: {spec_status:[in-progress|concluded]} ({X} of {Y} sources extracted)
    └─ Discussions:
       ├─ {source-name} (extracted)
       └─ {source-name} (extracted)
 ```
 
-**Output in a fenced code block exactly as shown above.**
-
 Determine discussion status from the spec's `sources` array:
 - `incorporated` + `discussion_status: concluded` or `not-found` → `extracted`
 - `incorporated` + `discussion_status: other` (e.g. `in-progress`) → `extracted, reopened`
@@ -39,6 +41,8 @@ Extraction count: X = sources with `status: incorporated`, Y = total source coun
 
 List concluded discussions that are not in any specification's `sources` array:
 
+> *Output the next fenced block as a code block:*
+
 ```
 Concluded discussions not in a specification:
   • {discussion-name}
@@ -47,17 +51,22 @@ Concluded discussions not in a specification:
 
 ### If in-progress discussions exist
 
+> *Output the next fenced block as a code block:*
+
 ```
 Discussions not ready for specification:
 These discussions are still in progress and must be concluded
 before they can be included in a specification.
-  · {discussion-name} (in-progress)
+
+  • {discussion-name}
 ```
 
 ### Key/Legend
 
 Show only the statuses that appear in the current display. No `---` separator before this section.
 
+> *Output the next fenced block as a code block:*
+
 ```
 Key:
 
@@ -76,12 +85,16 @@ No `---` separator before these messages.
 
 #### If cache status is "none"
 
+> *Output the next fenced block as a code block:*
+
 ```
 No grouping analysis exists.
 ```
 
 #### If cache status is "stale"
 
+> *Output the next fenced block as a code block:*
+
 ```
 A previous grouping analysis exists but is outdated — discussions
 have changed since it was created. Re-analysis is required.
@@ -101,6 +114,8 @@ List "Analyze for groupings (recommended)" first, then one entry per existing no
 
 **Example assembled menu** (2 specs exist):
 
+> *Output the next fenced block as markdown (not a code block):*
+
 ```
 · · · · · · · · · · · ·
 1. Analyze for groupings (recommended)
@@ -114,7 +129,7 @@ Select an option (enter number):
 · · · · · · · · · · · ·
 ```
 
-**Output in a fenced code block exactly as shown above.**
+Recreate with actual topics and states from discovery.
 
 Menu descriptions are wrapped in backticks to visually distinguish them from the choice labels.