docs: addressed PR comments

This commit is contained in:
murat 2025-12-23 09:04:14 -06:00
parent 325a264412
commit a459737480
4 changed files with 7 additions and 7 deletions

View File

@ -152,8 +152,8 @@
### Workflow Dependencies
- [ ] Can proceed to `atdd` workflow with P0 scenarios
- [ ] `atdd` is a separate workflow and must be run explicitly (not auto-run)
- [ ] Can proceed to `*atdd` workflow with P0 scenarios
- [ ] `*atdd` is a separate workflow and must be run explicitly (not auto-run)
- [ ] Can proceed to `automate` workflow with full coverage plan
- [ ] Risk assessment informs `gate` workflow criteria
- [ ] Integrates with `ci` workflow execution order
@ -177,7 +177,7 @@
1. [ ] Review risk assessment with team
2. [ ] Prioritize mitigation for high-priority risks (score ≥6)
3. [ ] Allocate resources per estimates
4. [ ] Run `atdd` workflow to generate P0 tests (separate workflow; not auto-run)
4. [ ] Run `*atdd` workflow to generate P0 tests (separate workflow; not auto-run)
5. [ ] Set up test data factories and fixtures
6. [ ] Schedule team review of test design document

View File

@ -764,7 +764,7 @@ After completing this workflow, provide a summary:
1. Review risk assessment with team
2. Prioritize mitigation for high-risk items (score ≥6)
3. Run `atdd` workflow to generate failing tests for P0 scenarios (separate workflow; not auto-run by `test-design`)
3. Run `*atdd` to generate failing tests for P0 scenarios (separate workflow; not auto-run by `*test-design`)
4. Allocate resources per effort estimates
5. Set up test data factories and fixtures
```

View File

@ -250,8 +250,8 @@
## Follow-on Workflows (Manual)
- Run `atdd` to generate failing P0 tests (separate workflow; not auto-run).
- Run `automate` for broader coverage once implementation exists.
- Run `*atdd` to generate failing P0 tests (separate workflow; not auto-run).
- Run `*automate` for broader coverage once implementation exists.
---

View File

@ -6,7 +6,7 @@
---
Note: This workflow does not generate tests. If gaps exist, run `atdd` or `automate` to create coverage.
Note: This workflow does not generate tests. If gaps exist, run `*atdd` or `*automate` to create coverage.
## PHASE 1: REQUIREMENTS TRACEABILITY