docs: update all documentation and add AI tooling configs
- Rewrite README.md with current architecture, features and stack - Update docs/API.md with all current endpoints (corporate, BI, client 360) - Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL - Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente) - Add docs/INDEX.md documentation index - Add PROJETO.md comprehensive project reference - Add BI-CCC-Implementation-Guide.md - Include AI agent configs (.claude, .agents, .gemini, _bmad) - Add netbird VPN configuration - Add status report Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
66
_bmad/wds/data/presentations/mimir-agents-overview.md
Normal file
66
_bmad/wds/data/presentations/mimir-agents-overview.md
Normal file
@@ -0,0 +1,66 @@
|
||||
# The WDS Agents — Who Does What
|
||||
|
||||
**Instructions:** Present each agent one at a time. After the overview, ask which
|
||||
agent the user wants to work with or if they need help deciding.
|
||||
|
||||
---
|
||||
|
||||
## The Team
|
||||
|
||||
WDS has three specialist agents. Each owns specific phases of product development.
|
||||
|
||||
---
|
||||
|
||||
## Saga — WDS Analyst Agent
|
||||
|
||||
**Phases:** 1 (Product Brief), 2 (Trigger Mapping)
|
||||
|
||||
**What she does:**
|
||||
- Discovers your product's strategic story through conversation
|
||||
- Creates the Product Brief — your project's North Star
|
||||
- Maps user psychology to business goals (Trigger Map)
|
||||
- Conducts market, competitive, and domain research
|
||||
|
||||
**When to use Saga:**
|
||||
- Starting a new project from scratch
|
||||
- You have an idea but need structure
|
||||
- You need to define who your users are and what drives them
|
||||
- You want to validate your business strategy
|
||||
|
||||
**What she produces:** Product Brief, Trigger Map, personas, research documents
|
||||
|
||||
---
|
||||
|
||||
## Freya — WDS Designer Agent
|
||||
|
||||
**Phases:** 4 (UX Design), 7 (Design System), 9 (Testing), 10 (Product Evolution)
|
||||
|
||||
**What she does:**
|
||||
- Creates detailed UX scenarios and page specifications
|
||||
- Builds interactive HTML prototypes
|
||||
- Develops design systems (tokens, components)
|
||||
- Validates implementation against design
|
||||
- Iterates on existing products
|
||||
|
||||
**When to use Freya:**
|
||||
- You have a Product Brief and need to design the experience
|
||||
- You want scenarios and specs for developers
|
||||
- You need prototypes to test concepts
|
||||
- You want to validate what was built matches the design
|
||||
|
||||
**What she produces:** Scenarios, page specs, prototypes, design system, test results
|
||||
|
||||
---
|
||||
|
||||
## How They Work Together
|
||||
|
||||
```
|
||||
Saga (Strategy) → Freya (Design + Delivery) → Development
|
||||
Phase 1-2 Phase 4-8
|
||||
```
|
||||
|
||||
Saga goes first. Freya designs, packages deliveries, and guides product evolution.
|
||||
|
||||
---
|
||||
|
||||
**Which agent do you want to work with? Or tell me what you need and I'll route you.**
|
||||
Reference in New Issue
Block a user