kiro-spec-requirements

1# kiro-spec-requirements Skill
2 
3## Core Mission
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 
11## Execution Steps
12 
13### Step 1: Gather Context
14 
15Reuse steering/spec context already available from conversation; load missing context below.
16Select skills for the current task even when steering/spec context is already available:
17- Read `{{KIRO_DIR}}/specs/{feature}/spec.json` for language and metadata
18- Read `{{KIRO_DIR}}/specs/{feature}/brief.md` if it exists (discovery context: problem, approach, scope decisions, boundary candidates)
19- Read `{{KIRO_DIR}}/specs/{feature}/requirements.md` for project description
20- Core steering context: `product.md`, `tech.md`, `structure.md`
21- Additional steering files only when directly relevant to feature scope, user personas, business/domain rules, compliance/security constraints, operational constraints, or existing product boundaries
22- 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.
23 
24### Step 2: Read Guidelines
25…