Merge pull request TheBushidoCollective#18 from TheBushidoCollective/hampton/design-unit-wireframes

feat(wireframes): include design units in wireframe generation

Author: jwaldrip

plugin/skills/elaborate-wireframes/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: (Internal) Autonomous wireframe generation for AI-DLC elaboration frontend units
+description: (Internal) Autonomous wireframe generation for AI-DLC elaboration frontend and design units
 context: fork
 agent: general-purpose
 user-invocable: false
@@ -27,7 +27,7 @@ allowed-tools:
 
 # Elaborate: Wireframe Generation
 
-Autonomous wireframe generation for AI-DLC elaboration frontend units. This skill runs as a forked subagent — it reads a brief file from disk, generates low-fidelity HTML wireframes, and writes results to disk.
+Autonomous wireframe generation for AI-DLC elaboration frontend and design units. This skill runs as a forked subagent — it reads a brief file from disk, generates low-fidelity HTML wireframes, and writes results to disk.
 
 **You have NO access to `AskUserQuestion`.** All work is fully autonomous. The main elaboration skill will present wireframes to product for review.
 
@@ -47,7 +47,7 @@ design_provider_type: figma  # or empty
 ```
 
 The markdown body contains:
-- **Frontend Units**: List of frontend units with their file paths, descriptions, domain entities, and technical specs
+- **Frontend & Design Units**: List of frontend and design units with their file paths, descriptions, domain entities, and technical specs
 - **Design Context**: Design analysis findings from discovery.md (if any)
 - **Domain Model Reference**: Abbreviated domain model for context
 
@@ -57,7 +57,7 @@ The markdown body contains:
 cd "{worktree_path}"
 ```
 
-**If no frontend units are listed in the brief**, write results with `status: skipped` and exit immediately.
+**If no frontend or design units are listed in the brief**, write results with `status: skipped` and exit immediately.
 
 ---
 
@@ -85,9 +85,9 @@ mkdir -p ".ai-dlc/${INTENT_SLUG}/mockups"
 
 ---
 
-## Step 4: Generate Wireframe HTML Per Frontend Unit
+## Step 4: Generate Wireframe HTML Per Frontend or Design Unit
 
-For each frontend unit from the brief, create a self-contained HTML file at:
+For each frontend or design unit from the brief, create a self-contained HTML file at:
 `.ai-dlc/{intent-slug}/mockups/unit-{NN}-{slug}-wireframe.html`
 
 Where `{NN}` is the zero-padded unit number and `{slug}` is the unit filename slug.
@@ -204,7 +204,7 @@ All wireframes MUST use this exact visual style — a gray/white low-fidelity ae
 
 ## Step 5: Add Wireframe Field to Unit Frontmatter
 
-For each frontend unit that received a wireframe, update its frontmatter by adding or replacing the `wireframe:` field:
+For each frontend or design unit that received a wireframe, update its frontmatter by adding or replacing the `wireframe:` field:
 
 ```yaml
 wireframe: mockups/unit-{NN}-{slug}-wireframe.html
@@ -220,7 +220,7 @@ Read the unit file, find the YAML frontmatter block, add the `wireframe:` field,
 INTENT_SLUG="{intent_slug from brief}"
 git add .ai-dlc/${INTENT_SLUG}/mockups/
 git add .ai-dlc/${INTENT_SLUG}/unit-*.md
-git commit -m "elaborate: add wireframes for ${INTENT_SLUG} frontend units"
+git commit -m "elaborate: add wireframes for ${INTENT_SLUG} frontend and design units"
 ```
 
 ---
@@ -250,7 +250,7 @@ error_message: ""
 - {any observations about the wireframes, ambiguities noted, design interpretation decisions}
 ```
 
-If no frontend units were in the brief:
+If no frontend or design units were in the brief:
 
 ```markdown
 ---
@@ -260,7 +260,7 @@ error_message: ""
 
 # Wireframe Generation Results
 
