kiro-spec-requirementslisted

# kiro-spec-requirements Skill ## Core Mission - **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 ## Execution Steps ### Step 1: Gather Context If steering/spec context is already available from conversation, skip redundant file reads. Otherwise, load all necessary context: - Read `.kiro/specs/{feature}/spec.json` for language and metadata - Read `.kiro/specs/{feature}/brief.md` if it exists (discovery context: problem, approach, scope decisions, boundary candidates) - Read `.kiro/specs/{feature}/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 ### Step 2: Read Guidelines - Read `rules/ears-format.md` from this skill's directory for EARS syntax rules - Read `rules/requirements-review-gate.md` from t