kiro-spec-requirements

1# Requirements Generation
2 
3<background_information>
4- **Success Criteria**:
5  - Create complete requirements document aligned with steering context
6  - Follow the project's EARS patterns and constraints for all acceptance criteria
7  - Focus on core functionality without implementation details
8  - Make inclusion/exclusion boundaries explicit when scope could otherwise be misread
9  - Update metadata to track generation status
10</background_information>
11 
12<instructions>
13## Execution Steps
14 
151. **Load Context**:
16   - Read `{{KIRO_DIR}}/specs/$1/spec.json` for language and metadata
17   - Read `{{KIRO_DIR}}/specs/$1/brief.md` if it exists (discovery context: problem, approach, scope decisions, boundary candidates)
18   - Read `{{KIRO_DIR}}/specs/$1/requirements.md` for project description
19   - Core steering context: `product.md`, `tech.md`, `structure.md`
20   - Additional steering files only when directly relevant to feature scope, user personas, business/domain rules, compliance/security constraints, operational constraints, or existing product boundaries
21   - Use explicitly requested skills and task-relevant local skills/playbooks, including design, accessibility, and UX. Select by description and read only needed guidance, even for small tasks; preserve required checks and host/project rules.
22 
232. **Read Guidelines**:
24   - Read `rules/ears-format.md` from this skill's directory for EARS syntax rules
25…