aod-speclisted

# Spec Validator Skill ## Purpose Automatically validates specification files (spec.md) for completeness, quality, and readiness for architecture and implementation phases. Implements FR-004 from the feature specification. ## How It Works ### Step 1: Locate Specification - Search for `specs/*/spec.md` files in the repository - If specific feature directory provided, validate that spec.md - Report if spec.md not found ### Step 2: Validate Mandatory Sections Check for required sections per specification template: - **User Scenarios & Testing** (mandatory) - User stories with acceptance scenarios - Independent test criteria - Edge cases identified - **Requirements** (mandatory) - Functional requirements - Key entities - **Success Criteria** (mandatory) - Measurable outcomes - **Scope** (mandatory) - In scope - Out of scope - **Assumptions** (optional but recommended) - **Dependencies** (optional but recommended) - **References** (optional) ### Step 3: Check for Clarification Markers - Grep for `[NEEDS CLARIFICATION]` markers - Report all instances with line numbers - Specification not ready if any markers remain ### Step 4: Validate Testable Criteria - Check that each user story has clear acceptance scenarios - Verify success criteria are measurable (contain numbers/percentages) - Ensure requirements have validation criteria ### Step 5: Check Scope Boundaries - Verify "In Scope" section exists and is populated - Verify "Out of Scope" section exi