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:
2026-03-19 13:29:03 -04:00
parent c5b377e788
commit 647cbec54f
3246 changed files with 479789 additions and 983 deletions

View File

@@ -0,0 +1,43 @@
---
name: trigger-mapping-validate
description: Validate Trigger Map documents against WDS quality standards
web_bundle: true
validateWorkflow: './steps-v/step-01-target-group-coverage.md'
---
# Validate Trigger Map
**Goal:** Systematically validate all Trigger Map documents against WDS quality standards and generate an actionable report.
**Your Role:** Validation specialist reviewing trigger map completeness, consistency, and strategic alignment.
---
## INITIALIZATION
### Design Log
Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
### Configuration Loading
Load and read full config from `{project-root}/_bmad/wds/config.yaml` and resolve:
- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
### Load Trigger Map Data
Load all trigger map documents from `{output_folder}/B-Trigger-Map/`.
### Route to Validation
Load, read completely, and execute `{validateWorkflow}` (steps-v/step-01-target-group-coverage.md)
Auto-proceed through all validation steps. Present final report at the end.
---
## AFTER COMPLETION
1. Update design log
2. Suggest next action
3. Return to activity menu