whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/4-ux-design/workflow-specify.md

@@ -13,16 +13,11 @@ description: 'Create a complete, implementation-ready page specification with la
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
-
+Read design log at `{output_folder}/_progress/00-design-log.md` before starting.
 
 ## Entry
 
-Load page context from existing page structure in `{output_folder}/D-UX-Design/`.
+Load page context from the existing page specification in the scenario's page folder (`{output_folder}/C-UX-Scenarios/[NN-slug]/pages/[NN].[step]-[page-slug]/`).
 
 ## Steps
 
@@ -37,7 +32,8 @@ Execute steps in `./steps-p/`:
 | 05 | step-05-interactions.md | User interactions and behaviors |
 | 06 | step-06-states.md | Loading, error, empty states |
 | 07 | step-07-validation.md | Form validation and constraints |
-| 08 | step-08-generate-spec.md | Generate final specification document |
+| 08 | step-08-spacing-typography.md | Spacing objects and typography tokens |
+| 09 | step-09-generate-spec.md | Generate final specification document |
 
 **Reference data:**
 - `./data/object-types/` — component types and templates
@@ -49,6 +45,5 @@ Execute steps in `./steps-p/`:
 
 ## AFTER COMPLETION
 
-1. Update design log
-2. Suggest next action
-3. Return to activity menu
+1. Update design log: status → `specified`
+2. Return to the two-option transition from step-01-exploration.md (the calling step determines what comes next based on what was identified during specification)

package/src/workflows/4-ux-design/workflow-suggest.md

@@ -13,32 +13,35 @@ description: 'Build a scenario's page flow step by step, with the agent proposin
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
-
+Read design log at `{output_folder}/_progress/00-design-log.md` before starting.
 
 ## Entry
 
 Load scenario context from `{output_folder}/C-UX-Scenarios/`.
 
-## Steps
+### Scenario Check (CRITICAL GATE)
 
-Execute steps in `./steps-s/`:
+Before starting page design, verify that a scenario exists for the selected scenario:
 
-### Scenario Setup (if new scenario)
+1. Look for scenario files in `{output_folder}/C-UX-Scenarios/[NN-slug]/[NN-slug].md`
+2. **If a Phase 3 scenario exists** → Skip to **Page Creation** below. The scenario's 8-question answers, shortest path, and first page specification provide everything needed.
+3. **If NO scenario exists** → Do NOT attempt to define the scenario here. Instead:
+   - Inform the user: *"Before we design pages, we need a scenario outline. This gives us the user's device, mental state, entry point, and the shortest path — all essential for good page design."*
+   - Suggest returning to Phase 3 to outline the scenario using the 8-question dialog
+   - The user can then return here with [D] from the Phase 3 post-scenario menu
 
-| Step | File | Purpose |
-|------|------|---------|
-| 01 | step-01-core-feature.md | Identify the core feature |
-| 02 | step-02-entry-point.md | Define user entry point |
-| 03 | step-03-mental-state.md | Capture user mental state |
-| 04 | step-04-mutual-success.md | Define mutual success criteria |
-| 05 | step-05-shortest-path.md | Map the shortest path |
-| 06 | step-06-scenario-name.md | Name the scenario |
-| 07 | step-07-create-scenario-folder.md | Create output structure |
+**Why:** Phase 3's 8-question dialog is the canonical way to define scenarios. It produces richer, more grounded scenarios than trying to shortcut the process here.
+
+### Phase 3 Handover Context
+
+When entering from Phase 3's [D] option (start designing), the scenario file and page folders already exist. Use:
+- **Page folders** from `{output_folder}/C-UX-Scenarios/[NN-slug]/pages/[NN].1-[page-slug]/` — each page has a boilerplate `.md` and a `Sketches/` subfolder
+- **First page spec** (`[NN].1-*.md`) has full entry context (device, arrival, mental state) from Q4, Q5, Q6
+- **Shortest path** from Q8 to know the full page sequence
+
+## Steps
+
+Execute steps in `./steps-s/`:
 
 ### Page Creation (per page)
 
@@ -63,6 +66,52 @@ Execute steps in `./steps-s/`:
 
 ## AFTER COMPLETION
 
