Plan Tests

When to use

• After explore-app has produced exploration reports for all scenarios in parsed-spec.md
• When running as part of run-testing-session pipeline (Stage 3)
• When re-synthesizing the plan after a UI change or new exploration

Inputs

• docs/playwright-spec-testing/project-context.md — existing infrastructure, conventions, routing
• docs/playwright-spec-testing/exploration/<slug>.md — one file per scenario (all of them)
• docs/playwright-spec-testing/parsed-spec.md — scenario list and slugs
• .playwright-cli/ (optional) — YAML snapshots and screenshots for selector cross-checking

What it does

Synthesize a complete, human-reviewable test plan grounded in observed DOM data and existing project architecture. Every assertion must be traceable to the exploration report. No invented selectors or URLs.