Complete agent-dialog removal across all phases, workflows, and step files
Replace Agent Dialog Gate with Design Log entry point in all 29 activity workflows (phases 2-8). Replace "Update agent dialog" with "Update design log" in 90+ step files across phases 5, 7, and 8. Update data files, guides, presentations, and templates to reference design log instead of agent dialogs. Only the deprecated _agent-dialogs/ archive folder retains original references. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
a4ac572451
commit
19e82cd3cb
|
|
@ -1,14 +1,16 @@
|
|||
# Freya's Agentic Development Guide
|
||||
|
||||
**When to load:** When implementing features, building prototypes, or fixing bugs through structured agent dialogs
|
||||
**When to load:** When implementing features, building prototypes, or fixing bugs through structured development
|
||||
|
||||
> **Note:** Agent dialogs have been replaced by the Design Log system. Use `_progress/00-design-log.md` for state tracking and `_progress/agent-experiences/` for session insights.
|
||||
|
||||
---
|
||||
|
||||
## Core Principle
|
||||
|
||||
**Agentic Development uses structured dialogs to build incrementally with full traceability.**
|
||||
**Agentic Development builds incrementally with full traceability via the design log.**
|
||||
|
||||
Agent Dialogs bridge the gap between specifications and working code. Each step is self-contained, allowing fresh context while maintaining continuity.
|
||||
The design log bridges the gap between specifications and working code. Each step is self-contained, allowing fresh context while maintaining continuity.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -23,7 +25,7 @@ Agentic Development is a **workflow approach** that produces various outputs:
|
|||
| **Bug Fixes** | Structured debugging and fixing | Issue resolution |
|
||||
| **Design Exploration** | Exploring visual/UX directions | Creative iteration |
|
||||
|
||||
**Key Insight:** By structuring work into documented dialog folders, we create:
|
||||
**Key Insight:** By structuring work with a design log and experience records, we create:
|
||||
- **Isolation** — Each step can run in a fresh context
|
||||
- **Traceability** — Clear record of what was planned and executed
|
||||
- **Replayability** — Instructions can be rerun if needed
|
||||
|
|
@ -33,14 +35,14 @@ Agentic Development is a **workflow approach** that produces various outputs:
|
|||
|
||||
## Agent Startup Protocol
|
||||
|
||||
**When awakened, always check for pending dialogs:**
|
||||
**When awakened, always check the design log:**
|
||||
|
||||
```
|
||||
1. Check: {output_folder}/_progress/agent-dialogs/
|
||||
2. Find dialogs where:
|
||||
- Status = "Not Started" or "In Progress"
|
||||
- Agent matches the awakened agent
|
||||
3. Present pending dialogs to user
|
||||
1. Read: {output_folder}/_progress/00-design-log.md
|
||||
2. Check Current and Backlog sections for:
|
||||
- Items in progress
|
||||
- Items ready to start
|
||||
3. Present current state to user
|
||||
```
|
||||
|
||||
This ensures no captured work is forgotten.
|
||||
|
|
@ -49,14 +51,14 @@ This ensures no captured work is forgotten.
|
|||
|
||||
## The Bridge Role
|
||||
|
||||
Agent Dialogs bridge **specifications** and **development**:
|
||||
The design log bridges **specifications** and **development**:
|
||||
|
||||
```
|
||||
┌─────────────────────┐ ┌─────────────────────┐ ┌─────────────────────┐
|
||||
│ SPECIFICATION │ │ AGENT DIALOG │ │ DEVELOPMENT │
|
||||
│ SPECIFICATION │ │ DESIGN LOG │ │ DEVELOPMENT │
|
||||
│ │ │ │ │ │
|
||||
│ • What to build │────────▶│ • What's in scope │────────▶│ • How to build │
|
||||
│ • Object IDs │ │ • Step breakdown │ │ • Code files │
|
||||
│ • Object IDs │ │ • Current/Backlog │ │ • Code files │
|
||||
│ • Requirements │ │ • Traceability │ │ • Components │
|
||||
│ • Translations │ │ • Progress tracking │ │ • Tests │
|
||||
└─────────────────────┘ └─────────────────────┘ └─────────────────────┘
|
||||
|
|
@ -64,20 +66,18 @@ Agent Dialogs bridge **specifications** and **development**:
|
|||
of Truth Layer
|
||||
```
|
||||
|
||||
**The specification is the single source of truth.** Dialogs do not duplicate spec content — they map implementation tasks to spec sections via Object IDs.
|
||||
**The specification is the single source of truth.** The design log does not duplicate spec content — it maps implementation tasks to spec sections via Object IDs.
|
||||
|
||||
---
|
||||
|
||||
## Dialog Folder Structure
|
||||
## Progress Folder Structure
|
||||
|
||||
```
|
||||
{output_folder}/_progress/agent-dialogs/
|
||||
└── {DATE}-{agent}-{feature-name}/
|
||||
├── {DATE}-{agent}-{feature-name}-dialog.md ← Main file
|
||||
└── steps/
|
||||
├── 01-{step-name}.md ← Self-contained steps
|
||||
├── 02-{step-name}.md
|
||||
└── ...
|
||||
{output_folder}/_progress/
|
||||
├── 00-design-log.md ← Main state tracking
|
||||
└── agent-experiences/
|
||||
├── {DATE}-{agent}-{feature-name}.md ← Session insights
|
||||
└── ...
|
||||
```
|
||||
|
||||
---
|
||||
|
|
@ -198,10 +198,10 @@ For each Object ID:
|
|||
- **Object IDs are the contract** — Every implementation maps to an Object ID
|
||||
- **Spec changes update the spec** — Not the dialog or step files
|
||||
|
||||
### Dialog Files
|
||||
### Design Log
|
||||
- **Be thorough in Setup Context** — Assume zero prior knowledge
|
||||
- **Include file paths** — Always use absolute or project-relative paths
|
||||
- **Track progress** — Update the Steps Overview table after each step
|
||||
- **Track progress** — Update the design log after each step
|
||||
|
||||
### Execution
|
||||
- **Read spec first** — Before implementing any Object ID
|
||||
|
|
@ -213,9 +213,8 @@ For each Object ID:
|
|||
|
||||
## Related Resources
|
||||
|
||||
- **Agent Dialog Workflow:** `workflows/_agent-dialogs/workflow.md`
|
||||
- **Dialog Template:** `workflows/_agent-dialogs/templates/dialog.template.md`
|
||||
- **Step Template:** `workflows/_agent-dialogs/templates/step.template.md`
|
||||
- **Design Log:** `{output_folder}/_progress/00-design-log.md`
|
||||
- **Agent Experiences:** `{output_folder}/_progress/agent-experiences/`
|
||||
- **Phase 4 UX Design:** `workflows/4-ux-design/workflow.md`
|
||||
- **Inline Testing Guide:** `workflows/5-agentic-development/guides/INLINE-TESTING-GUIDE.md`
|
||||
|
||||
|
|
|
|||
|
|
@ -237,7 +237,7 @@ Not:
|
|||
|
||||
### Never Re-Ask What You Already Know
|
||||
|
||||
When loading a new step, ALWAYS check what was captured in prior steps. The agent dialog files contain previous answers.
|
||||
When loading a new step, ALWAYS check what was captured in prior steps. The design log and previous step outputs contain previous answers.
|
||||
|
||||
**Pattern:**
|
||||
1. Before asking your first question in a new step, review available context from prior steps
|
||||
|
|
|
|||
|
|
@ -129,7 +129,7 @@ docs/method/dream-up-rubric-phase-2.md
|
|||
- ✅ Context declaration (explicit usage context)
|
||||
- ✅ Visual connection diagram (shows logic flow)
|
||||
|
||||
**Document in agent dialog:**
|
||||
**Document in design log:**
|
||||
|
||||
```markdown
|
||||
## Layer 1: WDS Form Learned
|
||||
|
|
@ -233,7 +233,7 @@ src/workflows/3-scenarios/data/validation-standards.md
|
|||
- SEO keywords (if relevant)
|
||||
- Future plans
|
||||
|
||||
**Document in agent dialog:**
|
||||
**Document in design log:**
|
||||
|
||||
```markdown
|
||||
## Layer 2: Project Context (Initial Load)
|
||||
|
|
@ -917,12 +917,12 @@ Would you like to:
|
|||
|
||||
---
|
||||
|
||||
## Agent Dialog Documentation
|
||||
## Design Log Documentation
|
||||
|
||||
**Throughout process, maintain comprehensive agent dialog:**
|
||||
**Throughout process, maintain comprehensive agent experience log:**
|
||||
|
||||
```markdown
|
||||
# Agent Dialog: Dream Up - Källa Trigger Map
|
||||
# Agent Experience: Dream Up - Källa Trigger Map
|
||||
|
||||
**Created:** {{date time}}
|
||||
**Mode:** {{Suggest/Dream}}
|
||||
|
|
@ -996,9 +996,9 @@ Would you like to:
|
|||
[Strategic choices during generation]
|
||||
```
|
||||
|
||||
**Save agent dialog at:**
|
||||
**Save agent experience at:**
|
||||
```
|
||||
{output_folder}/_progress/agent-dialogs/{date}-trigger-map-{{mode}}.md
|
||||
{output_folder}/_progress/agent-experiences/{date}-trigger-map-{{mode}}.md
|
||||
```
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -75,4 +75,4 @@ Whether designing new features, refining experiences, building design foundation
|
|||
|
||||
**Analyzing your project now...**
|
||||
|
||||
_(Continue to: `{project-root}/_bmad/wds/workflows/_agent-dialogs/project-analysis/02-project-analysis-router.md`)_
|
||||
_(Continue to: Read `{output_folder}/_progress/00-design-log.md` and present the Adaptive Dashboard)_
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ Figma for refinement and component integration.
|
|||
|
||||
### 4. Agentic Development
|
||||
**When to use:** You want to build features iteratively with AI assistance.
|
||||
**What it does:** Guided implementation using agent dialogs — prototypes, code, bug fixes.
|
||||
**What it does:** Guided implementation using design log — prototypes, code, bug fixes.
|
||||
**Output:** Working implementations, prototype iterations
|
||||
**Best for:** When you're ready to go from spec to code with AI support.
|
||||
|
||||
|
|
|
|||
|
|
@ -71,4 +71,4 @@ Whether defining architecture, planning sprints, creating handoff packages, or c
|
|||
|
||||
**Analyzing your project now...**
|
||||
|
||||
_(Continue to: `{project-root}/_bmad/wds/workflows/_agent-dialogs/project-analysis/02-project-analysis-router.md`)_
|
||||
_(Continue to: Read `{output_folder}/_progress/00-design-log.md` and present the Adaptive Dashboard)_
|
||||
|
|
|
|||
|
|
@ -72,4 +72,4 @@ Whether starting new products, clarifying direction, researching users, or defin
|
|||
|
||||
**Analyzing your project now...**
|
||||
|
||||
_(Continue to: `{project-root}/_bmad/wds/workflows/_agent-dialogs/project-analysis/02-project-analysis-router.md`)_
|
||||
_(Continue to: Read `{output_folder}/_progress/00-design-log.md` and present the Adaptive Dashboard)_
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
|
||||
wds,0-wds-agents,Wake Saga,SAGA,1,_bmad/wds/agents/saga-analyst.agent.yaml,bmad-wds-saga,false,saga-analyst,Agent Activation,"Agent launcher. Wakes Saga (Strategic Analyst) who handles Phases 1-2. Saga introduces herself scans attached repos for WDS projects checks phase completion status finds unfinished agent dialogs and offers contextually appropriate next steps. Use this to start Product Brief or Trigger Map work.",,,
|
||||
wds,0-wds-agents,Wake Saga,SAGA,1,_bmad/wds/agents/saga-analyst.agent.yaml,bmad-wds-saga,false,saga-analyst,Agent Activation,"Agent launcher. Wakes Saga (Strategic Analyst) who handles Phases 1-2. Saga introduces herself scans attached repos for WDS projects checks phase completion status reads the design log and offers contextually appropriate next steps. Use this to start Product Brief or Trigger Map work.",,,
|
||||
wds,0-wds-agents,Wake Freya,FREYA,2,_bmad/wds/agents/freya-ux.agent.yaml,bmad-wds-freya,false,freya-ux,Agent Activation,"Agent launcher. Wakes Freya (UX Designer) who handles Phases 3-4. Freya introduces herself scans repos checks prerequisites (Product Brief + Trigger Map) detects scenario and design status and offers appropriate next steps. Use this to start UX Scenarios or UX Design work.",,,
|
||||
wds,0-wds-agents,Wake Idunn,IDUNN,3,_bmad/wds/agents/idunn-pm.agent.yaml,bmad-wds-idunn,false,idunn-pm,Agent Activation,"Agent launcher. Wakes Idunn (Project Manager) who handles project oversight and Phase 5 (Design System). Idunn provides comprehensive status across ALL phases identifies unfinished work shows critical path and coordinates handoffs between agents. Use this for project overview or Design System work.",,,
|
||||
wds,0-wds-pitch,Alignment & Signoff,AS,10,_bmad/wds/workflows/0-alignment-signoff/workflow.md,bmad-wds-alignment,false,saga-analyst,Create Mode,"Optional. Secure stakeholder buy-in before the project starts. Create a pitch document service agreement and signoff. Use when working with clients or stakeholders who need to approve budget and scope. Skip if building your own product or working with a small trusted team.",design_artifacts/A-Product-Brief,"pitch service-agreement signoff",
|
||||
|
|
@ -14,6 +14,6 @@ wds,2-wds-design,Functional Components,FI,50,_bmad/wds/workflows/4-ux-design/wor
|
|||
wds,2-wds-design,Visual Design,VD,60,_bmad/wds/workflows/6-asset-generation/workflow.md,bmad-wds-visual-design,false,freya-ux,Create Mode,"Transform specifications into visual prototypes. Generate styled HTML prototypes from specs then refine with Figma round-trips using code.to.design or AI image generation. This is where soul enters the product. A visual designer should set the visual language — the AI applies it consistently.",design_artifacts/C-UX-Scenarios,"html-prototypes visual-designs",
|
||||
wds,2-wds-design,Design System,DS,70,_bmad/wds/workflows/7-design-system/workflow.md,bmad-wds-design-system,false,freya-ux,Create Mode,"Manage your component library based on project mode: None Building Library or Existing. Components and design tokens grow organically from your design work. Each project builds on the last. Skip if using Design System Mode None.",design_artifacts/D-Design-System,"components/ design-tokens.md",
|
||||
wds,2-wds-design,Design Delivery,DD,80,_bmad/wds/workflows/4-ux-design/workflow-handover.md,bmad-wds-design-delivery,true,freya-ux,Create Mode,"Required. Validate specifications are complete and package them for development as DD yaml files. Freya runs a final audit checking every element every state and accessibility. The DD contract is what developers or the agentic development phase builds from. Nothing ships without this validation.",design_artifacts/E-PRD/Design-Deliveries,"delivery-package acceptance-criteria",
|
||||
wds,3-wds-build,Agentic Development,AD,10,_bmad/wds/workflows/_agent-dialogs/workflow.md,bmad-wds-agentic-development,false,pm,Create Mode,"Build iteratively using Agent Dialogs. Design one thing build it verify with Puppeteer in the browser iterate. Every decision is logged so you can restart conversations without losing context. The agent tests its own work against acceptance criteria while you handle qualitative judgment.",_progress/agent-dialogs,"dialog-documents",
|
||||
wds,3-wds-build,Agentic Development,AD,10,_bmad/wds/workflows/5-agentic-development/workflow.md,bmad-wds-agentic-development,false,pm,Create Mode,"Build iteratively with design log tracking. Design one thing build it verify with Puppeteer in the browser iterate. Every decision is logged so you can restart conversations without losing context. The agent tests its own work against acceptance criteria while you handle qualitative judgment.",_progress/agent-experiences,"experience-documents",
|
||||
wds,3-wds-build,Acceptance Testing,AT,20,_bmad/wds/workflows/5-agentic-development/workflow-acceptance-testing.md,bmad-wds-usability-testing,false,freya-ux,Create Mode,"Test the product on real users using their own devices in their own environment. Plan the test scenario conduct sessions with silence and deflection then replay recordings with users for retrospective think-aloud. The Whiteport Rule: if it is not worth showing to 5 users and 1 domain expert it should not be built.",design_artifacts/F-Testing,"test-results findings",
|
||||
wds,3-wds-build,Product Evolution,PE,30,_bmad/wds/workflows/8-product-evolution/workflow.md,bmad-wds-product-evolution,false,idunn-pm,Create Mode,"Continuous improvement for living products. The full WDS process in miniature — receive feedback connect to Trigger Map update the spec first then project into code verify and document. Every change uses a Product Evolution Agent Dialog. Start here if you have an existing product you want to improve.",design_artifacts,"updated-artifacts",
|
||||
wds,3-wds-build,Product Evolution,PE,30,_bmad/wds/workflows/8-product-evolution/workflow.md,bmad-wds-product-evolution,false,idunn-pm,Create Mode,"Continuous improvement for living products. The full WDS process in miniature — receive feedback connect to Trigger Map update the spec first then project into code verify and document. Every change is tracked in the design log. Start here if you have an existing product you want to improve.",design_artifacts,"updated-artifacts",
|
||||
|
|
|
|||
|
|
|
@ -34,12 +34,12 @@ Let me check what you're working on...
|
|||
3. Filter out system repos (WDS, BMad expansion modules)
|
||||
4. For each WDS project repo found:
|
||||
- Read `wds-project-outline.yaml` for project name and phase status
|
||||
- Scan `_progress/agent-dialogs/` for dialog files with status `In Progress` or `Not Started`
|
||||
- Note any open dialogs related to Phases 3-4
|
||||
- Read `_progress/00-design-log.md` — check Current table and Design Loop Status
|
||||
- Note any in-progress work related to Phases 3-4
|
||||
|
||||
**Multi-project branching logic:**
|
||||
|
||||
**If multiple open agent dialogs found:**
|
||||
**If in-progress work found in multiple projects:**
|
||||
```
|
||||
I found open work in multiple projects:
|
||||
1. [Project A]: [Phase X - task description]
|
||||
|
|
@ -48,7 +48,7 @@ I found open work in multiple projects:
|
|||
Which would you like to work on?
|
||||
```
|
||||
|
||||
**If no open dialogs but multiple projects:**
|
||||
**If no in-progress work but multiple projects:**
|
||||
```
|
||||
I found [N] WDS projects in your workspace:
|
||||
1. [Project A] - Phase [X] status
|
||||
|
|
@ -64,7 +64,7 @@ Which project would you like to work on?
|
|||
- Check for my artifacts:
|
||||
- `C-UX-Scenarios/` folder (Phase 3)
|
||||
- `C-UX-Scenarios/` folder (Phase 3+4)
|
||||
- Check for open agent dialogs in that project
|
||||
- Check design log Current table for in-progress work
|
||||
- Note phase completion status
|
||||
|
||||
### 3. Status Report
|
||||
|
|
@ -83,26 +83,25 @@ Phase 4: UX Design [✓ complete / ⏳ in-progress / ○ not started]
|
|||
⚠️ Prerequisites missing: Need Saga to complete Phase 1-2 first
|
||||
Type /saga to call Saga
|
||||
|
||||
[If open dialog found:]
|
||||
⏸ Unfinished work: [dialog-file-name.md]
|
||||
Last task: [task description from dialog]
|
||||
[If Current table has task:]
|
||||
⏸ In progress: [task from Current table]
|
||||
|
||||
[If no open dialogs:]
|
||||
○ No open agent dialogs for my phases
|
||||
[If Current is empty:]
|
||||
○ No work in progress for my phases
|
||||
```
|
||||
|
||||
### 4. Offer Next Steps
|
||||
|
||||
**Only shown for single-project scenario.** Based on status, offer appropriate actions:
|
||||
|
||||
**If unfinished dialog found (default: resume):**
|
||||
**If Current table has a task (default: resume):**
|
||||
```
|
||||
I found unfinished work in [dialog-file-name.md]:
|
||||
→ [task description from dialog]
|
||||
I found in-progress work:
|
||||
→ [task from Current table]
|
||||
|
||||
Picking up where we left off...
|
||||
```
|
||||
Read the dialog file, find the next incomplete step, and continue naturally.
|
||||
Read the design log, check Design Loop Status for current page state, and continue naturally.
|
||||
Only ask before resuming if the user's message clearly indicates a different task.
|
||||
|
||||
**If prerequisites missing:**
|
||||
|
|
|
|||
|
|
@ -35,12 +35,12 @@ Let me check your project status...
|
|||
3. Filter out system repos (WDS, BMad expansion modules)
|
||||
4. For each WDS project repo found:
|
||||
- Read `wds-project-outline.yaml` for project name and phase status
|
||||
- Scan `_progress/agent-dialogs/` for dialog files with status `In Progress` or `Not Started`
|
||||
- Note any open dialogs across ALL phases
|
||||
- Read `_progress/00-design-log.md` — check Current table and Design Loop Status
|
||||
- Note any in-progress work across ALL phases
|
||||
|
||||
**Multi-project branching logic:**
|
||||
|
||||
**If multiple open agent dialogs found:**
|
||||
**If in-progress work found in multiple projects:**
|
||||
```
|
||||
I found open work in multiple projects:
|
||||
1. [Project A]: [Phase X - task description]
|
||||
|
|
@ -50,7 +50,7 @@ I found open work in multiple projects:
|
|||
Which would you like to work on?
|
||||
```
|
||||
|
||||
**If no open dialogs but multiple projects:**
|
||||
**If no in-progress work but multiple projects:**
|
||||
```
|
||||
I found [N] WDS projects in your workspace:
|
||||
1. [Project A] - Latest phase: [X], Status: [...]
|
||||
|
|
@ -66,7 +66,7 @@ Which project would you like to work on?
|
|||
- Phase 2: `B-Trigger-Map/trigger-map.md`
|
||||
- Phase 3+4: `C-UX-Scenarios/` folder (scenarios, specs, prototypes)
|
||||
- Phase 5: `D-Design-System/` folder
|
||||
- Check for open agent dialogs in that project
|
||||
- Check design log Current table for in-progress work
|
||||
- Identify blockers or dependencies
|
||||
- List all completed/in-progress/pending phases
|
||||
|
||||
|
|
@ -84,10 +84,9 @@ Phase 3: UX Scenarios [✓ complete / ⏳ in-progress / ○ not started]
|
|||
Phase 4: UX Design [✓ complete / ⏳ in-progress / ○ not started]
|
||||
Phase 5: Design System [✓ complete / ⏳ in-progress / ○ not started]
|
||||
|
||||
[If unfinished dialogs found:]
|
||||
⏸ Open work:
|
||||
- [phase-name]: [task description]
|
||||
- [phase-name]: [task description]
|
||||
[If Current table has tasks:]
|
||||
⏸ In progress:
|
||||
- [task from Current table]
|
||||
|
||||
[Critical path indicator:]
|
||||
➡️ Next critical phase: [Phase X]
|
||||
|
|
@ -98,14 +97,14 @@ Phase 5: Design System [✓ complete / ⏳ in-progress / ○ not started]
|
|||
|
||||
**Only shown for single-project scenario.** Based on status, offer appropriate actions:
|
||||
|
||||
**If unfinished dialog found (default: resume):**
|
||||
**If Current table has a task (default: resume):**
|
||||
```
|
||||
I found unfinished work in [dialog-file-name.md]:
|
||||
→ [task description from dialog]
|
||||
I found in-progress work:
|
||||
→ [task from Current table]
|
||||
|
||||
Picking up where we left off...
|
||||
```
|
||||
Read the dialog file, find the next incomplete step, and continue naturally.
|
||||
Read the design log, check Design Loop Status for current state, and continue naturally.
|
||||
Only ask before resuming if the user's message clearly indicates a different task.
|
||||
|
||||
**If project just starting:**
|
||||
|
|
|
|||
|
|
@ -34,12 +34,12 @@ Let me check what you're working on...
|
|||
3. Filter out system repos (WDS, BMad expansion modules)
|
||||
4. For each WDS project repo found:
|
||||
- Read `wds-project-outline.yaml` for project name and phase status
|
||||
- Scan `_progress/agent-dialogs/` for dialog files with status `In Progress` or `Not Started`
|
||||
- Note any open dialogs related to Phases 1-2
|
||||
- Read `_progress/00-design-log.md` — check Current table and Design Loop Status
|
||||
- Note any in-progress work related to Phases 1-2
|
||||
|
||||
**Multi-project branching logic:**
|
||||
|
||||
**If multiple open agent dialogs found:**
|
||||
**If in-progress work found in multiple projects:**
|
||||
```
|
||||
I found open work in multiple projects:
|
||||
1. [Project A]: [Phase X - task description]
|
||||
|
|
@ -48,7 +48,7 @@ I found open work in multiple projects:
|
|||
Which would you like to work on?
|
||||
```
|
||||
|
||||
**If no open dialogs but multiple projects:**
|
||||
**If no in-progress work but multiple projects:**
|
||||
```
|
||||
I found [N] WDS projects in your workspace:
|
||||
1. [Project A] - Phase [X] status
|
||||
|
|
@ -61,7 +61,7 @@ Which project would you like to work on?
|
|||
- Check for my artifacts:
|
||||
- `A-Product-Brief/product-brief.md` (Phase 1)
|
||||
- `B-Trigger-Map/trigger-map.md` (Phase 2)
|
||||
- Check for open agent dialogs in that project
|
||||
- Check design log Current table for in-progress work
|
||||
- Note phase completion status
|
||||
|
||||
### 3. Status Report
|
||||
|
|
@ -74,26 +74,25 @@ Which project would you like to work on?
|
|||
Phase 1: Product Brief [✓ complete / ⏳ in-progress / ○ not started]
|
||||
Phase 2: Trigger Map [✓ complete / ⏳ in-progress / ○ not started]
|
||||
|
||||
[If open dialog found:]
|
||||
⏸ Unfinished work: [dialog-file-name.md]
|
||||
Last task: [task description from dialog]
|
||||
[If Current table has task:]
|
||||
⏸ In progress: [task from Current table]
|
||||
|
||||
[If no open dialogs:]
|
||||
○ No open agent dialogs for my phases
|
||||
[If Current is empty:]
|
||||
○ No work in progress for my phases
|
||||
```
|
||||
|
||||
### 4. Offer Next Steps
|
||||
|
||||
**Only shown for single-project scenario.** Based on status, offer appropriate actions:
|
||||
|
||||
**If unfinished dialog found (default: resume):**
|
||||
**If Current table has a task (default: resume):**
|
||||
```
|
||||
I found unfinished work in [dialog-file-name.md]:
|
||||
→ [task description from dialog]
|
||||
I found in-progress work:
|
||||
→ [task from Current table]
|
||||
|
||||
Picking up where we left off...
|
||||
```
|
||||
Read the dialog file, find the next incomplete step, and continue naturally.
|
||||
Read the design log, check Backlog for context, and continue naturally.
|
||||
Only ask before resuming if the user's message clearly indicates a different task.
|
||||
|
||||
**If Phase 1 not started:**
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ Let's get clear on what you need so we can move forward."
|
|||
Display: "**Select an Option:** [C] Continue to step-01b-determine-if-needed"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ Route to Project Brief workflow.
|
|||
Display: "**Select an Option:** [C] Continue to step-01c-offer-extract"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@ Skip to step-01e-detect-starting-point.md
|
|||
Display: "**Select an Option:** [C] Continue to step-01d-extract-info (if documents provided) or step-01e-detect-starting-point (if skipping)"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile} (or step-01e if skipping extraction)
|
||||
- IF C: Load, read entire file, then execute {nextStepFile} (or step-01e if skipping extraction)
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -89,7 +89,7 @@ Extract relevant information from the communications/documents:
|
|||
Display: "**Select an Option:** [C] Continue to step-01e-detect-starting-point"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ Ask where they'd like to start:
|
|||
Display: "**Select an Option:** [C] Continue to step-02a-explore-realization (or step-02b-explore-solution based on user choice)"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile} (or step-02b if starting with solution)
|
||||
- IF C: Load, read entire file, then execute {nextStepFile} (or step-02b if starting with solution)
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@ Explore the realization section with the user.
|
|||
Display: "**Select an Option:** [C] Continue to step-02b-explore-solution"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ If user starts with a solution idea:
|
|||
Display: "**Select an Option:** [C] Continue to step-02c-explore-why-it-matters"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@ Explore why it matters and who we help.
|
|||
Display: "**Select an Option:** [C] Continue to step-02d-explore-how-we-see-it-working"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ Explore how they see it working.
|
|||
Display: "**Select an Option:** [C] Continue to step-02e-explore-paths-we-explored"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ Explore paths they explored.
|
|||
Display: "**Select an Option:** [C] Continue to step-02f-explore-recommended-solution"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ Explore the recommended solution.
|
|||
Display: "**Select an Option:** [C] Continue to step-02g-explore-path-forward"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ Explore the path forward.
|
|||
Display: "**Select an Option:** [C] Continue to step-02h-explore-value-we-create"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -89,7 +89,7 @@ Explore the value we'll create.
|
|||
Display: "**Select an Option:** [C] Continue to step-02i-explore-cost-of-inaction"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ Explore cost of inaction.
|
|||
Display: "**Select an Option:** [C] Continue to step-02j-explore-our-commitment"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@ Explore our commitment.
|
|||
Display: "**Select an Option:** [C] Continue to step-02k-explore-summary"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ Explore the summary.
|
|||
Display: "**Select an Option:** [C] Continue to step-03a-reflect-back"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ If user wants adjustments, make them and re-reflect until confirmed.
|
|||
Display: "**Select an Option:** [C] Continue to step-03b-synthesize-document"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -89,7 +89,7 @@ Help crystallize into a clear, compelling narrative using framework thinking:
|
|||
Display: "**Select an Option:** [C] Continue to Present for Approval"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -95,7 +95,7 @@ Proceed to Project Brief workflow
|
|||
Display: "**Select an Option:** [C] Continue to step-04a-offer-signoff"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -91,7 +91,7 @@ Route to step-06a-build-internal-signoff.md (for internal signoff)
|
|||
Display: "**Select an Option:** [C] Continue to step-04b-determine-business-model (or step-06a for internal signoff)"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile} (or step-06a for internal)
|
||||
- IF C: Load, read entire file, then execute {nextStepFile} (or step-06a for internal)
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@ Which model fits your situation?"
|
|||
Display: "**Select an Option:** [C] Continue to step-05a-contract-overview"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ Build the Project Overview section of the contract, pulling the realization and
|
|||
Display: "**Select an Option:** [C] Continue to step-05b-contract-business-model"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ Build the Business Model section based on the user's selected model, explaining
|
|||
Display: "**Select an Option:** [C] Continue to step-05c-contract-scope"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -92,7 +92,7 @@ Build the Scope of Work section with explicit IN scope, OUT of scope, deliverabl
|
|||
Display: "**Select an Option:** [C] Continue to step-05d-contract-payment"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -107,7 +107,7 @@ Build the payment terms section tailored to the selected business model, coverin
|
|||
Display: "**Select an Option:** [C] Continue to step-05e-contract-timeline"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ Build the Timeline section defining when work will happen, key milestones, and d
|
|||
Display: "**Select an Option:** [C] Continue to step-05f-contract-availability (or step-05g if not Retainer)"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile} (or step-05g if not Retainer)
|
||||
- IF C: Load, read entire file, then execute {nextStepFile} (or step-05g if not Retainer)
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -84,7 +84,7 @@ Build the Availability section for retainer contracts, defining when the contrac
|
|||
Display: "**Select an Option:** [C] Continue to step-05g-contract-confidentiality"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@ Build the Confidentiality clause protecting sensitive information shared during
|
|||
Display: "**Select an Option:** [C] Continue to step-05h-contract-not-to-exceed"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -95,7 +95,7 @@ Build the Not-to-Exceed clause based on business model - required for fixed-pric
|
|||
Display: "**Select an Option:** [C] Continue to step-05i-contract-work-initiation"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ Build the Work Initiation section specifying exactly when work can begin - prote
|
|||
Display: "**Select an Option:** [C] Continue to step-05j-contract-terms"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -84,7 +84,7 @@ Build the Terms and Conditions section covering the legal framework including ch
|
|||
Display: "**Select an Option:** [C] Continue to step-05k-contract-approval"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@ Build the Approval section with formal signature lines for both parties to make
|
|||
Display: "**Select an Option:** [C] Continue to step-05l-finalize-contract"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -89,7 +89,7 @@ Update frontmatter of contract file with completion status.
|
|||
Display: "**Select an Option:** [C] Continue to step-06a-build-internal-signoff"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -113,7 +113,7 @@ Build an internal signoff document for company projects, covering goals, budget,
|
|||
Display: "**Select an Option:** [C] Continue to step-06b-finalize-signoff"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -39,11 +39,9 @@ web_bundle: true
|
|||
Load and read full config from `{project-root}/_bmad/wds/config.yaml` and resolve:
|
||||
- `project_name`, `output_folder`, `user_name`, `communication_language`
|
||||
|
||||
### 2. Agent Dialog Gate
|
||||
### 2. Design Log
|
||||
|
||||
1. Check `{output_folder}/_progress/agent-dialogs/` for pending alignment dialogs
|
||||
2. If pending, present with status
|
||||
3. If none, suggest creating one
|
||||
Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
|
||||
|
||||
### 3. Start
|
||||
|
||||
|
|
|
|||
|
|
@ -148,7 +148,7 @@ Next: Set up your project structure.
|
|||
Display: "**Select an Option:** [C] Continue to Step 2: Configuration & Structure"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ Present the positioning components you captured:
|
|||
|
||||
### 3. Document What Was Misunderstood
|
||||
|
||||
**For agent dialog `07-positioning.md`:**
|
||||
**For design log `07-positioning.md`:**
|
||||
|
||||
In the Reflection Checkpoint section, record:
|
||||
- Your synthesis (what you presented)
|
||||
|
|
@ -72,7 +72,7 @@ Am I capturing this right?"
|
|||
|
||||
**Agent:** [Updates understanding, proceeds to Substep 4]
|
||||
|
||||
**Agent Dialog Update (`dialog/07-positioning.md`):**
|
||||
**Design Log Update (`dialog/07-positioning.md`):**
|
||||
```markdown
|
||||
### Reflection Checkpoint
|
||||
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ Show them the positioning statement:
|
|||
[1-2 sentences explaining why this positioning makes sense - reference specific context from conversation]
|
||||
```
|
||||
|
||||
### 4. Update Agent Dialog
|
||||
### 4. Update Design Log
|
||||
|
||||
**In `dialog/07-positioning.md`:**
|
||||
|
||||
|
|
@ -108,7 +108,7 @@ Northern Öland's geography creates a natural monopoly during summer season, but
|
|||
|
||||
---
|
||||
|
||||
## Agent Dialog Update
|
||||
## Design Log Update
|
||||
|
||||
**Mandatory:** Update `dialog/07-positioning.md` with:
|
||||
- Full conversation flow
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ Add to `product-brief.md`:
|
|||
- [Insight 3 - unique angle]
|
||||
```
|
||||
|
||||
### 3. Update Agent Dialog
|
||||
### 3. Update Design Log
|
||||
|
||||
**Mandatory:** Update `dialog/02-vision.md` before marking this step complete.
|
||||
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ Welcome the user and explain that this is their strategic foundation. This workf
|
|||
|
||||
Set time expectations (30-60 minutes) and ask about any existing context that should be considered.
|
||||
|
||||
### 2. Agent Dialog Update
|
||||
### 2. Design Log Update
|
||||
**Mandatory:** Update `dialog/00-context.md` before marking this step complete.
|
||||
|
||||
Fill in:
|
||||
|
|
@ -72,7 +72,7 @@ Mark Phase 0 / Step 1 complete in `dialog/progress-tracker.md` progress tracker.
|
|||
Display: "**Select an Option:** [C] Continue to Vision"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
@ -91,13 +91,13 @@ ONLY WHEN user confirms readiness will you then load and read fully `{nextStepFi
|
|||
- User welcomed and expectations set
|
||||
- Time estimate communicated (30-60 minutes)
|
||||
- Existing context gathered (or noted as none)
|
||||
- Agent dialog updated with project metadata
|
||||
- Design log updated with project metadata
|
||||
- User confirms readiness to proceed
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Started exploring vision or strategic topics
|
||||
- Generated content without user input
|
||||
- Skipped agent dialog update
|
||||
- Skipped design log update
|
||||
- Did not wait for user confirmation before proceeding
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
|
|
|
|||
|
|
@ -71,7 +71,7 @@ vision: '[synthesized vision statement]'
|
|||
Display: "**Select an Option:** [C] Continue to Positioning"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@ Load and reference `../data/positioning-reflect-confirm.md`. Synthesize position
|
|||
### 4. Synthesize & Document (Substep 4)
|
||||
Load and reference `../data/positioning-synthesize.md`. Create positioning statement, document with components and rationale.
|
||||
|
||||
### 5. Agent Dialog Update
|
||||
### 5. Design Log Update
|
||||
**Mandatory:** Update `dialog/07-positioning.md` before marking this step complete.
|
||||
|
||||
The dialog should capture:
|
||||
|
|
@ -76,7 +76,7 @@ Mark Step 3 complete in `dialog/progress-tracker.md` progress tracker.
|
|||
Display: "**Select an Option:** [C] Continue to Create Trigger Map"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
@ -96,7 +96,7 @@ ONLY WHEN positioning is synthesized and user confirms will you then load and re
|
|||
- All components captured (target, need, category, benefit, differentiator)
|
||||
- Positioning statement synthesized by agent from user input
|
||||
- User confirmed the synthesis
|
||||
- Agent dialog updated
|
||||
- Design log updated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Asked user to write a positioning statement directly
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ Reflect back what you heard. If user corrects, update understanding and confirm
|
|||
### 4. Document Decision
|
||||
Add Business Model section to product brief with Model, Rationale, and Implications.
|
||||
|
||||
### 5. Agent Dialog Update
|
||||
### 5. Design Log Update
|
||||
**Mandatory:** In `dialog/decisions.md`, append Business Model decision with opening question, user response, key discussion points, final decision, rationale, and implications.
|
||||
|
||||
Mark Step 5 complete in `dialog/progress-tracker.md` progress tracker.
|
||||
|
|
@ -75,7 +75,7 @@ Mark Step 5 complete in `dialog/progress-tracker.md` progress tracker.
|
|||
Display: "**Select an Option:** [C] Continue to Business Customers" (or "Continue to Target Users" if B2C)
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile} (or step-07 if B2C)
|
||||
- IF C: Load, read entire file, then execute {nextStepFile} (or step-07 if B2C)
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
@ -94,7 +94,7 @@ ONLY WHEN business model is determined and user confirms will you then load and
|
|||
- Business model determined through natural conversation
|
||||
- Rationale and implications documented
|
||||
- User confirmed the business model assessment
|
||||
- Agent dialog updated with decision
|
||||
- Design log updated with decision
|
||||
- Correct conditional routing applied
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ Help the user define their ideal business customer profile, including company ch
|
|||
### 1. Guide Business Customer Definition
|
||||
Ask about company size, industry, decision-making structure, and budget authority. Also identify buying roles (buyer vs. user).
|
||||
|
||||
### 2. Agent Dialog Update
|
||||
### 2. Design Log Update
|
||||
**Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
|
||||
|
||||
Record: Business customer definition, buyer vs end-user distinction, business customer needs and decision criteria.
|
||||
|
|
@ -68,7 +68,7 @@ Mark Step 6 complete in `dialog/progress-tracker.md` progress tracker.
|
|||
Display: "**Select an Option:** [C] Continue to Target Users"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ Help the user define their ideal customer profile by exploring who we are design
|
|||
### 1. Guide User Description
|
||||
Guide user to describe their ideal users in detail. Ask about their role, demographics, daily experience, frustrations, goals, and current solutions. Also identify any secondary users or stakeholders.
|
||||
|
||||
### 2. Agent Dialog Update
|
||||
### 2. Design Log Update
|
||||
**Mandatory:** Update `dialog/03-users.md` before marking this step complete.
|
||||
|
||||
Fill in: Opening question about users + user's initial response, key exchanges exploring who they are, frustrations, goals, current solutions, user scenarios captured, reflection checkpoint, primary user definition + secondary users.
|
||||
|
|
@ -68,7 +68,7 @@ Mark Step 7 complete in `dialog/progress-tracker.md` progress tracker.
|
|||
Display: "**Select an Option:** [C] Continue to Product Concept"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
@ -87,7 +87,7 @@ ONLY WHEN target users are defined and user confirms will you then load and read
|
|||
- Primary user profile defined with behavioral depth
|
||||
- Secondary users identified if applicable
|
||||
- User confirmed the profiles match their target
|
||||
- Agent dialog updated
|
||||
- Design log updated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Accepted demographics-only user description
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ Synthesize what you heard and confirm understanding with: Core Structural Idea,
|
|||
### 5. Document the Concept
|
||||
Record: Core Structural Idea, Implementation Principle, Rationale, Concrete Example, Features That Stem From Concept.
|
||||
|
||||
### 6. Agent Dialog Update
|
||||
### 6. Design Log Update
|
||||
**Mandatory:** Update `dialog/04-concept.md` before marking this step complete.
|
||||
|
||||
Fill in: Opening question, user's initial description, key exchanges, rationale discussion, reflection checkpoint, final concept documentation. Mark Step 7a complete in `dialog/progress-tracker.md`.
|
||||
|
|
@ -82,7 +82,7 @@ Fill in: Opening question, user's initial description, key exchanges, rationale
|
|||
Display: "**Select an Option:** [C] Continue to Success Criteria"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
@ -102,7 +102,7 @@ ONLY WHEN product concept is articulated and user confirms will you then load an
|
|||
- Rationale explored and documented
|
||||
- Concrete example provided
|
||||
- User confirmed the concept captures their vision
|
||||
- Agent dialog updated
|
||||
- Design log updated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Accepted a feature list as the product concept
|
||||
|
|
|
|||
|
|
@ -62,14 +62,14 @@ Ask which is most important.
|
|||
### 5. Confirm and Document
|
||||
Reflect back. Get confirmation. Document in product brief.
|
||||
|
||||
### 6. Agent Dialog Update
|
||||
### 6. Design Log Update
|
||||
Mandatory: Append to dialog/decisions.md. Mark Step 8 complete.
|
||||
|
||||
### N. Present MENU OPTIONS
|
||||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -65,14 +65,14 @@ What if the main alternative just adds your key feature?
|
|||
### 6. Synthesize and Document
|
||||
Reflect back. Get confirmation. Document in product brief.
|
||||
|
||||
### 7. Agent Dialog Update
|
||||
### 7. Design Log Update
|
||||
Append to dialog/decisions.md. Mark Step 9 complete.
|
||||
|
||||
### N. Present MENU OPTIONS
|
||||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ Brief and dialog.
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ Help user define their platform strategy by asking about primary platform choice
|
|||
### 2. Capture and Validate
|
||||
Capture platform strategy, validate alignment with vision and constraints, and document in Product Brief under "Platform & Device Strategy" section including primary platform, supported devices, device priority with rationale, interaction models, technical requirements (offline, native features), platform rationale, constraints considered, future plans, and design/development implications.
|
||||
|
||||
### 3. Agent Dialog Update
|
||||
### 3. Design Log Update
|
||||
**Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
|
||||
|
||||
**Record:**
|
||||
|
|
@ -90,7 +90,7 @@ Capture platform strategy, validate alignment with vision and constraints, and d
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -122,7 +122,7 @@ Once confirmed, document:
|
|||
4. **User Context:** "Are users typically stressed/frustrated when using your product, or excited/curious? How should tone respond to their state?"
|
||||
5. **Differentiation:** "How do competitors communicate? Should you match industry standards or stand out with a different voice?"
|
||||
|
||||
### 7. Agent Dialog Update
|
||||
### 7. Design Log Update
|
||||
**Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
|
||||
|
||||
**Record:**
|
||||
|
|
@ -136,7 +136,7 @@ Once confirmed, document:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -177,7 +177,7 @@ Present a cohesive summary of everything captured, get final confirmation, and g
|
|||
|
||||
### 5. Update All Dialog Files
|
||||
|
||||
**Finalize agent dialogs:**
|
||||
**Finalize design log:**
|
||||
|
||||
**In `dialog/progress-tracker.md`:**
|
||||
- Mark ALL steps complete
|
||||
|
|
@ -205,7 +205,7 @@ Present a cohesive summary of everything captured, get final confirmation, and g
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -64,8 +64,8 @@ Welcome user and set context for defining content and language strategy.
|
|||
- "We'll cover: brand personality, tone of voice, language requirements, and content guidelines."
|
||||
- "This usually takes 15-20 minutes."
|
||||
|
||||
### 5. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 5. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 13: Initialization
|
||||
|
|
@ -81,7 +81,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -84,8 +84,8 @@ Guide the user to articulate specific traits:
|
|||
- Fill in Brand Personality section
|
||||
- Create personality summary paragraph
|
||||
|
||||
### 6. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 6. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 14: Brand Personality
|
||||
|
|
@ -101,7 +101,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -85,8 +85,8 @@ Present examples and ask:
|
|||
- Include spectrum positions with examples
|
||||
- Add We Say / We Don't Say lists
|
||||
|
||||
### 6. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 6. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 15: Tone of Voice
|
||||
|
|
@ -102,7 +102,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -89,8 +89,8 @@ Example: German business communication is often more formal than Swedish.
|
|||
- Create language table with priority and coverage
|
||||
- Document translation approach
|
||||
|
||||
### 7. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 7. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 16: Language Strategy
|
||||
|
|
@ -106,7 +106,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -134,8 +134,8 @@ Document how keywords should be used:
|
|||
- Fill in full SEO Strategy section in content-language document
|
||||
- Include page-keyword map, URL structure, local SEO, structured data plan
|
||||
|
||||
### 10. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 10. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 17: SEO Strategy
|
||||
|
|
@ -151,7 +151,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ Add a "Content Structure Principles" section with whatever emerged from the conv
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -111,8 +111,8 @@ Explain what's next:
|
|||
- "Keywords will guide SEO implementation"
|
||||
- Recommend: "Now let's do Visual Direction to establish the visual style"
|
||||
|
||||
### 7. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 7. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 18: Create Content Document
|
||||
|
|
@ -124,7 +124,7 @@ After completing this step, update the agent dialog:
|
|||
**Timestamp:** [HH:MM]
|
||||
```
|
||||
|
||||
**Also update agent dialog completion:**
|
||||
**Also update design log completion:**
|
||||
- Status: `complete`
|
||||
- Mark content-language.md in Generated Artifacts
|
||||
- Note: "Ready for Visual Direction workflow"
|
||||
|
|
@ -133,7 +133,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -74,9 +74,9 @@ After all sites:
|
|||
|
||||
Create `inspiration-analysis.md` in the Product Brief output folder using the template at `../templates/inspiration-analysis.template.md`.
|
||||
|
||||
### 5. Agent Dialog Integration
|
||||
### 5. Design Log Integration
|
||||
|
||||
Follow the same agent dialog pattern as other PB workflows:
|
||||
Follow the same design log pattern as other PB workflows:
|
||||
- Create/update dialog entry for this workshop
|
||||
- Document key questions, answers, and insights
|
||||
- Note which elements were liked/disliked and why
|
||||
|
|
@ -85,7 +85,7 @@ Follow the same agent dialog pattern as other PB workflows:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -73,8 +73,8 @@ Welcome user and set context for capturing visual direction.
|
|||
- If yes: "Let's start by documenting what exists."
|
||||
- If no: "Great, we have a blank canvas to work with."
|
||||
|
||||
### 5. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 5. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 20: Visual Direction Init
|
||||
|
|
@ -90,7 +90,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -101,8 +101,8 @@ If user has assets to share:
|
|||
- Fill in Existing Brand Assets section
|
||||
- Note brand constraints from partnerships
|
||||
|
||||
### 6. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 6. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 21: Existing Brand Assets
|
||||
|
|
@ -118,7 +118,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -90,8 +90,8 @@ Validate with user: "Would you say the visual direction should feel [keywords]?"
|
|||
- Add each reference with URL and what we like
|
||||
- Capture mood description and keywords
|
||||
|
||||
### 7. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 7. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 22: Visual References
|
||||
|
|
@ -107,7 +107,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -96,8 +96,8 @@ Based on tone and style:
|
|||
- Fill in Color Direction section
|
||||
- Fill in Typography Direction section
|
||||
|
||||
### 6. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 6. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 23: Design Style
|
||||
|
|
@ -113,7 +113,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -101,8 +101,8 @@ Note constraints:
|
|||
- Fill in Layout Direction section
|
||||
- Fill in Visual Effects section
|
||||
|
||||
### 7. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 7. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 24: Layout & Effects
|
||||
|
|
@ -118,7 +118,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -110,8 +110,8 @@ Document standards:
|
|||
- Fill in Photography & Imagery section
|
||||
- Note image sources and guidelines
|
||||
|
||||
### 8. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 8. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 25: Photography & Imagery
|
||||
|
|
@ -127,7 +127,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -116,7 +116,7 @@ Explain what's next:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -65,8 +65,8 @@ Welcome user and set context for capturing platform decisions.
|
|||
- If yes, capture these first
|
||||
- If no, proceed to exploration
|
||||
|
||||
### 5. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 5. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 27: Platform Init
|
||||
|
|
@ -82,7 +82,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -78,8 +78,8 @@ For React/Next:
|
|||
### 4. Capture in Template
|
||||
- Fill in Technology Stack section of output document
|
||||
|
||||
### 5. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 5. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 28: Technology Stack
|
||||
|
|
@ -95,7 +95,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -84,8 +84,8 @@ Ask: "Are there any integrations you might want in the future?"
|
|||
- Fill in Integrations section
|
||||
- Fill in Plugin/Package Stack section
|
||||
|
||||
### 6. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 6. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 29: Integrations & Plugins
|
||||
|
|
@ -101,7 +101,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -88,8 +88,8 @@ Capture constraints for UX design:
|
|||
- Fill in Contact Strategy section
|
||||
- Note UX Constraints
|
||||
|
||||
### 7. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 7. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 30: Contact Strategy
|
||||
|
|
@ -105,7 +105,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -108,8 +108,8 @@ Discuss realistic targets:
|
|||
- Fill in SEO Requirements section
|
||||
- Add Performance Targets
|
||||
|
||||
### 6. Agent Dialog Update
|
||||
After completing this step, update the agent dialog:
|
||||
### 6. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 31: Multilingual & SEO
|
||||
|
|
@ -125,7 +125,7 @@ After completing this step, update the agent dialog:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -106,7 +106,7 @@ Explain what's next:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ Check completeness:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ This creates a strategic foundation that ensures every design decision serves bo
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@ If no significant decisions were made, skip this section.
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ For each section:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ For each Trigger Map:
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ Check if SEO/keyword content exists in the Content & Language document. If not,
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ Check if Content & Language document exists at `{output_folder}/A-Product-Brief/
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ Check if Visual Direction document exists at `{output_folder}/A-Product-Brief/`.
|
|||
Display: "**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ cp -r workflows/1-project-brief/templates/project-brief-dialog projects/{{slug}}
|
|||
**Each step file should mandate:**
|
||||
|
||||
```markdown
|
||||
## Agent Dialog Update
|
||||
## Design Log Update
|
||||
|
||||
Before marking complete:
|
||||
1. Update `dialog/{{step}}-{{name}}.md`
|
||||
|
|
@ -62,105 +62,20 @@ All dialog files: 65-86 lines (well under 100-line target)
|
|||
|
||||
---
|
||||
|
||||
## Agent Session Dialogs (Meta-Level)
|
||||
## Design Log (Meta-Level)
|
||||
|
||||
**For multi-session work**, agents should maintain their own session dialog separate from project dialogs.
|
||||
**For multi-session work**, agents should use the design log for state tracking and `_progress/agent-experiences/` for session insights.
|
||||
|
||||
**Location:** `{{root_folder}}/_progress/agent-dialogs/{{session-date}}-{{agent-name}}-{{task}}.md`
|
||||
|
||||
**Structure Pattern:**
|
||||
|
||||
```markdown
|
||||
# Agent Dialog: {{Task Name}}
|
||||
|
||||
**Date:** {{date}}
|
||||
**Agent:** {{agent name}}
|
||||
**Project:** {{project name}}
|
||||
|
||||
---
|
||||
|
||||
## CURRENT PLAN
|
||||
|
||||
**{{Overall objective}}**
|
||||
|
||||
1. ✅ Task 1 name
|
||||
2. ✅ Task 2 name
|
||||
3. ⏳ Task 3 name (in progress)
|
||||
4. ⬜ Task 4 name
|
||||
5. ⬜ Task 5 name
|
||||
|
||||
**Ultimate Goal:** {{End state description}}
|
||||
|
||||
---
|
||||
|
||||
## ⏳ CURRENT WORK
|
||||
|
||||
### Task 3: {{Task name}}
|
||||
|
||||
**Objective:** {{What you're doing now}}
|
||||
|
||||
**Sub-tasks:**
|
||||
- {{Specific thing 1}}
|
||||
- {{Specific thing 2}}
|
||||
- {{Specific thing 3}}
|
||||
|
||||
**Status:** {{Current status}}
|
||||
|
||||
---
|
||||
|
||||
## 🎯 UPCOMING WORK
|
||||
|
||||
### Task 4: {{Next task}}
|
||||
|
||||
**Purpose:** {{Why this matters}}
|
||||
|
||||
**Implementation:** {{How you'll do it}}
|
||||
|
||||
---
|
||||
|
||||
## ✅ COMPLETED WORK
|
||||
|
||||
*(Reverse chronological order - latest first)*
|
||||
|
||||
---
|
||||
|
||||
### Task 2: {{Task name}} ({{date}})
|
||||
|
||||
**Objective:** {{What was done}}
|
||||
|
||||
**Key achievements:**
|
||||
- {{Achievement 1}}
|
||||
- {{Achievement 2}}
|
||||
|
||||
**Files modified:** {{File count and names}}
|
||||
|
||||
**Status:** Complete
|
||||
|
||||
---
|
||||
|
||||
### Task 1: {{Task name}} ({{date}})
|
||||
|
||||
**Objective:** {{What was done}}
|
||||
|
||||
[Details...]
|
||||
```
|
||||
|
||||
**Navigation Benefits:**
|
||||
- Easy to see progress at a glance
|
||||
- Clear separation: current vs upcoming vs completed
|
||||
- Latest work always at top of completed section
|
||||
- Ultimate goal always visible
|
||||
**Location:** `{{root_folder}}/_progress/00-design-log.md`
|
||||
|
||||
**Update Protocol:**
|
||||
1. Complete current task
|
||||
2. Update agent dialog with changes
|
||||
2. Update design log with changes
|
||||
3. Show git diff to user
|
||||
4. Move task from CURRENT WORK to top of COMPLETED WORK
|
||||
5. Move next task from UPCOMING WORK to CURRENT WORK
|
||||
6. Update CURRENT PLAN checkboxes (✅/⏳/⬜)
|
||||
4. Record session insights in `_progress/agent-experiences/` if needed
|
||||
|
||||
---
|
||||
|
||||
## Purpose
|
||||
|
||||
Create transparent record of discovery conversations so future agents (and humans) understand WHY decisions were made, not just WHAT was decided.
|
||||
Create transparent record of discovery conversations so future agents (and humans) understand WHY decisions were made, not just WHAT was decided. The design log provides this continuity across sessions.
|
||||
|
|
|
|||
|
|
@ -11,11 +11,9 @@ description: 'Verify all Product Brief artifacts are complete, consistent, and r
|
|||
|
||||
## INITIALIZATION
|
||||
|
||||
### Agent Dialog Gate
|
||||
### Design Log
|
||||
|
||||
1. Check for pending activity dialogs
|
||||
2. If none, suggest creating one
|
||||
3. Load dialog context
|
||||
Read `{output_folder}/_progress/00-design-log.md` before starting.
|
||||
|
||||
### Configuration Loading
|
||||
|
||||
|
|
|
|||
|
|
@ -34,11 +34,9 @@ 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`
|
||||
- `brief_level` from `{output_folder}/wds-workflow-status.yaml:config.brief_level`
|
||||
|
||||
### 2. Agent Dialog Gate
|
||||
### 2. Design Log
|
||||
|
||||
1. Check `{output_folder}/_progress/agent-dialogs/` for pending project brief dialogs
|
||||
2. If pending, present with status
|
||||
3. If none, suggest creating one
|
||||
Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
|
||||
|
||||
### 3. Mode Determination
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ Present Phase 2: Trigger Mapping overview, offer engagement mode selection (Work
|
|||
- 🚫 FORBIDDEN to skip mode selection or auto-choose for user
|
||||
- 💬 Approach: Clear presentation of three modes with time estimates
|
||||
- 📋 Workshop mode proceeds through step-by-step facilitation
|
||||
- 📋 Suggest and Dream modes use the dream-up-approach with agent dialog tracking
|
||||
- 📋 Suggest and Dream modes use the dream-up-approach with design log tracking
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
|
|
@ -88,9 +88,9 @@ If One at a time: Run Workshop 1, then offer to save and continue later.
|
|||
**If Suggest (S) or Dream (D):**
|
||||
Output: "{{mode}} selected. I'll generate the Trigger Map using WDS methodology + Product Brief + domain research."
|
||||
|
||||
Inform user: "I'm creating an agent dialog to track my learning, research, generation, and self-review process."
|
||||
Inform user: "I'm creating a design log to track my learning, research, generation, and self-review process."
|
||||
|
||||
Create agent dialog using ../../_agent-dialogs/templates/dream-up-agent-dialog.template.md at {output_folder}/_progress/agent-dialogs/{date}-trigger-map-{{mode}}.md
|
||||
Create session log at {output_folder}/_progress/agent-experiences/{date}-trigger-map-{{mode}}.md
|
||||
|
||||
Execute Layer 1: Learn WDS Form (Static - loaded once)
|
||||
- Read docs/method/phase-2-trigger-mapping-guide.md
|
||||
|
|
@ -99,7 +99,7 @@ Execute Layer 1: Learn WDS Form (Static - loaded once)
|
|||
- Read docs/models/impact-effect-mapping.md
|
||||
- Read docs/method/dream-up-rubric-phase-2.md
|
||||
- Internalize: Structure, quality criteria, common mistakes, best practices
|
||||
- Document in agent dialog "Layer 1: WDS Form Learned" section
|
||||
- Document in design log "Layer 1: WDS Form Learned" section
|
||||
|
||||
Execute Layer 2: Project Context (Initial load, grows with each step)
|
||||
- Read {output_folder}/A-Product-Brief/product-brief.md
|
||||
|
|
@ -107,7 +107,7 @@ Execute Layer 2: Project Context (Initial load, grows with each step)
|
|||
- Read {output_folder}/A-Product-Brief/platform-requirements.md
|
||||
- Read {output_folder}/A-Product-Brief/visual-direction.md
|
||||
- Extract: business context, user archetypes, constraints, strategic direction
|
||||
- Document in agent dialog "Layer 2: Project Context (Initial)" section
|
||||
- Document in design log "Layer 2: Project Context (Initial)" section
|
||||
- NOTE: Layer 2 grows cumulatively - add Business Goals, Target Groups, Driving Forces, Prioritization as created
|
||||
|
||||
For EACH step (Business Goals, Target Groups, Driving Forces, Prioritization):
|
||||
|
|
@ -115,7 +115,7 @@ For EACH step (Business Goals, Target Groups, Driving Forces, Prioritization):
|
|||
Execute Layer 3: Domain Research (per step)
|
||||
- WebSearch relevant to current step
|
||||
- Look for industry insights, user reviews, behavioral patterns
|
||||
- Document findings in agent dialog
|
||||
- Document findings in design log
|
||||
|
||||
Execute Layer 4: Generate
|
||||
- Apply WDS Form (Layer 1) with ALL Project Context (Layer 2 cumulative)
|
||||
|
|
@ -125,7 +125,7 @@ For EACH step (Business Goals, Target Groups, Driving Forces, Prioritization):
|
|||
Execute Layer 5: Self-Review
|
||||
- Check against rubric (completeness, quality, mistakes, practices)
|
||||
- Calculate quality score, identify gaps
|
||||
- Document in agent dialog
|
||||
- Document in design log
|
||||
|
||||
If gaps exist: Create refinement plan, regenerate (max 5 iterations per step)
|
||||
|
||||
|
|
@ -140,7 +140,7 @@ When all steps complete:
|
|||
- Create persona documents if needed
|
||||
- Create mermaid diagram if generated
|
||||
- Present final output to user
|
||||
- Update agent dialog with final output section
|
||||
- Update design log with final output section
|
||||
|
||||
Skip to handover after generation complete.
|
||||
|
||||
|
|
@ -171,7 +171,7 @@ ONLY WHEN user selects [C] will you load the next step file. Mode must be select
|
|||
- User explicitly selected a mode
|
||||
- Correct path activated based on selection
|
||||
- Workshop sub-choice (All/One) offered if Workshop mode selected
|
||||
- Suggest/Dream modes properly initialize agent dialog and layered approach
|
||||
- Suggest/Dream modes properly initialize design log and layered approach
|
||||
- User confirmed and ready to proceed
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
|
@ -179,7 +179,7 @@ ONLY WHEN user selects [C] will you load the next step file. Mode must be select
|
|||
- Not presenting all three mode options
|
||||
- Not explaining what each mode involves
|
||||
- Proceeding without explicit user selection
|
||||
- Not initializing agent dialog for Suggest/Dream modes
|
||||
- Not initializing design log for Suggest/Dream modes
|
||||
- Skipping the layered approach for autonomous modes
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
|
|
|
|||
|
|
@ -15,11 +15,8 @@ validateWorkflow: './steps-v/step-01-target-group-coverage.md'
|
|||
|
||||
## INITIALIZATION
|
||||
|
||||
### Agent Dialog Gate
|
||||
|
||||
1. Check for pending activity dialogs
|
||||
2. If none, suggest creating one
|
||||
3. Load dialog context
|
||||
### Design Log
|
||||
Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
|
||||
|
||||
### Configuration Loading
|
||||
|
||||
|
|
|
|||
|
|
@ -51,11 +51,9 @@ 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
|
||||
|
||||
1. Check `{output_folder}/_progress/agent-dialogs/` for pending trigger mapping dialogs
|
||||
2. If pending, present with status
|
||||
3. If none, suggest creating one
|
||||
Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
|
||||
|
||||
### 3. Mode Determination
|
||||
|
||||
|
|
|
|||
|
|
@ -96,7 +96,7 @@ Read `{output_folder}/B-Trigger-Map/trigger-map.md` (the hub document)
|
|||
**Check for resume situation:**
|
||||
- Does `{output_folder}/C-UX-Scenarios/` exist?
|
||||
- Are there any scenario files already?
|
||||
- Are there unfinished agent dialogs in `{output_folder}/_progress/agent-dialogs/`?
|
||||
- Is there in-progress work in the design log (`{output_folder}/_progress/00-design-log.md`)?
|
||||
|
||||
**If existing work found:**
|
||||
```
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ workflowFile: '../workflow.md'
|
|||
|
||||
## STEP GOAL:
|
||||
|
||||
Complete Phase 3 by presenting a final summary, guiding the user through design intent selection for each scenario, explaining what comes next in Phase 4, and updating any agent dialogs.
|
||||
Complete Phase 3 by presenting a final summary, guiding the user through design intent selection for each scenario, explaining what comes next in Phase 4, and updating the design log.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
|
|
@ -130,9 +130,9 @@ You can always change approach in Phase 4.
|
|||
Would you like to continue to Phase 4, or take a break?
|
||||
```
|
||||
|
||||
### 4. Update Agent Dialog (If Exists)
|
||||
### 4. Update Design Log (If Exists)
|
||||
|
||||
If tracking via agent dialog:
|
||||
If tracking via design log:
|
||||
- Mark Phase 3 as complete
|
||||
- Log scenario count and quality scores
|
||||
- Note any user adjustments made during the process
|
||||
|
|
@ -166,7 +166,7 @@ ONLY WHEN [M main menu option] is selected and [design intent captured for all s
|
|||
- Design intent selection offered for each scenario
|
||||
- Design intent and status saved to scenario frontmatter
|
||||
- Phase 4 approaches clearly explained
|
||||
- Agent dialog updated if applicable
|
||||
- Design log updated if applicable
|
||||
- User informed of next steps
|
||||
- Menu presented and user input handled correctly
|
||||
|
||||
|
|
@ -176,6 +176,6 @@ ONLY WHEN [M main menu option] is selected and [design intent captured for all s
|
|||
- Skipping design intent selection
|
||||
- Not saving design intent to scenario files
|
||||
- Ending without explaining next steps
|
||||
- Not updating agent dialog when one exists
|
||||
- Not updating design log when one exists
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue