gan-planner

GAN Planner

Step 1 of 3 in the GAN (Generative Adversarial Network) harness. Turns a feature brief into falsifiable, Playwright-testable scenarios plus a rubric handoff, so gan-generator knows exactly what to build and gan-evaluator knows exactly how to score it. Codex CLI has no subagents: run this as the first of three skills in sequence — its markdown plan is the literal input to the generator step.

Hard Rules

• Every scenario MUST carry all four assertion types: visual, state, persistence, timing.
• The plan MUST fill the four fixed scenario slots — happy / empty / error / auth-required. A slot may read N/A — <reason> only when it genuinely cannot apply (e.g., auth-required on a fully public page).
• The plan MUST include the ## Rubric section: rubric file(s), applicable criteria count N per rubric, N/A rows with reasons, extra criteria. gan-evaluator scores X / N from this section — omitting it breaks the loop.
• NEVER pause to ask the user mid-run. When the spec leaves a question open, record it under ## Assumptions with the assumption you proceed on.
• Every scenario states what the user sees on failure as concretely as on success.
• Name the exact Playwright test file path the generator must create.

Phase 0 — Load Project Context

Read if present, skip silently if absent:

1. CLAUDE.md / AGENTS.md — project conventions, test setup
2. playwright.config.* — what's already wired up
3. Existing tests in tests/e2e/ or e2e/ — reuse patterns and helpers
4. Rubric files in .claude/rubrics/ (if not found: glob **/rubrics/ui-quality.md; still missing → note NOT FOUND: <path> in the plan and use the default totals in Step 5)
5. The feature spec / brief from the user

Use it to make the plan executable in this project, not a generic template.

When to Use

• Before gan-generator writes code for a UI / interactive feature
• For features where "looks right" matters (UX flows, forms, dashboards, components)
• For changes where a passing unit test is insufficient evidence of correctness