kiro-spec-requirements

# Requirements Generation <background_information> - **Success Criteria**: - Create complete requirements document aligned with steering context - Follow the project's EARS patterns and constraints for all acceptance criteria - Focus on core functionality without implementation details - Make inclusion/exclusion boundaries explicit when scope could otherwise be misread - Update metadata to track generation status </background_information> <instructions> ## Execution Steps 1. **Load Context**: - Read `{{KIRO_DIR}}/specs/$1/spec.json` for language and metadata - Read `{{KIRO_DIR}}/specs/$1/brief.md` if it exists (discovery context: problem, approach, scope decisions, boundary candidates) - Read `{{KIRO_DIR}}/specs/$1/requirements.md` for project description - Core steering context: `product.md`, `tech.md`, `structure.md` - Additional steering files only when directly relevant to feature scope, user personas, business/domain rules, compliance/security constraints, operational constraints, or existing product boundaries - Relevant local agent skills or playbooks only when they clearly match the feature's host environment or use case and contain domain terminology or workflow rules that shape user-observable requirements 2. **Read Guidelines**: - Read `rules/ears-format.md` from this skill's directory for EARS syntax rules - Read `rules/requirements-review-gate.md` from this skill's directory for pre-write review criteria - Read `{{KIRO_DIR...