원클릭으로
verify-interpreter
Interpret the output of `specgraph verify` and explain what each status means and what to do next.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Interpret the output of `specgraph verify` and explain what each status means and what to do next.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Write correct @spec JSDoc annotations in TypeScript/JavaScript source files to link code to specgraph spec documents.
Analyse specgraph verify output and identify what evidence is missing to advance specs to their next state.
Write specgraph spec documents with correct YAML frontmatter, evidence requirements, and section structure.
Write a specgraph evidence waiver for a spec requirement that cannot currently be satisfied, with a clear justification and expiry plan.
| name | verify-interpreter |
| description | Interpret the output of `specgraph verify` and explain what each status means and what to do next. |
Read and explain the output of specgraph verify in plain language, then recommend next steps.
| Status | Meaning | Action |
|---|---|---|
PASS | All required evidence thresholds met | Nothing required |
WARN | Evidence exists but below required strength for this state | Strengthen evidence or lower requirement |
FAIL | No evidence found for a required dimension | Add evidence or add waiver |
SKIP | Spec has no evidence requirements (draft/deprecated) | Review if state is correct |
WAIVED | Requirement waived — check expiry | Verify waiver is still valid |
specgraph verify # summary table for all specs
specgraph verify --json # machine-readable output
specgraph explain <SPEC-ID> # full claim breakdown for one spec
specgraph find <SPEC-ID> # locate files that reference a spec
specgraph waivers # list active waivers
specgraph subject issue:beads:BD-xx # show a specific Beads issue's claims
specgraph explain <ID> to see what claims exist.state requirements.provider_runs are recent — stale scan data can hide real gaps.| Symptom | Likely cause | Fix |
|---|---|---|
| All specs FAIL | Annotations not scanned | Run specgraph verify again; check @spec syntax |
WARN on accepted specs | Evidence is E0/E1, need E2+ | Add cross-refs or tests |
| Unexpected PASS | Waiver is covering a gap | Check specgraph waivers for active waivers |
| Missing specs in output | Spec file not in docs/ | Check path and .specgraph/config.json |
specgraph explain before deciding whether to add evidence or a waiver.