-No frontend units found — wireframe generation skipped.
+No frontend or design units found — wireframe generation skipped.
 ```
 
 ---

plugin/skills/elaborate/SKILL.md

@@ -1088,10 +1088,10 @@ git commit -m "elaborate(${INTENT_SLUG}): draft unit-NN-{slug}"
 
 **CRITICAL: If your output only shows the unit title or frontmatter without the body sections (Description, Technical Specification, Success Criteria, etc.), you have truncated the output. Go back and display the full file.**
 
-**Step C — If the unit has `discipline: frontend`, open its wireframe in the browser** so the user can review the visual alongside the spec:
+**Step C — If the unit has `discipline: frontend` or `discipline: design`, open its wireframe in the browser** so the user can review the visual alongside the spec:
 
 ```bash
-# Only for frontend units — open the wireframe if it exists
+# Only for frontend or design units — open the wireframe if it exists
 WIREFRAME=".ai-dlc/${INTENT_SLUG}/mockups/unit-NN-{slug}-wireframe.html"
 if [ -f "$WIREFRAME" ]; then
   open "$WIREFRAME"  # macOS; use xdg-open on Linux
@@ -1158,17 +1158,17 @@ This ensures builders can pull the intent branch when working remotely. Note in
 
 ---
 
-## Phase 6.25: Generate Frontend Wireframes (Delegated)
+## Phase 6.25: Generate Frontend & Design Wireframes (Delegated)
 
-**Skip this phase entirely if no units have `discipline: frontend` in their frontmatter.**
+**Skip this phase entirely if no units have `discipline: frontend` or `discipline: design` in their frontmatter.**
 
-Wireframe generation runs in a forked subagent. The subagent generates low-fidelity HTML wireframes for all frontend units, updates unit frontmatter, and commits the artifacts.
+Wireframe generation runs in a forked subagent. The subagent generates low-fidelity HTML wireframes for all frontend and design units, updates unit frontmatter, and commits the artifacts.
 
-### Step 1: Identify frontend units
+### Step 1: Identify frontend and design units
 
-Scan all `unit-*.md` files in `.ai-dlc/{intent-slug}/`. Collect units where frontmatter contains `discipline: frontend`.
+Scan all `unit-*.md` files in `.ai-dlc/{intent-slug}/`. Collect units where frontmatter contains `discipline: frontend` or `discipline: design`.
 
-If no frontend units exist, skip to Phase 6.5.
+If no frontend or design units exist, skip to Phase 6.5.
 
 ### Step 2: Load design provider config
 
@@ -1190,9 +1190,9 @@ intent_title: {Intent Title from intent.md}
 design_provider_type: {DESIGN_TYPE or empty}
 ---
 
-# Frontend Units
+# Frontend & Design Units
 
-{For each frontend unit, include:}
+{For each frontend or design unit, include:}
 
 ## {unit filename}
 
@@ -1229,15 +1229,15 @@ Skill("elaborate-wireframes", args: ".ai-dlc/{INTENT_SLUG}/.briefs/elaborate-wir
 
 Read `.ai-dlc/${INTENT_SLUG}/.briefs/elaborate-wireframes-results.md`.
 
-- If `status: skipped` — no frontend units found, proceed to Phase 6.5
+- If `status: skipped` — no frontend or design units found, proceed to Phase 6.5
 - If `status: error` — report the error to the user and discuss how to proceed
 - If `status: success` — list the generated wireframes for the user
 
 Commit the wireframe artifacts and results brief:
 
 ```bash
 git add .ai-dlc/${INTENT_SLUG}/mockups/ .ai-dlc/${INTENT_SLUG}/.briefs/elaborate-wireframes-results.md
-git commit -m "elaborate(${INTENT_SLUG}): generate frontend wireframes"
+git commit -m "elaborate(${INTENT_SLUG}): generate frontend and design wireframes"
 ```
 
 ### Step 6: Product review gate
@@ -1247,7 +1247,7 @@ Present all generated wireframes to product for review using `AskUserQuestion`:
 ```json
 {
   "questions": [{
-    "question": "I've generated low-fidelity wireframes for the frontend units. Please open them in a browser to review screen structure, flow, and placeholder copy. How do they look?",
+    "question": "I've generated low-fidelity wireframes for the frontend and design units. Please open them in a browser to review screen structure, flow, and placeholder copy. How do they look?",
     "header": "Wireframes",
     "options": [
       {"label": "Approved", "description": "Wireframes accurately capture the intended screens, flows, and copy"},