@leeovery/claude-technical-workflows 2.1.24 → 2.1.26

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.
 

package/skills/status/SKILL.md

@@ -2,6 +2,7 @@
 name: status
 description: "Show workflow status - what exists, where you are, and what to do next."
 disable-model-invocation: true
+allowed-tools: Bash(.claude/skills/status/scripts/discovery.sh)
 ---
 
 Show the current state of the workflow for this project.
@@ -12,74 +13,190 @@ Show the current state of the workflow for this project.
 
 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: Scan Directories
+## Step 1: Discovery State
 
-Check for files in each workflow directory:
+!`.claude/skills/status/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/status/scripts/discovery.sh
 ```
-docs/workflow/research/
-docs/workflow/discussion/
-docs/workflow/specification/
-docs/workflow/planning/
-```
+
+If YAML content is already displayed, it has been run on your behalf.
+
+Parse the discovery output. **IMPORTANT**: Use ONLY this script for discovery. Do NOT run additional bash commands (ls, head, cat, etc.) to gather state.
+
+→ Proceed to **Step 2**.
+
+---
 
 ## Step 2: Present Status
 
-Research is project-wide exploration. From discussion onwards, work is organised by **topic** - different topics may be at different stages.
+Build the display from discovery data. Only show sections for phases that have content.
+
+**CRITICAL**: Entities don't flow one-to-one across phases. Multiple discussions may combine into one specification, topic names may change between phases, and specs may be superseded. The display must make these relationships visible — primarily through the specification's `sources` array.
 
-Show a summary like this:
+### 2a: Summary
 
+> *Output the next fenced block as a code block:*
+
+```
+Workflow Status
+
+  Research:       {count} file(s)
+  Discussion:     {count} ({concluded} concluded, {in_progress} in-progress)
+  Specification:  {active} active ({feature} feature, {crosscutting} cross-cutting)
+  Planning:       {count} ({concluded} concluded, {in_progress} in-progress)
+  Implementation: {count} ({completed} completed, {in_progress} in-progress)
 ```
-## Workflow Status
 
-**Research:** 2 files (exploration.md, market-analysis.md)
+Only show lines for phases that have content. If a phase has zero items but a later phase has content, show the line as `(none)` to highlight the gap.
+
+#### If no workflow content exists at all
 
-**Topics:**
+> *Output the next fenced block as a code block:*
 
-| Topic        | Discussion | Spec | Plan | Implemented |
-|--------------|------------|------|------|-------------|
-| auth-system  | ✓          | ✓    | ✓    | in progress |
-| payment-flow | ✓          | ✓    | -    | -           |
-| notifications| ✓          | -    | -    | -           |
 ```
+Workflow Status
 
-Adapt based on what exists:
-- If a directory is empty or missing, show "Not started"
-- For planning, note the output format if specified in frontmatter
-- Match topics across phases by filename
+No workflow files found in docs/workflow/
 
-## Step 3: Suggest Next Steps
+Start with /start-research to explore ideas,
+or /start-discussion if you already know what to build.
+```
+
+**STOP.** Do not proceed — terminal condition.
+
+### 2b: Specifications
+
+Show if any specifications exist. This is the most important section — it reveals many-to-one relationships between discussions and specifications.
+
+> *Output the next fenced block as a code block:*
+
+```
+Specifications
+
+  1. {name:(titlecase)} ({status})
+     └─ Sources: {src1} ({src1_status}), {src2} ({src2_status})
+
+  2. ...
+```
+
+**Rules:**
+
+- Each numbered item is an active (non-superseded) specification
+- Show `(cross-cutting)` after status for cross-cutting specs; omit type label for feature specs
+- Sources come from the spec's `sources` array — show all with their incorporation status
+- If a spec has no sources, show `└─ Sources: (none)`
+- Blank line between numbered items
+- If superseded specs exist, show after the numbered list:
+
+```
+  Superseded:
+    • {name} → {superseded_by}
+```
+
+### 2c: Plans
+
+Show if any plans exist.
+
+> *Output the next fenced block as a code block:*
 
-Based on what exists, offer relevant options. Don't assume linear progression - topics may have dependencies on each other.
+```
+Plans
+
+  1. {name:(titlecase)} ({status})
+     └─ Spec: {specification_name}
+
+  2. ...
+```
+
+**Rules:**
+
+- Map raw `planning` status to `in-progress` in the display
+- Show spec name without `.md` extension
+- If `has_unresolved_deps`, add line: `└─ Blocked: {dep_topic}:{dep_task_id} ({dep_state})`
+
+### 2d: Implementation
+
+Show if any implementations exist.
 
-**If nothing exists:**
-- "Start with `/start-research` to explore ideas, or `/start-discussion` if you already know what you're building."
+> *Output the next fenced block as a code block:*
 
-**If topics exist at various stages**, summarise options without being prescriptive:
-- Topics in discussion can move to specification
-- Topics with specs can move to planning
-- Topics with plans can move to implementation
-- Completed implementations can be reviewed
+```
+Implementation
+
+  1. {topic:(titlecase)} ({status})
+     └─ Phase {current_phase}, {completed_tasks}/{total_tasks} tasks done
+
+  2. ...
+```
 
-Example: "auth-system has a plan ready. payment-flow needs a spec before planning. You might want to complete planning for related topics before implementing if there are dependencies."
+**Rules:**
 
-Keep suggestions brief - the user knows their project's dependencies better than we do.
+- `not-started` → `└─ Not started`
+- `in-progress` → phase and task progress; if `total_tasks` is 0, show `{completed_tasks} tasks done` without denominator
+- `completed` → `└─ Complete`
 
-## Step 4: Mention Plan Viewing
+### 2e: Unlinked Discussions
 
-If planning files exist, let the user know they can view plan details:
+Derive which discussions are NOT referenced in any active (non-superseded) specification's `sources` array. Show only if unlinked discussions exist.
+
+> *Output the next fenced block as a code block:*
 
 ```
-To view a plan's tasks and progress, use /view-plan
+Discussions not yet in a specification:
+
+  • {name} ({status})
 ```
 
+### 2f: Key
+
+Show if the display uses statuses that benefit from explanation. Only include statuses actually shown. No `---` separator before this section.
+
+> *Output the next fenced block as a code block:*
+
+```
+Key:
+
+  Status:
+    in-progress — work is ongoing
+    concluded   — complete, ready for next step
+    superseded  — replaced by another specification
+
+  Spec type:
+    cross-cutting — architectural policy, not directly plannable
+```
+
+Omit categories with no entries.
+
+---
+
+## Step 3: Suggest Next Steps
+
+Based on gaps in the workflow, briefly suggest 2-3 most relevant actions:
+
+- Concluded discussions not in any spec → `/start-specification`
+- In-progress specs → finish with `/start-specification`
+- Concluded feature specs without plans → `/start-planning`
+- Concluded plans not yet implemented → `/start-implementation`
+- Completed implementations → `/start-review`
+
+If plans exist, mention `/view-plan` for detailed plan viewing.
+
+Keep suggestions brief — the user knows their project better than we do.
+
 ## Notes
 
-- Keep output concise - this is a quick status check
-- Use tables for scannable information
+- Keep output scannable — this is a status check, not a deep analysis
+- Discussions may appear in multiple specifications' sources
+- A discussion not appearing in any active spec's sources is "unlinked"
+- Research files are project-wide, not topic-specific
+- Topic names may differ across phases (e.g., discussions "auth-flow" and "session-mgmt" may combine into specification "auth-system")