The user input can be provided directly by the agent or as a command argument:
$ARGUMENTS
Purpose
/validate is the unified, level-dispatching entry point for Speck validation. It does not re-implement validation logic — it detects the level and routes to the specialist, which adjudicates prior evidence and owns readiness-state and cap logic.
Level detection
Use --level <project|epic|story> if provided. Otherwise infer from the current directory:
- In
specs/projects/<id>/epics/<eid>/stories/<sid>/→ story - In
specs/projects/<id>/epics/<eid>/→ epic - In
specs/projects/<id>/or higher → project
If the level is still ambiguous, ask the user which level to validate.
Routing
| Level | Read and fully execute |
|---|---|
| story | .cursor/skills/story-validate/SKILL.md |
| epic | .cursor/skills/epic-validate/SKILL.md |
| project | .cursor/skills/project-validate/SKILL.md |
Read the target SKILL.md and follow it end-to-end (including its FIRST-ACTION template reads). Emitting a validation-report.md without running the specialist is simulation, not validation (Verify-Skills Gate).
This router exists for explicit user convenience. Automatic selection uses the level specialist directly.