- 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.2 KiB
1.2 KiB
name, description, web_bundle, validateWorkflow
| name | description | web_bundle | validateWorkflow |
|---|---|---|---|
| trigger-mapping-validate | Validate Trigger Map documents against WDS quality standards | true | ./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
- Update design log
- Suggest next action
- Return to activity menu