- 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>
1.7 KiB
Scenario Initialization Guide
From Trigger Map to first sketch
Purpose
You've created your Trigger Map. Now: What should you start sketching?
This process helps you identify:
- The core feature to design first
- The natural starting point
- The user's mental state
- The shortest path to mutual success
The 7 Steps
1. Confirm Platform Strategy
Inherit platform strategy from Product Brief and confirm for this scenario
2. What Feature Delivers Value?
Which core feature serves your primary target group?
3. Where Do They Encounter It?
Where does the user first come into contact with your solution?
4. What's Their Mental State?
How are they feeling at this moment?
5. What's Mutual Success?
What does winning look like for both business and user?
6. What's the Shortest Path?
Minimum steps from starting point to mutual success
7. Reference Trigger Map
Identify the relevant Trigger Map context for this scenario
Examples
E-commerce Example
Sales-driven transparent purchase journey
SaaS Example
Subscription-driven frictionless onboarding
Service Booking Example
Appointment-driven trust-building flow
Next Step
Once you have clarity on all 7 steps (including strategic context), start sketching the journey.
Each sketch serves the path from trigger to mutual success, guided by the Trigger Map.