-1. Update design log
-2. Suggest next action
-3. Return to activity menu
+### Design Log Update
+
+After finishing a page specification, append to the Design Loop Status table in `{output_folder}/_progress/00-design-log.md`:
+```
+| [Scenario slug] | [NN.X] | [Page name] | specified | [YYYY-MM-DD] |
+```
+Do NOT skip this — the design log drives the adaptive dashboard.
+
+### Two-Option Transition
+
+After specification is complete, check what was identified during the design:
+- **Web platform?** → Responsive content decisions are needed
+- **Storyboard items identified?** → On-page interactions need exploring
+- **Complex functionality?** → Forms, validation, dynamic content need detail
+
+**If complexity exists:**
+
+<output>
+**Specification for "[page name]" is complete.**
+
+This page has [responsive states / storyboard items / complex functionality] that need exploring.
+
+1. **Explore [responsive states / storyboard / functionality]** — define the details
+2. **Explore the next scenario step** — [next page name]
+</output>
+
+**If simple page (no complexity identified):**
+
+<output>
+**Specification for "[page name]" is complete. Ready to build.**
+
+1. **Build it** — start agentic development
+2. **Explore the next scenario step** — [next page name]
+</output>
+
+**If no more pages in scenario:**
+Replace option 2 with: "All pages in this scenario are designed!"
+
+### Transition Handling
+
+- **Option 1 (next logical step):** Proceed to the appropriate activity (explore → responsive diffs, build → Phase 5 prototyping)
+- **Option 2 (next scenario step):** Check Q8 for the next page. If the next page doesn't have a folder yet, ask the two outline questions (page purpose + exit action), create the page folder, then design it using steps 08-15.
+- **Component Extraction Check** (2nd+ page only): Before designing the next page, scan completed specs for shared elements. If found, briefly suggest extraction. Don't block the flow — the user can defer.
+
+### Execution Rules
+
+- ALWAYS halt and wait for user input after presenting transition options
+- User can chat or ask questions — always respond and then redisplay the transition
+- The user can always say "stop" to pause and return later — log current status

package/src/workflows/4-ux-design/workflow-validate.md

@@ -13,16 +13,12 @@ description: 'Systematically audit page specifications for completeness, consist
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+Read design log at `{output_folder}/_progress/00-design-log.md` before starting.
 
 ### Configuration Loading
 
 1. Load project config
-2. Locate page specifications at `{output_folder}/D-UX-Design/`
+2. Locate page specifications at `{output_folder}/C-UX-Scenarios/`
 3. Begin: Load and execute `./steps-v/step-01-page-metadata.md`
 
 **Reference data:**
@@ -53,12 +49,12 @@ Execute each step in order. Each step produces a section of the validation repor
 
 ## Final Output
 
-Save validation report to `{output_folder}/D-UX-Design/validation-report.md`
+Save validation report to `{output_folder}/_progress/validation-report.md`
 
 ---
 
 ## AFTER COMPLETION
 
-1. Update design log
-2. Suggest next action
-3. Return to activity menu
+1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`:
+   `### [date] — Validation: [N] pages audited, [results summary]`
+2. If issues found, suggest fixing them. If all pass, suggest next logical step from the adaptive dashboard

package/src/workflows/4-ux-design/workflow-visual.md

@@ -13,16 +13,11 @@ description: 'Create visual representations of page designs using external tools
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
-
+Read design log at `{output_folder}/_progress/00-design-log.md` before starting.
 
 ## Entry
 
-Load page specification from `{output_folder}/D-UX-Design/`.
+Load page specification from `{output_folder}/C-UX-Scenarios/`.
 
 ## Steps
 
@@ -49,6 +44,6 @@ Execute steps in `./steps-w/`:
 
 ## AFTER COMPLETION
 
-1. Update design log
-2. Suggest next action
-3. Return to activity menu
+1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`:
+   `### [date] — Visual Design: [what was generated]`
+2. Suggest next action based on the adaptive dashboard (read Design Loop Status to find what needs attention next)

package/src/workflows/4-ux-design/workflow.md

@@ -14,14 +14,14 @@ web_bundle: true
 
 ## WORKFLOW ARCHITECTURE
 
-Phase 4 is **menu-driven**, not linear. The user picks scenarios and activities from a dashboard.
+Phase 4 is **adaptive** — Freya reads the design log on startup, shows the project's design status, and suggests the next logical step. The user can follow the suggestion or switch to any activity.
 
 ### Core Principles
 
+- **Adaptive**: Freya reads the design log and suggests where to continue
 - **Scenario-Driven**: Each scenario (from Phase 3) gets its own design approach
