Audit SPEC documents for completeness, consistency, and technical quality.
npx skills add https://github.com/kaptinlin/gozod --skill spec-reviewing
Please help me install this Agent Skill. Skill: spec-reviewing Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/spec-reviewing Command: npx skills add https://github.com/kaptinlin/gozod --skill spec-reviewing
SPEC documents often drift from defined standards, creating gaps and risks of over-engineering. This skill provides a disciplined review workflow to enforce completeness, consistency, and alignment with reference implementations before moving to implementation.
Review the latest SPEC documents to identify gaps, inconsistencies, and potential over-engineering.
High-intent search queries and answers about installing and using this skill.
Spec review checks document completeness and consistency by enforcing mechanical, semantic, and technical audits to identify design gaps, validate single-source truth, and ensure alignment with reference implementations before implementation begins.
Auditing technical specifications for over-engineering requires a technical review that flags vague requirements, identifies misalignments with reference implementations, and enforces explicit decision records to prevent unnecessary design complexity.
Run a spec review after a batch of specs is written, immediately before implementation begins, or during spec refactors to ensure documents align with spec-writing guides and maintain cross-SPEC consistency.
Single-source truth consistency across SPEC documents is enforced through semantic review checks that verify terminology alignment, validate cross-SPEC references, and require explicit decision records to prevent documentation drift.
Validating SPEC document structure and reference validity requires a mechanical review that verifies section presence, checks document formatting, and confirms that all cross-references align with defined spec-writing guidelines.
Yes, you can use this spec review workflow to audit documentation after refactoring to verify that updated SPECs maintain completeness, enforce single-source truth, and preserve alignment with reference implementations.
raiichReview Markdown files for naming, conciseness, consistency, and completeness.
fkbertholdIdentify documentation gaps and produce code-validated docs with M1–M5 verification.
team-attentionGenerate a Draft PR from a validated spec using a PR body template.
pax-kConvert recurring code review findings into automated harness checks or documentation.
