- 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.1 KiB
1.1 KiB
Requirements Traceability & Quality Gate
Workflow: bmad-testarch-trace
Version: 5.0 (Step-File Architecture)
Overview
Create a requirements-to-tests traceability matrix, analyze coverage gaps, and optionally make a gate decision (PASS/CONCERNS/FAIL/WAIVED) based on evidence.
WORKFLOW ARCHITECTURE
This workflow uses step-file architecture:
- Micro-file Design: Each step is self-contained
- JIT Loading: Only the current step file is in memory
- Sequential Enforcement: Execute steps in order
INITIALIZATION SEQUENCE
1. Configuration Loading
From workflow.yaml, resolve:
config_source,test_artifacts,user_name,communication_language,document_output_language,datetest_dir,source_dir,coverage_levels,gate_type,decision_mode
2. First Step
Load, read completely, and execute:
./steps-c/step-01-load-context.md
3. Resume Support
If the user selects Resume mode, load, read completely, and execute:
./steps-c/step-01b-resume.md
This checks the output document for progress tracking frontmatter and routes to the next incomplete step.