When should I run the Spec Verification skill?

It is best used during Phase 5 of the specification creation process, immediately after drafting requirements and tasks but before beginning implementation.

Can it help reduce over-engineering?

Yes, the skill specifically flags unnecessary abstractions, redundant components, and features that exceed the defined project scope.

Does it work with UI designs and mockups?

Absolutely. It verifies that visual assets are documented in requirements, analyzed for components, and correctly referenced in frontend implementation tasks.

What happens if the verification fails?

The skill generates a detailed report highlighting critical, important, and minor issues. It can often help you fix these issues automatically or provide guidance for manual corrections.

What documentation does it need to run?

It typically reads initialization.md, requirements.md, spec.md, and tasks.md, along with any files in the planning/visuals directory.

Spec Verification & Quality Audit

Name: Spec Verification & Quality Audit
Author: marcos-abreu

bymarcos-abreu

•

생산성 및 워크플로

Validates technical specifications for accuracy, visual alignment, and implementation readiness to prevent over-engineering and logic gaps.

소개

The Spec Verification skill acts as a rigorous quality gate between planning and coding by systematically auditing requirements against original project goals. It ensures visual assets are correctly mapped to implementation tasks, identifies opportunities for code reuse, and creates a comprehensive verification report. By flagging over-engineering and missing details before a single line of code is written, it helps developers maintain a lean, efficient, and well-documented development cycle.

주요 기능

Detailed verification reports with prioritized issue severity
1 GitHub stars
Requirements-to-Q&A accuracy cross-referencing
Visual asset integration and UI component mapping
Automated identification of code reusability opportunities
Over-engineering and technical debt risk detection

사용 사례

Reviewing complex feature specifications before starting a development sprint
Auditing project documentation for scope creep and unnecessary complexity
Ensuring UI designs are accurately reflected in task-level requirements