-- **Activity-Based**: Pick the right activity for the current need
-- **Non-Linear**: Start anywhere, switch between activities freely
-- **Design Intent**: Phase 3 handover specifies preferred approach per scenario
+- **Two-Option Transitions**: Every completed stage offers: next logical step + explore next scenario step
+- **Design Log as Memory**: Per-page status tracking drives the adaptive dashboard across sessions
 
 ### Step Processing Rules
 
@@ -40,53 +40,124 @@ Load and read full config from `{project-root}/_bmad/wds/config.yaml` and resolv
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`
 
-### 2. Agent Dialog Gate
+### 2. Design Log Loading
 
-1. Check `{output_folder}/_progress/agent-dialogs/` for pending UX design dialogs
-2. If pending, present with status
-3. If none, suggest creating one
+Read the design log at `{output_folder}/_progress/00-design-log.md`. This single file contains:
+- **Backlog** — business-value items to work on
+- **Current** — what's actively being worked on right now
+- **Design Loop Status** — per-page status tracking (latest row per page = current status)
+- **Log** — append-only history of completed work
+
+If the file doesn't exist, guide the user to run Phase 0 setup first.
 
 ### 3. Mode Determination
 
 **Check invocation:**
 - "validate" / -v → Load and execute `./workflow-validate.md`
-- Default → Continue to Scenario Dashboard
+- Default → Continue to Adaptive Dashboard
 
-### 4. Scenario Dashboard
+### 4. Adaptive Dashboard
 
-Read all scenario files from `{output_folder}/C-UX-Scenarios/scenarios/` and display:
+Read from the design log and scenario files:
+1. **Design log** (`{output_folder}/_progress/00-design-log.md`) — Backlog, Current, Design Loop Status, Log
+2. **Scenario files** from `{output_folder}/C-UX-Scenarios/` — full page inventory
 
-```
-Your scenarios and their design status:
+#### 4a. Build Status Overview
 
-1. [Scenario Name]     → [Approach] — [Status]
-2. [Scenario Name]     → [Approach] — [Status]
-3. [Scenario Name]     → [Approach] — [Status]
+For each scenario, determine per-page status from the **Design Loop Status** table. The latest row per page is the current status.
 
-Pick a scenario to work on, or choose a scenario-independent activity:
-```
+Check the **Current** table — if a task is listed there, the user was mid-work when the last session ended.
+
+#### 4b. Suggest Where to Continue
+
+**If a task is listed in Current:**
+
+<output>
+**Welcome back! Here's where we left off:**
+
+**In progress:** [task from Current table]
+
+**Design status:**
+| Scenario | Page | Status |
+|----------|------|--------|
+| [NN] | [page name] | [current status] |
+| ... | ... | ... |
+
+I'd suggest we continue with **[the in-progress task]**.
+Pick up there, or change direction?
+</output>
+
+**If Current is empty but Backlog has items:**
+
+<output>
+**Ready to continue!**
+
+**Next from backlog:**
+- [ ] [first unchecked backlog item]
+- [ ] [second unchecked backlog item]
+
+**Design status:**
+| Scenario | Page | Status |
+|----------|------|--------|
+| [NN] | [page name] | [latest status] |
+
+I'd suggest we start with **[first backlog item]**. Sound good?
+</output>
+
+**If both Current and Backlog are empty** (fresh project):
+
+<output>
+**Ready to start designing!**
+
+Your scenarios:
+| # | Scenario | Pages | Designed |
+|---|----------|-------|----------|
+| 01 | [Name] | [total] | [done] |
+| 02 | [Name] | [total] | [done] |
+
+Which scenario shall we work on?
+</output>
+
+#### 4c. Design Log Updates
+
+**When starting work:** Move the task from Backlog to Current (or add a new row to Current).
+
+**At each transition:** Append a row to the Design Loop Status table with the new status. Update the Log section with what was accomplished.
+
+**When finishing a task:** Remove from Current. Check off the Backlog item if applicable. The next session reads the updated design log and knows exactly where things stand.
+
+#### 4d. Agent Experiences
+
+After fruitful design discussions, methodology breakthroughs, or pattern discoveries, save compressed insights to `{output_folder}/_progress/agent-experiences/YYYY-MM-DD-[topic].md`. These are cross-session wisdom — not project state, but lessons learned.
+
+#### 4e. User Response Handling
 
-**Status values:** not started / in progress / completed
-**Approach values:** [K] Sketch, [C] Conceptualize, [S] Suggest, [D] Dream Up, [L] Not chosen
+- **User accepts suggestion** → Load the appropriate activity workflow and continue
+- **User picks a different page or scenario** → Update the session plan and continue
+- **User asks for the full activity menu** → Show the Activity Reference below
+- **User wants scenario-independent work** (design system, validation, delivery) → Route to that activity
 
 ---
 
-## ACTIVITY MENU
+## ACTIVITY REFERENCE
 
-When a scenario is selected (or for scenario-independent work), present:
+The primary navigation is the adaptive dashboard above — Freya suggests the next logical step based on the design log. The activities below are available when the user wants to switch to a specific workflow or asks for the full menu.
 
 ```
