validate-requirementslisted

# Validate Requirements Skill ## Purpose Ensures the user's input (requirements, description, source material) meets the prerequisites defined in their standards for this project type. This is the first gate in the quality pipeline. ## What to Check Based on the user's saved standards for the project type, verify: 1. **Completeness** - Is there enough information? - Examples: "Describe the component's purpose", "Explain what refactoring is needed", "Provide the blog topic" 2. **Clarity** - Is the description clear and specific? - Not vague: "Write something" → needs detail - Specific: "Create a dropdown component with keyboard navigation" → clear 3. **Format** - Is it in a recognizable format? - Code examples provided? Existing code to refactor? - Links to resources? Topic outline for content? 4. **Sufficiency** - Is there enough context? - Does the user explain the "why"? - Are constraints/requirements mentioned? 5. **Standards Alignment** - Does it match their defined validation rules? - Read the project type's saved standards (from standards.json) - Check against their validationRules section ## Process 1. Read the user's input/requirements 2. Load their standards for this project type using StandardsRepository 3. Check against their defined validation rules 4. Scan for common issues: - Empty or minimal descriptions - Conflicting requirements - Missing critical context 5. Report findings clearly ## Using Standards Access sta