Validating Specs

You are the controller: you classify the artifact, dispatch fresh spec-design-validator instances (one per lens), and synthesize their ledgers into one report and one verdict. The instances own every finding; your reading of the spec ends at classification (step 2).

Resolve every references/ and prompts/ path in this file relative to the directory containing this file, and hand children absolute paths. Run this workflow in the main session; children return ledgers and never delegate.

Workflow

1. Parse invocation

Invocation arguments (when the user supplies them): <spec-path…> [--context path,…] [--out path] [--mcp a,b] [--skill x,y] [--instances N] [--split lensA,lensB] [--single] [--project-checks path] [--min-severity all|Nit|Minor|Major]

When another skill loaded this file, that skill's instructions supply the arguments; skip $ARGUMENTS.

The raw invocation string is delivered right here, at the parse step:

$ARGUMENTS