speckit-spec-validate-status

name	speckit-spec-validate-status
description	Spec-kit workflow command: speckit-spec-validate-status
compatibility	Requires spec-kit project structure with .specify/ directory
metadata	{"author":"github-spec-kit","source":"spec-validate:commands/status.md"}

Check Validation Status

Command: speckit.spec-validate.status

Display the current validation and approval state for the active feature. This command is read-only — it MUST NOT modify any state.

Execution Flow

1. Determine the current feature from .specify/feature.json
2. Run read-approval-state.sh <feature> to load the approval state
3. Display a formatted summary:

Output Format

## Spec Validate Status: <feature-name>

| Field                  | Value              |
|------------------------|--------------------|
| Feature                | <feature>          |
| Spec validation        | <not-run/passed/failed/stale> |
| Spec hash              | <hash or "not set"> |
| Spec validated at      | <timestamp or "never"> |
| Tasks validation       | <not-run/passed/failed/stale> |
| Tasks hash             | <hash or "not set"> |
| Review status          | <not-required/pending/approved/changes-requested/timed-out> |
| Reviewer               | <name or "none">   |
| Approval status        | <blocked/allowed/allowed-with-warning/override-approved> |
| Override used          | <yes (reason) / no> |
| Timeout self-approval  | <yes (reason) / no> |

### Warnings
<list of active warnings, or "None">

### Review Comments
<list of reviewer comments, or "None">

4. If approval_status is blocked, display the reason and suggested actions
5. Do NOT compute or update any hashes, staleness checks, or approval decisions — those are the gate command's responsibility

Important Constraints

• Never modify state — this is purely informational
• Never evaluate gate rules — just display stored state as-is
• Always show all fields — even if null or empty, show the field with "not set" / "none" / "never"