name: 'step-01-load-context' description: 'Load knowledge base, determine scope, and gather context' nextStepFile: './step-02-discover-tests.md' knowledgeIndex: '{project-root}/_bmad/tea/testarch/tea-index.csv'
Determine review scope, load required knowledge fragments, and gather related artifacts.
{communication_language}CRITICAL: Follow this sequence exactly. Do not skip, reorder, or improvise.
Use review_scope:
If unclear, ask the user.
From {knowledgeIndex} load:
Read {config_source} and check tea_use_playwright_utils and tea_browser_automation to select the correct fragment set.
Core:
test-quality.mddata-factories.mdtest-levels-framework.mdselective-testing.mdtest-healing-patterns.mdselector-resilience.mdtiming-debugging.mdIf Playwright Utils enabled:
overview.md, api-request.md, network-recorder.md, auth-session.md, intercept-network-call.md, recurse.md, log.md, file-utils.md, burn-in.md, network-error-monitor.md, fixtures-composition.mdIf disabled:
fixture-architecture.mdnetwork-first.mdplaywright-config.mdcomponent-tdd.mdci-burn-in.mdPlaywright CLI (if tea_browser_automation is "cli" or "auto"):
playwright-cli.mdMCP Patterns (if tea_browser_automation is "mcp" or "auto"):
If available:
Summarize what was found.
Coverage mapping and coverage gates are out of scope in test-review. Route those concerns to trace.
Save this step's accumulated work to {outputFile}.
If {outputFile} does not exist (first save), create it using the workflow template (if available) with YAML frontmatter:
---
stepsCompleted: ['step-01-load-context']
lastStep: 'step-01-load-context'
lastSaved: '{date}'
---
Then write this step's output below the frontmatter.
{outputFile} already exists, update:
'step-01-load-context' to stepsCompleted array (only if not already present)lastStep: 'step-01-load-context'lastSaved: '{date}'Load next step: {nextStepFile}