What problem does it solve? Software specifications often contain missing requirements, ambiguous wording, conflicting definitions, and gaps between documented behavior and actual code, leading to rework and defects. This Skill provides a structured framework to audit specs before and during development. ## Core Features & Use Cases - Completeness Check: Verify that specs include functional requirements, non-functional requirements, edge cases, error handling, and acceptance criteria using a structured template. - Consistency & Conflict Detection: Cross-reference UI specs, API specs, database schemas, and test specs to find contradictions such as mismatched field constraints. - Implementation Comparison: Compare spec-defined endpoints and features against the actual codebase to track implementation and test coverage status. - Use Case: Before a sprint starts, run a validation pass on a feature spec to catch TBD placeholders, ambiguous terms like "fast", and missing error-handling sections, then produce a gap report for stakeholders. ## Quick Start Validate the attached feature specification for completeness, ambiguity, and consistency with the current API implementation.