pkuppens/validation-draft

Validation Draft

Transforms acceptance criteria into an executable validation checklist. Produces concrete steps that any engineer can run without interpretation.

When to use

• Before implementation (TDD): draft tests and verification steps from acceptance criteria
• During implementation: know exactly what "done" looks like before writing code
• After implementation: verify all criteria are met before opening a PR

Instructions

1. Read acceptance criteria — each - [ ] checkbox in the issue is a criterion to validate.
2. For each criterion, produce:
   • The command or action to execute (exact CLI command, URL + click path, or test invocation)
   • The expected result (exit code, output text, UI state, response body)
3. Identify test type — unit test, integration test, manual UI flow, or CLI smoke test.
4. Order by dependency — infrastructure first (app starts), then feature tests, then edge cases.
5. Flag untestable criteria — if a criterion cannot be validated automatically, flag it for manual review.

Validation step format

Per criterion, use one markdown block for the narrative fields, then a separate bash block for the command (avoid nested triple backticks).

### [Criterion summary]
**Type:** unit | integration | manual | smoke
**Command / action:** see the bash block below this section in your doc.
**Expected result:** [What to observe — exit code, output, UI state]

<exact command>

BDD scenario format (optional)

For feature-level criteria, use Gherkin when it aids clarity:

Given [precondition]
When  [action]
Then  [expected outcome]

Example

Criterion: "uv run pytest -v --cov=. --cov-fail-under=80 exits 0; new modules covered"

### Tests pass with ≥80% coverage
**Type:** integration
**Command / action:** see bash block below.
**Expected result:** Exit 0; coverage report shows ≥80% for new modules.

cd backend && uv run pytest -v --cov=. --cov-fail-under=80

Output format

Produce a ## Validation Checklist section suitable for pasting into the issue or a tmp/validation.md scratch file:

## Validation Checklist

- [ ] [Criterion 1] — `<command>` → [expected result]
- [ ] [Criterion 2] — Open [URL], click [path] → [expected state]
- [ ] [Criterion 3] — `<test command>` exits 0

Integration

• Input: acceptance criteria from issue-acceptance-criteria.
• Output feeds: test-write and validation-run.
• In TDD flow: run before implementation-construction.