Files
sar/design-artifacts/_progress/agent-experiences/2026-05-27-trigger-map-D.md
julian 17c08e6392 chore: initial monorepo scaffold + WDS Phase 1+2 artifacts
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-27 14:34:20 +00:00

92 lines
3.2 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Session Log — Trigger Mapping (Dream Mode)
**Date:** 2026-05-27
**Agent:** Saga (BA / Strategic Analyst)
**Mode:** Dream (D) — autonomous generation + final review
**Duration target:** 15-25 min
---
## Layer 1: WDS Form (internalizado)
Effect Mapping by Mijo Balic & Ingrid Domingues, adapted by WDS:
- **WHY:** Business goals (refined from brief)
- **WHO:** Target groups (alliterative persona names)
- **WHAT:** Driving forces (positive motivations + negative fears/frustrations)
- **HOW:** Feature impact (mapping features to forces)
**Quality criteria:**
- Personas alliterative, behavioral (não demográficas)
- Driving forces specific, not vague (não "user wants efficiency")
- Forces scored Frequency × Intensity × Fit
- Feature impact direct mapping
- Diagram mermaid Goals → Personas → Forces
**Common mistakes:**
- Personas demográficos sem comportamento
- Forces genéricas ("quer mais produtividade")
- Pular forças negativas (medos, frustrações)
- Não escorar forças
- Inventar sem ancorar em discovery
---
## Layer 2: Project Context (Phase 1 destilada)
Disponível em contexto:
- `01-product-brief.md` — Vision, Positioning, Personas, Business Model, Success, Competitive, Constraints
- `02-content-language.md` — Tom, vocabulário canônico
- `03-visual-direction.md` — Visual DNA
- `04-platform-requirements.md` — Stack, integrações
- `dialog/*` — 16 docs de histórico detalhado
**4 personas confirmadas:**
- Rafael Representante (PRIMARY) — mobile-first, 70-90% volume
- Sandra Supervisora — desktop+mobile, influenciadora-chave da compra
- Daniel Dono — desktop/iPad, IA estratégica, overlap buyer persona
- Alice Admin — desktop-only, campanhas no-code
**Concept canônico:** "4 cockpits especializados sobre dado único em tempo real, atravessado por WhatsApp nativo e IA contextual"
**Positioning:** target 5-50 reps · dor "decide no escuro" · coexistência com ERPs.
---
## Layer 3: Domain Research (skipped — Phase 1 já cobre extensivamente)
Domain conhecido:
- Mercado B2B força de vendas BR (concorrentes Mercos/Promosoft/MaxFV/Workforce/Mobits)
- ERPs com módulo (TOTVS/Sankhya/Senior/Bling/Tiny/Omie)
- Realidade do rep externo BR (carro, 3G, comissão pesa no salário)
- Estrutura típica PME 5-50 reps (dono decide, supervisor influencia, financeiro/TI ausentes)
- Dor "decide no escuro" validada com Julian
- LGPD constraints
- Setor visual medíocre (insight Step 19)
Web search seria redundante — basear em context destilado.
---
## Layer 4: Generate (executando)
Outputs em `design-artifacts/B-Trigger-Map/`:
- `01-business-goals.md`
- `personas/02-rafael-representante.md`
- `personas/03-sandra-supervisora.md`
- `personas/04-daniel-dono.md`
- `personas/05-alice-admin.md`
- `06-feature-impact-analysis.md`
- `00-trigger-map.md` (hub + mermaid)
---
## Layer 5: Self-Review (pós-generation)
A executar após assembly completo. Verificar:
- [ ] Goals refinados, não copiados do brief
- [ ] Personas com 5-7 driving forces cada (mix positivo+negativo)
- [ ] Forces scored Freq×Int×Fit
- [ ] Feature impact matrix completa
- [ ] Diagram mermaid coerente
- [ ] Trace: cada decision desta Phase 2 tem origem em Phase 1