chore: initial monorepo scaffold + WDS Phase 1+2 artifacts

- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-27 14:34:20 +00:00
commit 17c08e6392
3631 changed files with 855518 additions and 0 deletions

26
_bmad/tea/config.yaml Normal file
View File

@@ -0,0 +1,26 @@
# TEA Module Configuration
# Generated by BMAD installer
# Version: 6.7.1
# Date: 2026-05-20T13:44:55.560Z
test_artifacts: "{project-root}/_bmad-output/test-artifacts"
tea_use_playwright_utils: true
tea_use_pactjs_utils: false
tea_pact_mcp: none
tea_browser_automation: auto
tea_execution_mode: auto
tea_capability_probe: true
test_stack_type: auto
ci_platform: auto
test_framework: auto
risk_threshold: p1
test_design_output: _bmad-output/test-artifacts/test-design
test_review_output: _bmad-output/test-artifacts/test-reviews
trace_output: _bmad-output/test-artifacts/traceability
# Core Configuration Values
user_name: Julian
project_name: sar
communication_language: Portugues Brasil
document_output_language: Portugues Brasil
output_folder: "{project-root}/_bmad-output"

11
_bmad/tea/module-help.csv Normal file
View File

@@ -0,0 +1,11 @@
module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
Test Architecture Enterprise,_meta,,,,,,,,,false,https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/llms.txt,
Test Architecture Enterprise,bmad-teach-me-testing,Teach Me Testing,TMT,Teach testing fundamentals through 7 sessions (TEA Academy).,,,0-learning,,,false,test_artifacts,progress file|session notes|certificate
Test Architecture Enterprise,bmad-testarch-test-design,Test Design,TD,Risk-based test planning.,,,3-solutioning,,bmad-testarch-framework,false,test_artifacts,test design document
Test Architecture Enterprise,bmad-testarch-framework,Test Framework,TF,Initialize production-ready test framework.,,,3-solutioning,bmad-testarch-test-design,bmad-testarch-ci,false,test_artifacts,framework scaffold
Test Architecture Enterprise,bmad-testarch-ci,CI Setup,CI,Configure CI/CD quality pipeline.,,,3-solutioning,bmad-testarch-framework,,false,test_artifacts,ci config
Test Architecture Enterprise,bmad-testarch-atdd,ATDD,AT,Generate red-phase acceptance test scaffolds before implementation.,,,4-implementation,bmad-create-story:create,bmad-dev-story,false,test_artifacts,atdd-checklist|red-phase acceptance tests
Test Architecture Enterprise,bmad-testarch-automate,Test Automation,TA,Expand test coverage.,,,4-implementation,bmad-testarch-atdd,,false,test_artifacts,test suite
Test Architecture Enterprise,bmad-testarch-test-review,Test Review,RV,Quality audit (0-100 scoring).,,,4-implementation,bmad-testarch-automate,,false,test_artifacts,review report
Test Architecture Enterprise,bmad-testarch-nfr,NFR Evidence Audit,NR,Audit non-functional requirement evidence.,,,4-implementation,bmad-testarch-automate,,false,test_artifacts,nfr report
Test Architecture Enterprise,bmad-testarch-trace,Traceability,TR,Coverage traceability and gate.,,,4-implementation,bmad-testarch-test-review,,false,test_artifacts,traceability matrix|gate decision
1 module skill display-name menu-code description action args phase preceded-by followed-by required output-location outputs
2 Test Architecture Enterprise _meta false https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/llms.txt
3 Test Architecture Enterprise bmad-teach-me-testing Teach Me Testing TMT Teach testing fundamentals through 7 sessions (TEA Academy). 0-learning false test_artifacts progress file|session notes|certificate
4 Test Architecture Enterprise bmad-testarch-test-design Test Design TD Risk-based test planning. 3-solutioning bmad-testarch-framework false test_artifacts test design document
5 Test Architecture Enterprise bmad-testarch-framework Test Framework TF Initialize production-ready test framework. 3-solutioning bmad-testarch-test-design bmad-testarch-ci false test_artifacts framework scaffold
6 Test Architecture Enterprise bmad-testarch-ci CI Setup CI Configure CI/CD quality pipeline. 3-solutioning bmad-testarch-framework false test_artifacts ci config
7 Test Architecture Enterprise bmad-testarch-atdd ATDD AT Generate red-phase acceptance test scaffolds before implementation. 4-implementation bmad-create-story:create bmad-dev-story false test_artifacts atdd-checklist|red-phase acceptance tests
8 Test Architecture Enterprise bmad-testarch-automate Test Automation TA Expand test coverage. 4-implementation bmad-testarch-atdd false test_artifacts test suite
9 Test Architecture Enterprise bmad-testarch-test-review Test Review RV Quality audit (0-100 scoring). 4-implementation bmad-testarch-automate false test_artifacts review report
10 Test Architecture Enterprise bmad-testarch-nfr NFR Evidence Audit NR Audit non-functional requirement evidence. 4-implementation bmad-testarch-automate false test_artifacts nfr report
11 Test Architecture Enterprise bmad-testarch-trace Traceability TR Coverage traceability and gate. 4-implementation bmad-testarch-test-review false test_artifacts traceability matrix|gate decision

