Claude
Skills
Sign in
Back

define-validation

Included with Lifetime
$97 forever

Use to add validation criteria to a spec or plan. Triggers include "define validation", "how will we validate", "what should the AI check", and "add validation to this".

General

What this skill does


# Define Validation

Validation answers: "How will the AI know this is done?"

It must be behavioral and actionable — something the AI can actually run or observe. "Run the CLI with these args and confirm the output contains X." "Use Playwright to confirm clicking the button triggers Y." "Run the test suite and check it passes." Not "verify the UX feels right."

Add a validation section to an existing spec or plan. If none exists, save standalone to `.lore/work/validation/[topic].html`. Load `${CLAUDE_PLUGIN_ROOT}/shared/document-schema.md` for the meta tag fields before writing.

When saving standalone, the output is HTML — make the validation steps interactive. A checklist with pass/fail state, code blocks with copy buttons for CLI invocations, or clear visual separation between automated and manual steps turns a doc into something someone can actually work through. Inline CSS and JS are fine; no external dependencies.

## What counts

- Unit or integration tests
- CLI invocations with expected output
- Browser automation steps
- Manual steps the AI can follow and report on
- Lint and type checks when behavior depends on them

Structural assertions ("verify this function appears only once") don't count. If a regression must not recur, write a test that fails when the behavior regresses, not when lines move.

Related in General