-What would you like to do?
-
-[C] Conceptualize            — Explore what the design needs
-[K] Analyse Sketches         — I'll interpret your sketch
-[S] Suggest Interface        — I'll propose a design, checking each step
-[D] Dream Up Interface       — I'll create it all, you review
-[P] Write Specifications     — Detail a page specification
-[W] Visual Design            — Work with visual tools, integrate results
-[M] Manage Design System     — Define/update design system components
-[V] Validate Specifications  — Audit a finished spec
-[H] Design Delivery          — Package DD-XXX, hand off to BMad
+── Design ──────────────────────────────────────
+[C] Discuss              — Creative dialog (D1, D2), wireframe, iterate
+[K] Analyse Sketches     — I'll interpret your sketch
+[S] Suggest Design       — I'll propose a design, you confirm each step
+[D] Dream Up Design      — I'll create it all, you review
+
+── Specify ─────────────────────────────────────
+[P] Write Specifications — Content, interactions, spacing, typography specs
+[V] Validate Specs       — Audit spec completeness and quality
+
+── Produce ─────────────────────────────────────
+[W] Visual Design        — Generate assets with Nano Banana, Stitch, etc.
+[M] Design System        — Extract or update shared components
+[H] Design Delivery      — Package for development handoff
 ```
 
 ### Activity Routing
@@ -96,10 +167,10 @@ What would you like to do?
 | [C] | workflow-conceptualize.md | steps-c/ |
 | [K] | workflow-sketch.md | steps-k/ |
 | [S] | workflow-suggest.md | steps-s/ |
-| [D] | workflow-dream.md | steps-d/ (uses steps-s/) |
+| [D] | workflow-dream.md | steps-s/ (autonomous mode) |
 | [P] | workflow-specify.md | steps-p/ |
 | [W] | workflow-visual.md | steps-w/ |
-| [M] | workflow-design-system.md | steps-m/ |
+| [M] | workflow-design-system.md | steps-m/ (extract on 2nd use) |
 | [V] | workflow-validate.md | steps-v/ |
 | [H] | workflow-handover.md | steps-h/ |
 
@@ -112,7 +183,7 @@ If the scenario has a `design_intent` from Phase 3 handover, pre-select that act
 | Location | Purpose |
 |----------|---------|
 | `data/object-types/` | Component type definitions and templates |
-| `data/guides/` | Sketch analysis, specification patterns, styling |
+| `data/guides/` | Design loop, sketch analysis, specification patterns, styling |
 | `data/modular-architecture/` | Three-tier architecture documentation |
 | `data/scenario-init/` | Scenario initialization guides and examples |
 | `data/page-creation-flows/` | Page creation flow approaches |
@@ -123,11 +194,11 @@ If the scenario has a `design_intent` from Phase 3 handover, pre-select that act
 
 ## OUTPUT
 
-- `{output_folder}/D-UX-Design/` — page specifications, design system, validation reports
+- `{output_folder}/C-UX-Scenarios/` — page specifications within scenario page folders
+- `{output_folder}/D-Design-System/` — shared components and design tokens
 
 ---
 
 ## AFTER COMPLETION
 
-1. Update design log
-2. Suggest next action or return to Scenario Dashboard
+When the user returns to Phase 4 (or starts a new session), the Adaptive Dashboard (section 4) reads the design log and suggests where to continue. No separate "after completion" action is needed — the design log IS the memory.

package/src/workflows/5-agentic-development/data/guides/FILE-INDEX.md

@@ -1,6 +1,6 @@
 # Agentic Development - File Index
 
-**Location**: `src/workflows/4-ux-design/agentic-development/`
+**Location**: `src/workflows/5-agentic-development/`
 
 ---
 

package/src/workflows/5-agentic-development/steps-a/step-01-define-question.md

@@ -115,7 +115,7 @@ If the time box expires, document what you found and what remains unexplored.
 Display: "**Select an Option:** [C] Continue to Step 2: Scan Codebase"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-a/step-02-scan-codebase.md

@@ -147,7 +147,7 @@ As you scan, note initial observations about:
 Display: "**Select an Option:** [C] Continue to Step 3: Map Architecture"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-a/step-03-map-architecture.md

@@ -152,7 +152,7 @@ Document patterns you observe:
 Display: "**Select an Option:** [C] Continue to Step 4: Document Findings"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-a/step-04-document-findings.md

@@ -193,7 +193,7 @@ Example:
 Save the document to the project's output location. If no output location is defined, save to:
 
 - `docs/architecture/` in the analyzed project, or
-- The dialog output folder if using the agent dialog system
+- The agent experiences folder for session insights
 
 ### 6. Verify Checklist
 
@@ -209,7 +209,7 @@ Save the document to the project's output location. If no output location is def
 Display: "**Select an Option:** [M] Return to Activity Menu"
 
 #### Menu Handling Logic:
-- IF M: Update agent dialog, then load, read entire file, then execute {activityWorkflowFile}
+- IF M: Update design log, then load, read entire file, then execute {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-d/step-01-scope-and-plan.md

@@ -123,7 +123,7 @@ Record the inventory, implementation order, and acceptance criteria in the dialo
 Display: "**Select an Option:** [C] Continue to Step 2: Setup Environment"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-d/step-02-setup-environment.md

@@ -134,7 +134,7 @@ Record the result:
 Display: "**Select an Option:** [C] Continue to Step 3: Implement"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-d/step-03-implement.md

@@ -142,7 +142,7 @@ Write clear commit messages that reference what was built. Do not accumulate lar
 Display: "**Select an Option:** [C] Continue to Step 4: Verify"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-d/step-04-verify.md

@@ -144,7 +144,7 @@ For projects using Puppeteer, follow the verification process in INLINE-TESTING-
 Display: "**Select an Option:** [C] Continue to Step 5: Finalize"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-d/step-05-finalize.md

@@ -147,7 +147,7 @@ Based on what was built, recommend next steps:
 Display: "**Select an Option:** [M] Return to Activity Menu"
 
 #### Menu Handling Logic:
-- IF M: Update agent dialog, then load, read entire file, then execute {activityWorkflowFile}
+- IF M: Update design log, then load, read entire file, then execute {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-e/step-01-scope-change.md

@@ -102,7 +102,7 @@ Categorize all affected areas:
 Display: "**Select an Option:** [C] Continue to Step 2: Analyze Impact"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-e/step-02-analyze-impact.md

@@ -104,7 +104,7 @@ Write a risk assessment in the dialog file:
 Display: "**Select an Option:** [C] Continue to Step 3: Plan Implementation"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-e/step-03-plan-implementation.md

@@ -112,7 +112,7 @@ Between steps, define what to check:
 Display: "**Select an Option:** [C] Continue to Step 4: Implement"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-e/step-04-implement.md

@@ -106,7 +106,7 @@ When the plan calls for feature flags:
 Display: "**Select an Option:** [C] Continue to Step 5: Verify and Document"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-e/step-05-verify-and-document.md

@@ -114,7 +114,7 @@ Comprehensive verification of all new and existing functionality, then document
 Display: "**Select an Option:** [M] Return to Activity Menu"
 
 #### Menu Handling Logic:
-- IF M: Update agent dialog, then load, read entire file, then execute {activityWorkflowFile}
+- IF M: Update design log, then load, read entire file, then execute {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-f/step-01-reproduce.md

@@ -103,7 +103,7 @@ If the bug cannot be reproduced:
 Display: "**Select an Option:** [C] Continue to Step 2: Investigate"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-f/step-02-investigate.md

@@ -105,7 +105,7 @@ Identify the root cause of the bug, not just the symptom.
 Display: "**Select an Option:** [C] Continue to Step 3: Fix"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-f/step-03-fix.md

@@ -98,7 +98,7 @@ Implement the minimal fix targeting the root cause.
 Display: "**Select an Option:** [C] Continue to Step 4: Verify"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-f/step-04-verify.md

@@ -101,7 +101,7 @@ Confirm the fix works and has not introduced regressions.
 Display: "**Select an Option:** [C] Continue to Step 5: Document"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-f/step-05-document.md

@@ -101,7 +101,7 @@ Document the bug, the fix, and create a clean PR.
 Display: "**Select an Option:** [M] Return to Activity Menu"
 
 #### Menu Handling Logic:
-- IF M: Update agent dialog, then load, read entire file, then execute {activityWorkflowFile}
+- IF M: Update design log, then load, read entire file, then execute {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES: