Answer: In Kiro Feature Specs, the requirements.md file uses EARS (Easy Approach to Requirements Syntax) notation, where each requirement follows the pattern: WHEN [condition/event] THE SYSTEM SHALL [expected behavior]. Status: Confirmed Entry: tool/kiro/features/ears-notation-requirements Revision: 1 Digest: sha256:5e1630ce5c70facc (changes whenever the content changes) Timeline: Created: 2026-11-13T03:44:59Z Last changed: 2026-11-13T03:44:59Z Last verified: 2026-11-20T13:32:36Z Next check: 2026-11-21T13:32:36Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of notation | EARS (Easy Approach to Requirements Syntax) | [1] | 2026-11-20 requirement pattern | WHEN [condition/event] THE SYSTEM SHALL [expected behavior] | [1] | 2026-11-20 example | WHEN a user submits a form with invalid data THE SYSTEM SHALL display validation errors next to the relevant fields | [1] | 2026-11-20 file | requirements.md | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Feature Specs - Specs - Features - Docs - Kiro". https://kiro.dev/docs/specs/feature-specs/ Role: primary. Accessed: 2026-11-20T13:32:36Z Quote: "uses EARS (Easy Approach to Requirements Syntax) notation to provide structured, testable requirements" (Supports: notation) Quote: "Each requirement follows this pattern: WHEN [condition/event] THE SYSTEM SHALL [expected behavior]" (Supports: requirement pattern) Quote: "WHEN a user submits a form with invalid data THE SYSTEM SHALL display validation errors next to the relevant fields" (Supports: example) Quote: "The requirements.md file uses EARS" (Supports: file) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 7c4a8e29fabd65acdf3c5cc75cca180cff514c6ec9b99a924236ed36d4b4e40c (captured 2026-11-20T13:32:35Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:32:36Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:32:36Z Last attempt: 2026-11-20T13:32:36Z Notes and limitations: Extracted automatically from a single official source (section "Requirements with EARS Notation"). Related: https://latestn.com/tool/kiro/features/edit-and-resend How do I edit and resend a message in Kiro Crew chat? https://latestn.com/tool/kiro/features/enable-computer-use How do I enable Computer Use in Kiro Crew? https://latestn.com/tool/kiro/features/enable-delegate How do I enable delegate in Kiro CLI? https://latestn.com/tool/kiro/features/dockable-chat-vs-chat-panel When should I use dockable chat instead of the Kiro chat panel? https://latestn.com/tool/kiro/features/docs-access-hash-docs How do I access documentation in Kiro using #docs for JavaScript frameworks? https://latestn.com/tool/kiro/features/drag-file-mention How do I mention a file by dragging it into the Kiro Crew chat composer? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:44:59Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/features/ears-notation-requirements/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/features/ears-notation-requirements POST: https://latestn.com/dispute/tool/kiro/features/ears-notation-requirements with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/features/ears-notation-requirements?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I write requirements using EARS notation in Kiro Feature Specs? Revision 1, last verified 2026-11-20T13:32:36Z. https://latestn.com/tool/kiro/features/ears-notation-requirements (accessed 2026-11-21T09:54:46Z). @misc{LatestN_tool_kiro_features_ears_notation_requirements_r1, title = {How do I write requirements using EARS notation in Kiro Feature Specs?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/features/ears-notation-requirements}}, note = {Revision 1; digest sha256:5e1630ce5c70facc; last verified 2026-11-20T13:32:36Z; accessed 2026-11-21T09:54:46Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/features/ears-notation-requirements