diff --git a/src/workflows/0-project-setup/steps/step-02-structure.md b/src/workflows/0-project-setup/steps/step-02-structure.md index 79f9387d0..7f4367c2e 100644 --- a/src/workflows/0-project-setup/steps/step-02-structure.md +++ b/src/workflows/0-project-setup/steps/step-02-structure.md @@ -157,14 +157,14 @@ Store all as `project_context` and `working_relationship` in outline. **Create folder structure:** 1. Create root folder: `{{root_folder}}/` 2. Create progress folder: `{{root_folder}}/_progress/` -3. Create agent dialogs folder: `{{root_folder}}/_progress/agent-dialogs/` +3. Create agent experiences folder: `{{root_folder}}/_progress/agent-experiences/` 4. Create phase folders (greenfield vs brownfield) 5. Create D-Design-System subfolders 6. Install folder guide files from templates **Generate `{{root_folder}}/_progress/wds-project-outline.yaml`** with all configuration values. -**Fill in `00-progress.md`** with initial Phase 0 entry. +**Fill in `00-design-log.md`** with initial Phase 0 entry. ### 11. Summary & Next Steps diff --git a/src/workflows/0-project-setup/templates/folder-guides/00-design-log.template.md b/src/workflows/0-project-setup/templates/folder-guides/00-design-log.template.md new file mode 100644 index 000000000..d875c789b --- /dev/null +++ b/src/workflows/0-project-setup/templates/folder-guides/00-design-log.template.md @@ -0,0 +1,59 @@ +# Design Log + +**Project:** {{project_name}} +**Started:** {{date}} +**Method:** Whiteport Design Studio (WDS) + +--- + +## Backlog + +> Business-value items. Add links to detail files if needed. + +- [ ] Complete product brief — Phase 1 +- [ ] Define trigger map — Phase 2 +- [ ] Create user scenarios — Phase 3 + +--- + +## Current + +| Task | Started | Agent | +|------|---------|-------| +| — | — | — | + +**Rules:** Mark what you start. Complete it when done (move to Log). One task at a time per agent. + +--- + +## Design Loop Status + +> Per-page design progress. Updated by agents at every design transition. + +| Scenario | Step | Page | Status | Updated | +|----------|------|------|--------|---------| + +**Status values:** `discussed` → `wireframed` → `specified` → `explored` → `building` → `built` → `approved` | `removed` + +**How to use:** +- **Append a row** when a page reaches a new status (do not overwrite — latest row per page is current status) +- **Read on startup** to see where the project stands and what to suggest next + +--- + +## Log + +### {{date}} — Project initialized (Phase 0) +- Type: {{greenfield/brownfield}} +- Complexity: {{product_complexity}} +- Tech stack: {{tech_stack}} + +--- + +## About This Folder + +- **This file** — Single source of truth for project progress +- **agent-experiences/** — Compressed insights from design discussions (dated files) +- **wds-project-outline.yaml** — Project configuration from Phase 0 setup + +**Do not modify `wds-project-outline.yaml`** — it is the source of truth for project configuration. diff --git a/src/workflows/0-project-setup/templates/folder-guides/00-progress.template.md b/src/workflows/0-project-setup/templates/folder-guides/00-progress.template.md deleted file mode 100644 index 5d8d51b45..000000000 --- a/src/workflows/0-project-setup/templates/folder-guides/00-progress.template.md +++ /dev/null @@ -1,72 +0,0 @@ -# Design Process Log - -> Track progress, decisions, and agent handoffs across the design process. - -**Project:** {{project_name}} -**Started:** {{date}} -**Method:** Whiteport Design Studio (WDS) - ---- - -## About This Folder - -The `_progress` folder is the memory of your design process. It tracks what happened, when, and why — so any agent or human can pick up where you left off. - -**Contents:** -- **This file** — Design log with phase progress and key decisions -- **agent-dialogs/** — Conversation records between agents and humans, persisted across sessions -- **wds-project-outline.yaml** — Project configuration from Phase 0 setup - -**Learn more:** WDS Course Module 02 (Installation & Setup), Lesson 4: WDS Initialization - ---- - -## For Agents - -**Your dialog files go in `agent-dialogs/`.** Name them: `YYYY-MM-DD-agent-topic.md` - -When you complete a phase milestone, add an entry to the Progress section below. When the user makes a key decision, record it in Key Decisions. - -**Do not modify `wds-project-outline.yaml`** — it is the source of truth for project configuration. - ---- - -## Progress - -### {{date}} — Project Initialized (Phase 0) - -**Configuration:** -- Type: {{greenfield/brownfield}} -- Complexity: {{product_complexity}} -- Tech Stack: {{tech_stack}} -- Brief Level: {{brief_level}} - -**Next:** Phase 1 — Product Brief - ---- - -## Design Loop Status - -> Per-page design progress. Updated by agents at every design transition. - -| Scenario | Step | Page | Status | Updated | -|----------|------|------|--------|---------| - -**Status values:** `discussed` → `wireframed` → `specified` → `explored` → `building` → `built` → `approved` | `removed` - -**How agents use this table:** -- **Append a row** when a page reaches a new status (do not overwrite — the latest row per page is the current status) -- **Read on startup** to determine where the project stands and what to suggest next -- **The latest row per Step** is the current status for that page - ---- - -## Key Decisions - -| Date | Decision | Context | Made By | -|------|----------|---------|---------| -| {{date}} | Project initialized | Phase 0 setup | {{agent}} | - ---- - -_Updated using Whiteport Design Studio (WDS) methodology_ diff --git a/src/workflows/1-project-brief/steps-c/step-35-update-design-log.md b/src/workflows/1-project-brief/steps-c/step-35-update-design-log.md index 79b05f8d1..4ebf57330 100644 --- a/src/workflows/1-project-brief/steps-c/step-35-update-design-log.md +++ b/src/workflows/1-project-brief/steps-c/step-35-update-design-log.md @@ -49,7 +49,7 @@ Document Phase 1 completion in the project design log - the project's memory. ### 1. Read the Current Log -Read `{output_folder}/_progress/00-progress.md` to understand existing entries and format. +Read `{output_folder}/_progress/00-design-log.md` to understand existing entries and format. ### 2. Append Progress Entry diff --git a/src/workflows/2-trigger-mapping/steps-c/step-09e-update-design-log.md b/src/workflows/2-trigger-mapping/steps-c/step-09e-update-design-log.md index 66543a948..83f872cbf 100644 --- a/src/workflows/2-trigger-mapping/steps-c/step-09e-update-design-log.md +++ b/src/workflows/2-trigger-mapping/steps-c/step-09e-update-design-log.md @@ -42,7 +42,7 @@ Document Phase 2: Trigger Mapping completion in the project design log, listing ## EXECUTION PROTOCOLS: - 🎯 Read current design log and append progress entry -- 💾 Update {output_folder}/_progress/00-progress.md +- 💾 Update {output_folder}/_progress/00-design-log.md - 📖 List all artifacts and key decisions specifically - 🚫 Do not overwrite existing entries @@ -57,7 +57,7 @@ Document Phase 2: Trigger Mapping completion in the project design log, listing ### 1. Read Current Log -Read `{output_folder}/_progress/00-progress.md` to understand existing entries and format. +Read `{output_folder}/_progress/00-design-log.md` to understand existing entries and format. ### 2. Append Progress Entry @@ -106,7 +106,7 @@ If no significant decisions were made, skip this section. - Summary is specific, not generic - Key decisions recorded (if any) -Output: "Design log updated. Phase 2: Trigger Mapping documented in _progress/00-progress.md" +Output: "Design log updated. Phase 2: Trigger Mapping documented in _progress/00-design-log.md" ### 5. Present MENU OPTIONS diff --git a/src/workflows/3-scenarios/steps-c/step-08-update-design-log.md b/src/workflows/3-scenarios/steps-c/step-08-update-design-log.md index 984ed518c..078347675 100644 --- a/src/workflows/3-scenarios/steps-c/step-08-update-design-log.md +++ b/src/workflows/3-scenarios/steps-c/step-08-update-design-log.md @@ -55,7 +55,7 @@ Document Phase 3 completion in the project design log, recording all artifacts c ### 1. Read the Current Log -Read `{output_folder}/_progress/00-progress.md` to understand existing entries and format. +Read `{output_folder}/_progress/00-design-log.md` to understand existing entries and format. ### 2. Append Progress Entry diff --git a/src/workflows/4-ux-design/data/guides/NANO-BANANA-PROMPT-GUIDE.md b/src/workflows/4-ux-design/data/guides/NANO-BANANA-PROMPT-GUIDE.md index acf0d6ce8..445a6e94c 100644 --- a/src/workflows/4-ux-design/data/guides/NANO-BANANA-PROMPT-GUIDE.md +++ b/src/workflows/4-ux-design/data/guides/NANO-BANANA-PROMPT-GUIDE.md @@ -393,7 +393,7 @@ white cards with subtle shadow, warm authentic imagery. - **Only content swaps:** image descriptions, headlines, service lists, section-specific text - **Sequential generation:** Generate one at a time, quick-review each, flag outliers for iteration - **Use `flash` model tier** for batch runs (faster, cheaper) — save `pro` for the template page -- **Track everything** in the batch agent dialog for reproducibility +- **Track everything** in the agent experience file for reproducibility --- diff --git a/src/workflows/4-ux-design/steps-c/step-01-exploration.md b/src/workflows/4-ux-design/steps-c/step-01-exploration.md index 1db754828..71f1070a1 100644 --- a/src/workflows/4-ux-design/steps-c/step-01-exploration.md +++ b/src/workflows/4-ux-design/steps-c/step-01-exploration.md @@ -104,7 +104,7 @@ Now they're on [page name]. **If the user decides to eliminate the step:** 1. Update the scenario outline (remove/merge the step) 2. Remove the page folder -3. Append status `removed` to `{output_folder}/_progress/00-progress.md` Design Loop Status table: +3. Append status `removed` to `{output_folder}/_progress/00-design-log.md` Design Loop Status table: `| [Scenario slug] | [NN.X] | [Page name] | removed | [YYYY-MM-DD] |` 4. Loop back to step 2 (Set the Scene) for the next page @@ -136,7 +136,7 @@ When the discussion feels complete, summarize: Update the page specification with discussion findings (fill empty sections in the existing page spec file) -Update design log: append row with status `discussed` to `{output_folder}/_progress/00-progress.md` (see section 9 for exact format) +Update design log: append row with status `discussed` to `{output_folder}/_progress/00-design-log.md` (see section 9 for exact format) ### 7. Visualization Question @@ -173,7 +173,7 @@ Let me know when you've saved the image. Wait for user confirmation that the PNG is saved. SYNC SPEC: Update the page specification to match the agreed wireframe. Add a reference to the PNG in the spec's visual reference section. The spec is the source of truth — never implement from wireframe directly. -Update design log: append row with status `wireframed` to `{output_folder}/_progress/00-progress.md` (see section 9) +Update design log: append row with status `wireframed` to `{output_folder}/_progress/00-design-log.md` (see section 9) See `{designLoopGuide}` for the full design loop reference. Then proceed to the **Page Transition** (step 8). @@ -187,7 +187,7 @@ Then proceed to the **Page Transition** (step 8). #### IF 3 (Specification without sketch): Proceed to specification activity (steps-p/) with the discussion findings -Update design log: append row with status `specified` to `{output_folder}/_progress/00-progress.md` (see section 9) +Update design log: append row with status `specified` to `{output_folder}/_progress/00-design-log.md` (see section 9) Then proceed to the **Page Transition** (step 8). @@ -244,22 +244,22 @@ If none exist (simple page, single-device platform): - **Next logical step:** Proceed to the appropriate activity (specification → steps-p/, responsive → diff file, build → Phase 5 prototyping) - **Explore next scenario step:** Loop back to step 2 (Set the Scene) for the next page in the scenario's shortest path. If no more pages, show "All pages in this scenario are designed!" -- **Design log:** Always append a status row to `{output_folder}/_progress/00-progress.md` before presenting transition options (see section 9) -- **Session plan:** Check off the completed item in the active agent dialog. If all plan items are done, note it in the transition: "That's everything we planned! Want to continue or wrap up?" +- **Design log:** Always append a status row to `{output_folder}/_progress/00-design-log.md` before presenting transition options (see section 9) +- **Current task:** Update the Current table in the design log — remove completed task, add next task if continuing #### 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 — update the design log with current status AND set the agent dialog to `status: paused` +- The user can always say "stop" to pause and return later — update the design log with current status and clear the Current table ### 9. Design Log Updates -At every transition, append a row to the **Design Loop Status** table in `{output_folder}/_progress/00-progress.md`. +At every transition, append a row to the **Design Loop Status** table in `{output_folder}/_progress/00-design-log.md`. **How to update (exact procedure):** -1. Open `{output_folder}/_progress/00-progress.md` +1. Open `{output_folder}/_progress/00-design-log.md` 2. Find the `## Design Loop Status` section 3. Append a new row to the table: diff --git a/src/workflows/4-ux-design/steps-p/step-09-generate-spec.md b/src/workflows/4-ux-design/steps-p/step-09-generate-spec.md index 320f50707..d4eb4b184 100644 --- a/src/workflows/4-ux-design/steps-p/step-09-generate-spec.md +++ b/src/workflows/4-ux-design/steps-p/step-09-generate-spec.md @@ -99,7 +99,7 @@ Fill in all sections with data collected: ### 2. Update Design Log -Append a row with status `specified` to the Design Loop Status table in `{output_folder}/_progress/00-progress.md`: +Append a row with status `specified` to the Design Loop Status table in `{output_folder}/_progress/00-design-log.md`: ``` | [Scenario slug] | [NN.X] | [Page name] | specified | [YYYY-MM-DD] | diff --git a/src/workflows/4-ux-design/steps-w/step-01-visual-approach.md b/src/workflows/4-ux-design/steps-w/step-01-visual-approach.md index 86407a1b0..9bb5e7736 100644 --- a/src/workflows/4-ux-design/steps-w/step-01-visual-approach.md +++ b/src/workflows/4-ux-design/steps-w/step-01-visual-approach.md @@ -82,8 +82,7 @@ How would you like to create the visual design? ### 3. Setup Gate (Nano Banana only) If user selects [N]: -1. Check for existing agent dialog for this page in `{output_folder}/_progress/agent-dialogs/` - - If active dialog found: offer to resume previous visual generation session +1. Check the design log at `{output_folder}/_progress/00-design-log.md` for previous visual generation entries for this page 2. If first time using Nano Banana in this project: - Route to `step-00-nb-setup.md` to verify MCP connection - Return here after verification succeeds diff --git a/src/workflows/4-ux-design/steps-w/step-02w-nb-compose-prompt.md b/src/workflows/4-ux-design/steps-w/step-02w-nb-compose-prompt.md index df5fae11b..1cbbba650 100644 --- a/src/workflows/4-ux-design/steps-w/step-02w-nb-compose-prompt.md +++ b/src/workflows/4-ux-design/steps-w/step-02w-nb-compose-prompt.md @@ -39,12 +39,12 @@ Translate a page specification into an effective AI image generation prompt that - 🎯 Focus on composing an effective generation prompt from page spec data - 🚫 FORBIDDEN to generate without user confirming creative direction - 💬 Approach: Extract, present, let user override, compose, generate, iterate -- 📋 Track all generations in agent dialog file +- 📋 Track all generations in agent experience file ## EXECUTION PROTOCOLS: - 🎯 Extract image descriptions, gather creative direction, compose prompt, generate -- 💾 Log all generations to agent dialog file +- 💾 Log all generations to agent experience file - 📖 Reference NANO-BANANA-PROMPT-GUIDE.md for compression strategy - 🚫 FORBIDDEN to skip creative direction step @@ -57,24 +57,15 @@ Translate a page specification into an effective AI image generation prompt that ## Sequence of Instructions (Do not deviate, skip, or optimize) -### 0. Start Agent Dialog +### 0. Start Generation Log -Create (or resume) an agent dialog file to track this visual generation session. +Create an agent experience file to track this visual generation session. -**File location:** `{output_folder}/_progress/agent-dialogs/` -**Naming:** `{date}-freya-visual-{page-name}.md` -**Example:** `2026-02-19-freya-visual-1.1-hem.md` +**File location:** `{output_folder}/_progress/agent-experiences/` +**Naming:** `{date}-visual-{page-name}.md` +**Example:** `2026-02-19-visual-1.1-hem.md` ```markdown ---- -status: active -agent: Freya -topic: Visual generation for {page-name} -created: {timestamp} -last_updated: {timestamp} -context_summary: Generating visual designs for {page-name} using Nano Banana ---- - # Visual Generation: {page-name} ## Inputs @@ -92,7 +83,7 @@ context_summary: Generating visual designs for {page-name} using Nano Banana {each generation appended here in step H} ``` -**If an active dialog exists** for this page, resume it -- load previous context, creative direction, and generation history. +**If a previous generation log exists** for this page, read it for context — previous creative direction, successful prompts, and lessons learned. ### A. Load Inputs @@ -253,7 +244,7 @@ Call `mcp__nanobanana__generate_image` with the assembled prompt, system instruc Present the result to the user. -**Log to agent dialog:** +**Log to agent experience file:** ```markdown ### Generation {N} -- {timestamp} @@ -274,7 +265,7 @@ Present the result to the user. **User feedback:** {filled after review} ``` -Update the dialog `last_updated` timestamp. +Update the agent experience file. ### I. Iterate @@ -339,19 +330,19 @@ ONLY WHEN the user has accepted a generated visual and selected an option from t ### ✅ SUCCESS: -- Agent dialog created or resumed +- Generation log created in agent experiences - Image descriptions extracted from spec - User creative direction captured - Prompt composed within 8192 char limit - Image generated and presented -- Generation logged to agent dialog +- Generation logged to agent experience file - User accepted or iterated to satisfaction ### ❌ SYSTEM FAILURE: - Generating without user creative direction - Exceeding prompt character limit -- Not logging generations to agent dialog +- Not logging generations to agent experience file - Not presenting iteration options - Skipping reference image auto-detection diff --git a/src/workflows/4-ux-design/steps-w/step-03-review-integrate.md b/src/workflows/4-ux-design/steps-w/step-03-review-integrate.md index ebc442992..28d3683af 100644 --- a/src/workflows/4-ux-design/steps-w/step-03-review-integrate.md +++ b/src/workflows/4-ux-design/steps-w/step-03-review-integrate.md @@ -87,7 +87,7 @@ Store visual artifact in the appropriate location: - **Image assets (photos/illustrations):** `{output_folder}/D-Design-System/01-Visual-Design/design-concepts/` (move to `02-Assets/images/` when finalized) - **Legacy path:** `{output_folder}/C-UX-Scenarios/[scenario]/visuals/` (if project uses older folder structure) -**Update the agent dialog** with the accepted result and save path. +**Update the agent experience file** with the accepted result and save path. ### 5. Present MENU OPTIONS @@ -117,14 +117,14 @@ ONLY WHEN the user selects an option from the menu and the visual has been integ - Design decisions documented - Page specification updated with visual reference - Visual artifact saved to correct location -- Agent dialog updated with accepted result +- Agent experience file updated with accepted result ### ❌ SYSTEM FAILURE: - Skipping user feedback - Not integrating into page specification - Not saving visual artifact -- Not updating agent dialog +- Not updating agent experience file - Relying on AI-generated text in images for content accuracy **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/workflows/4-ux-design/workflow-conceptualize.md b/src/workflows/4-ux-design/workflow-conceptualize.md index 505309b2b..ae0eb82a2 100644 --- a/src/workflows/4-ux-design/workflow-conceptualize.md +++ b/src/workflows/4-ux-design/workflow-conceptualize.md @@ -13,12 +13,7 @@ description: 'Creative dialog for page design — discuss what each page needs, ## 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 diff --git a/src/workflows/4-ux-design/workflow-design-system.md b/src/workflows/4-ux-design/workflow-design-system.md index 03a938d42..0b8f04a0e 100644 --- a/src/workflows/4-ux-design/workflow-design-system.md +++ b/src/workflows/4-ux-design/workflow-design-system.md @@ -13,12 +13,7 @@ description: 'Define, update, and review design system components used across pa ## 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. ## Extraction Rules @@ -60,6 +55,6 @@ Execute steps in `./steps-m/`: ## AFTER COMPLETION -1. Append a progress entry to `{output_folder}/_progress/00-progress.md` under `## Progress`: +1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`: `### [date] — Design System: [components extracted/updated]` 2. Suggest next action based on the adaptive dashboard diff --git a/src/workflows/4-ux-design/workflow-dream.md b/src/workflows/4-ux-design/workflow-dream.md index 48797911b..686aa17c9 100644 --- a/src/workflows/4-ux-design/workflow-dream.md +++ b/src/workflows/4-ux-design/workflow-dream.md @@ -13,12 +13,7 @@ description: 'The agent creates a complete scenario flow autonomously, then pres ## 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 @@ -67,7 +62,7 @@ In Dream mode: - **OVERRIDE** all "halt and wait" rules — auto-proceed after completing each step - **OVERRIDE** "NEVER generate content without user input" — generate based on context and WDS patterns - **DO NOT** display menus or wait for menu selections between steps -- **DO** still save outputs and update agent dialog at each step +- **DO** still save outputs and update the design log at each step - **DO** still follow the step's actual instructions for what to generate - The user can type **"stop"** or **"pause"** at any time to interrupt and switch to Suggest mode @@ -79,7 +74,7 @@ In Dream mode: ## DESIGN LOG REPORTING -In Dream mode, the agent updates the design log autonomously at each page completion. Append to the Design Loop Status table in `{output_folder}/_progress/00-progress.md`: +In Dream mode, the agent updates the design log autonomously at each page completion. 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] | diff --git a/src/workflows/4-ux-design/workflow-handover.md b/src/workflows/4-ux-design/workflow-handover.md index 779739038..175b5ac1d 100644 --- a/src/workflows/4-ux-design/workflow-handover.md +++ b/src/workflows/4-ux-design/workflow-handover.md @@ -13,11 +13,7 @@ description: Package complete testable flows and hand off to development ## INITIALIZATION -### Agent Dialog Gate - -1. Check `{output_folder}/_progress/agent-dialogs/` for pending handover dialogs -2. If none exists, suggest creating one for this handover -3. If exists, load and resume +Read design log at `{output_folder}/_progress/00-design-log.md` before starting. --- @@ -43,6 +39,6 @@ Execute steps in `./steps-h/`: ## AFTER COMPLETION -1. Append a progress entry to `{output_folder}/_progress/00-progress.md` under `## Progress`: +1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`: `### [date] — Design Delivery: [what was packaged]` 2. Suggest next action: Phase 5 prototyping or next scenario diff --git a/src/workflows/4-ux-design/workflow-sketch.md b/src/workflows/4-ux-design/workflow-sketch.md index 199392382..a8ce32db0 100644 --- a/src/workflows/4-ux-design/workflow-sketch.md +++ b/src/workflows/4-ux-design/workflow-sketch.md @@ -13,12 +13,7 @@ description: 'Analyze user-provided sketches (photos, screenshots, wireframes) a ## 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 diff --git a/src/workflows/4-ux-design/workflow-specify.md b/src/workflows/4-ux-design/workflow-specify.md index 59f3d484d..4b6982992 100644 --- a/src/workflows/4-ux-design/workflow-specify.md +++ b/src/workflows/4-ux-design/workflow-specify.md @@ -13,12 +13,7 @@ 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 diff --git a/src/workflows/4-ux-design/workflow-suggest.md b/src/workflows/4-ux-design/workflow-suggest.md index 549d0974e..6c7a55adb 100644 --- a/src/workflows/4-ux-design/workflow-suggest.md +++ b/src/workflows/4-ux-design/workflow-suggest.md @@ -13,12 +13,7 @@ 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 @@ -73,7 +68,7 @@ Execute steps in `./steps-s/`: ### Design Log Update -After finishing a page specification, append to the Design Loop Status table in `{output_folder}/_progress/00-progress.md`: +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] | ``` diff --git a/src/workflows/4-ux-design/workflow-validate.md b/src/workflows/4-ux-design/workflow-validate.md index fd4497e30..569e148d4 100644 --- a/src/workflows/4-ux-design/workflow-validate.md +++ b/src/workflows/4-ux-design/workflow-validate.md @@ -13,11 +13,7 @@ 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 @@ -59,6 +55,6 @@ Save validation report to `{output_folder}/_progress/validation-report.md` ## AFTER COMPLETION -1. Append a progress entry to `{output_folder}/_progress/00-progress.md` under `## Progress`: +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 diff --git a/src/workflows/4-ux-design/workflow-visual.md b/src/workflows/4-ux-design/workflow-visual.md index 4e4d10687..500dc202b 100644 --- a/src/workflows/4-ux-design/workflow-visual.md +++ b/src/workflows/4-ux-design/workflow-visual.md @@ -13,12 +13,7 @@ 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 @@ -49,6 +44,6 @@ Execute steps in `./steps-w/`: ## AFTER COMPLETION -1. Append a progress entry to `{output_folder}/_progress/00-progress.md` under `## Progress`: +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) diff --git a/src/workflows/4-ux-design/workflow.md b/src/workflows/4-ux-design/workflow.md index 39d3d065e..406a0b596 100644 --- a/src/workflows/4-ux-design/workflow.md +++ b/src/workflows/4-ux-design/workflow.md @@ -40,13 +40,15 @@ 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 -Check `{output_folder}/_progress/agent-dialogs/` for agent dialogs with `status: active` and `agent: Freya`. +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 an active dialog exists:** Read it. The dialog contains the session plan — what pages the user intended to work on and how far they got. Use this to drive the dashboard. - -**If no active dialog exists:** You'll create one after the user chooses what to work on (see step 4c). +If the file doesn't exist, guide the user to run Phase 0 setup first. ### 3. Mode Determination @@ -56,48 +58,53 @@ Check `{output_folder}/_progress/agent-dialogs/` for agent dialogs with `status: ### 4. Adaptive Dashboard -Read both sources: -1. **Agent dialog** (the plan) — what was the user working on? -2. **Design log** (`{output_folder}/_progress/00-progress.md`) — what status did each page reach? -3. **Scenario files** from `{output_folder}/C-UX-Scenarios/` — full page inventory +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 #### 4a. Build Status Overview -For each scenario, determine per-page status from the Design Loop Status table in the design log. The **latest row per page** is the current status. +For each scenario, determine per-page status from the **Design Loop Status** table. The latest row per page is the current status. + +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 an active dialog with a session plan exists:** - -Read the plan's checklist. Compare against the design log. Present what's done and what's left: +**If a task is listed in Current:** **Welcome back! Here's where we left off:** -**Session plan:** [topic from dialog] +**In progress:** [task from Current table] -| Step | Page | Plan | Status | -|------|------|------|--------| -| [NN.1] | [page name] | [target] | [current] ✓ | -| [NN.2] | [page name] | [target] | [current] ← next | -| [NN.3] | [page name] | [target] | — | +**Design status:** +| Scenario | Page | Status | +|----------|------|--------| +| [NN] | [page name] | [current status] | +| ... | ... | ... | -I'd suggest we continue with **[next unchecked item from the plan]**. -Pick up there, or change plans? +I'd suggest we continue with **[the in-progress task]**. +Pick up there, or change direction? -**If the session plan is complete** (all items checked): +**If Current is empty but Backlog has items:** -**Session plan complete!** +**Ready to continue!** -Everything we planned is done. What would you like to do next? +**Next from backlog:** +- [ ] [first unchecked backlog item] +- [ ] [second unchecked backlog item] -1. **Continue with [next scenario step / next scenario]** — keep the momentum -2. **Start a new session plan** — pick different pages to work on +**Design status:** +| Scenario | Page | Status | +|----------|------|--------| +| [NN] | [page name] | [latest status] | + +I'd suggest we start with **[first backlog item]**. Sound good? -**If no active dialog exists** (fresh start): +**If both Current and Backlog are empty** (fresh project): **Ready to start designing!** @@ -108,44 +115,22 @@ Your scenarios: | 01 | [Name] | [total] | [done] | | 02 | [Name] | [total] | [done] | -Which scenario shall we work on? I'll set up a session plan. +Which scenario shall we work on? -#### 4c. Create or Update Session Plan +#### 4c. Design Log Updates -**When starting a new session**, create an agent dialog file: +**When starting work:** Move the task from Backlog to Current (or add a new row to Current). -**File:** `{output_folder}/_progress/agent-dialogs/YYYY-MM-DD-freya-[topic].md` +**At each transition:** Append a row to the Design Loop Status table with the new status. Update the Log section with what was accomplished. -```markdown ---- -status: active -agent: Freya -topic: [what the user wants to work on] -created: [date] -last_updated: [date] ---- +**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. -# [Topic] +#### 4d. Agent Experiences -## Session Plan +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. -| # | Page | Target Status | Done | -|---|------|---------------|------| -| 1 | [NN.X page name] | [discussed/wireframed/specified/etc.] | [ ] | -| 2 | [NN.X page name] | [discussed/wireframed/specified/etc.] | [ ] | - -## Decisions Made - -| # | Decision | Rationale | -|---|----------|-----------| -``` - -**At each transition:** Update the dialog — check off completed items, add decisions, update `last_updated`. - -**When the plan is complete or user stops:** Set `status: complete` or `status: paused`. The next session will find no active dialog and offer to start fresh or resume. - -#### 4d. User Response Handling +#### 4e. User Response Handling - **User accepts suggestion** → Load the appropriate activity workflow and continue - **User picks a different page or scenario** → Update the session plan and continue diff --git a/src/workflows/5-agentic-development/workflow-acceptance-testing.md b/src/workflows/5-agentic-development/workflow-acceptance-testing.md index 3181f039c..c9fd3cd4e 100644 --- a/src/workflows/5-agentic-development/workflow-acceptance-testing.md +++ b/src/workflows/5-agentic-development/workflow-acceptance-testing.md @@ -42,7 +42,7 @@ Execute steps in `./steps-t/`: ## DESIGN LOG REPORTING POINT -When all tests pass and the user approves, append to the Design Loop Status table in `{output_folder}/_progress/00-progress.md`: +When all tests pass and the user approves, append to the Design Loop Status table in `{output_folder}/_progress/00-design-log.md`: ``` | [Scenario slug] | [NN.X] | [Page name] | approved | [YYYY-MM-DD] | diff --git a/src/workflows/5-agentic-development/workflow-analysis.md b/src/workflows/5-agentic-development/workflow-analysis.md index 222977743..74f033001 100644 --- a/src/workflows/5-agentic-development/workflow-analysis.md +++ b/src/workflows/5-agentic-development/workflow-analysis.md @@ -59,6 +59,6 @@ Execute steps in `./steps-a/`: ## AFTER COMPLETION -1. Append a progress entry to `{output_folder}/_progress/00-progress.md` under `## Progress`: +1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`: `### [date] — Analysis: [what was analyzed, key findings]` 2. Suggest next action: feed into development, reverse engineer further, or start prototyping diff --git a/src/workflows/5-agentic-development/workflow-bugfixing.md b/src/workflows/5-agentic-development/workflow-bugfixing.md index 05256d3bc..d183bd043 100644 --- a/src/workflows/5-agentic-development/workflow-bugfixing.md +++ b/src/workflows/5-agentic-development/workflow-bugfixing.md @@ -62,6 +62,6 @@ Execute steps in `./steps-f/`: ## AFTER COMPLETION -1. Append a progress entry to `{output_folder}/_progress/00-progress.md` under `## Progress`: +1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`: `### [date] — Bugfix: [what was fixed]` 2. Suggest re-running acceptance testing (Phase 5 [T]) to verify the fix diff --git a/src/workflows/5-agentic-development/workflow-development.md b/src/workflows/5-agentic-development/workflow-development.md index c44fe830b..ffb1d0b9e 100644 --- a/src/workflows/5-agentic-development/workflow-development.md +++ b/src/workflows/5-agentic-development/workflow-development.md @@ -75,7 +75,7 @@ Execute steps in `./steps-d/`: ## DESIGN LOG REPORTING POINTS -Append to the Design Loop Status table in `{output_folder}/_progress/00-progress.md`: +Append to the Design Loop Status table in `{output_folder}/_progress/00-design-log.md`: **On entry (step 01 complete):** `| [Scenario slug] | [NN.X] | [Page name] | building | [YYYY-MM-DD] |` **On completion (step 05 approved):** `| [Scenario slug] | [NN.X] | [Page name] | built | [YYYY-MM-DD] |` diff --git a/src/workflows/5-agentic-development/workflow-evolution.md b/src/workflows/5-agentic-development/workflow-evolution.md index 78d10aa6b..dbb8d25a3 100644 --- a/src/workflows/5-agentic-development/workflow-evolution.md +++ b/src/workflows/5-agentic-development/workflow-evolution.md @@ -62,6 +62,6 @@ Execute steps in `./steps-e/`: ## AFTER COMPLETION -1. Append a progress entry to `{output_folder}/_progress/00-progress.md` under `## Progress`: +1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`: `### [date] — Evolution: [what was evolved/added]` 2. Suggest acceptance testing (Phase 5 [T]) to validate the changes diff --git a/src/workflows/5-agentic-development/workflow-prototyping.md b/src/workflows/5-agentic-development/workflow-prototyping.md index ec19844df..4b72e16c2 100644 --- a/src/workflows/5-agentic-development/workflow-prototyping.md +++ b/src/workflows/5-agentic-development/workflow-prototyping.md @@ -61,7 +61,7 @@ Execute steps in `./steps-p/`: ## DESIGN LOG REPORTING POINTS -This workflow has TWO reporting points. Both append to the Design Loop Status table in `{output_folder}/_progress/00-progress.md`: +This workflow has TWO reporting points. Both append to the Design Loop Status table in `{output_folder}/_progress/00-design-log.md`: **1. On entry (step 1 complete):** Append status `building` ``` diff --git a/src/workflows/5-agentic-development/workflow-reverse-engineering.md b/src/workflows/5-agentic-development/workflow-reverse-engineering.md index a1cca6627..ccd1b34bc 100644 --- a/src/workflows/5-agentic-development/workflow-reverse-engineering.md +++ b/src/workflows/5-agentic-development/workflow-reverse-engineering.md @@ -63,6 +63,6 @@ Execute steps in `./steps-r/`: ## AFTER COMPLETION -1. Append a progress entry to `{output_folder}/_progress/00-progress.md` under `## Progress`: +1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`: `### [date] — Reverse Engineering: [what was extracted]` 2. Suggest next action: feed specs into prototyping, analyze further, or start development diff --git a/tools/cli/lib/installer.js b/tools/cli/lib/installer.js index df354a173..ab853f48c 100644 --- a/tools/cli/lib/installer.js +++ b/tools/cli/lib/installer.js @@ -302,7 +302,7 @@ class Installer { // Create _progress folder for agent tracking const progressPath = path.join(docsPath, '_progress'); await fs.ensureDir(progressPath); - await fs.ensureDir(path.join(progressPath, 'agent-dialogs')); + await fs.ensureDir(path.join(progressPath, 'agent-experiences')); } }