View File

@@ -0,0 +1,77 @@
# TEA Workflow Step Files
This folder contains the Test Architect (TEA) workflows converted to skill-driven step-file architecture for strict LLM compliance. Each workflow is tri-modal (create, edit, validate) and uses small, ordered step files routed from `SKILL.md` instead of a single monolithic instruction file.
## Why Step Files
- Enforces sequential execution and prevents improvisation
- Keeps context small and focused per step
- Makes validation and edits deterministic
## Standard Layout (per workflow)
```
<workflow>/
├── SKILL.md # Canonical entrypoint and mode routing
├── customize.toml # Workflow customization surface
├── workflow-plan.md # Design reference for step order and intent
├── workflow.yaml # Installer metadata
├── instructions.md # Short entrypoint / summary
├── checklist.md # Validation criteria for outputs
├── steps-c/ # Create mode steps
├── steps-e/ # Edit mode steps
├── steps-v/ # Validate mode steps
├── templates/ # Output templates (if applicable)
└── validation-report-*.md # Validator outputs (latest run)
```
## Modes
- **Create (steps-c/):** Primary execution flow to generate outputs
- **Edit (steps-e/):** Structured edits to existing outputs
- **Validate (steps-v/):** Checklist-based validation of outputs
## Execution Rules (Summary)
- Load **one step at a time**. Do not preload future steps.
- Follow the **MANDATORY SEQUENCE** exactly in each step.
- Do not skip steps, reorder, or improvise.
- If a step writes outputs, do so **before** loading the next step.
## Step Naming Conventions
- `step-01-*.md` is the init step (no menus unless explicitly required).
- `step-01b-*.md` is a continuation/resume step if the workflow is continuable.
- `step-0X-*.md` are sequential create-mode steps.
- `steps-v/step-01-validate.md` is the validate mode entrypoint.
- `steps-e/step-01-assess.md` is the edit mode entrypoint.
## Validation
- Each workflow has a latest `validation-report-*.md` in its folder.
- Validation uses the BMad Builder workflow validator (workflow-builder).
- The goal is 100% compliance with no warnings.
## References
- Step-file architecture: `docs/explanation/step-file-architecture.md`
- Subagent patterns: `docs/explanation/subagent-architecture.md`
## TEA Workflows
- teach-me-testing
- test-design
- framework
- ci
- atdd
- automate
- test-review
- nfr-assess
- trace
## Notes
- `SKILL.md` is the canonical entrypoint. `instructions.md` is a short summary for quick context.
- `customize.toml` defines activation hooks, persistent facts, and the optional `on_complete` hook.
- Output files typically use `{test_artifacts}` or `{project-root}` variables.
- If a workflow produces multiple artifacts (e.g., system-level vs epic-level), the step file will specify which templates and output paths to use.