skills/formatting-audits/SKILL.md
Binary Ready/NotReady gate for SOW/Spec. Use when: 設計書レビュー, 実装可否判定, document gate.
npx skillsauth add thkt/dotclaude formatting-auditsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Binary gate: the spec is either ready for CC to implement without asking, or it is not. No numeric score.
Goal: every FR / AC produces unambiguous test cases. If CC cannot write a test from a requirement without an escalation, the spec is NotReady.
Judgment rule: "Can I write the Given/When/Then from this requirement right now, with observable assertions?" If no → Blocker.
| Level | Meaning | Gate | | ----- | ------------------------------------------------------ | ------------- | | P0 | Decision missing or behavior unobservable. CC will escalate | Block (NotReady) | | P1 | Ambiguous but CC can infer with risk of drift | Warn | | P2 | Quality issue, no implementation impact | Info |
Concrete triggers live in validating-specs (check-level) and sow-spec-reviewer
(document-level). The rule for assigning Priority: replay the judgment above on
the specific finding.
| Condition | Judgment | Action | | ------------------- | --------- | ----------------------------------- | | P0 = 0 | Ready | Proceed to implementation | | P0 ≥ 1 | NotReady | Resolve P0 findings, re-run gate |
P1/P2 findings are reported for visibility. They never block the gate.
Every finding must carry Priority + Fix example. A finding without a Fix example is not actionable and must be rejected as a reviewer error.
| Field | Requirement | | -------- | ----------------------------------------------------- | | Priority | P0 / P1 / P2 | | Location | document:line or section | | CC Impact | What happens when CC reads this (escalates / drifts / ok) | | Fix | Concrete rewrite example, not "clarify this" |
Documents written before a template extension may lack a newly-added column.
| State | Treatment | | -------------------------------------------- | -------------------------------------------- | | Column exists in table, value empty | Finding per Priority rules (Check 8 etc.) | | Column absent from table structure entirely | Skip column check. Emit P2 "legacy format — column X missing, migrate when convenient" |
Prevents every pre-existing document from being marked NotReady after template changes.
Applies to all column-completeness checks in validating-specs and reviewer agents.
| Concern | Skill / Agent |
| ----------------------------------- | ------------------------- |
| AC-FR traceability, consistency | validating-specs |
| Document-level review orchestration | sow-spec-reviewer agent |
tools
Internal helper for /think Step 11. Renders SOW.md + Spec.md as an integrated Astro view and returns a dev server URL.
development
Extract repository spec while detecting bugs, spec gaps, and consistency drift via dual-purpose documentation. OUTCOME.md-axis question-driven exploration with ephemeral output. Do NOT use for code review (use /audit or /polish), feature implementation (use /code), planning only (use /think), or single-bug fix (use /fix).
development
Discover undocumented design decisions and challenge each candidate via critic-design before promotion. Rank by impact and reversibility, produce ADR promotion candidates. Treat each candidate as a position arguing for ADR status, not a fact to be filed. Pairs with audit-adr-drift, which scans existing ADRs for drift against code.
development
Scan ADR Decision sections against current code and report drift with modification direction and priority. Do NOT use for repos without ADRs (use audit-adr-gaps instead).