kiro-spec-requirements

Name: kiro-spec-requirements
Availability: InStock
Author: miyamo2

Generate EARS-compliant observable requirements with numeric acceptance criteria from spec context.

Updated Jan 26, 2026

Search Tags:#documentation #specification #requirements #validation #ears #boundary

Ready to run

npx skills add https://github.com/miyamo2/braider --skill kiro-spec-requirements-miyamo2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiro-spec-requirements
Source: https://github.com/miyamo2/braider/tree/main/.gemini/skills/kiro-spec-requirements
Command: npx skills add https://github.com/miyamo2/braider --skill kiro-spec-requirements-miyamo2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of structured, verifiable requirements for a specification, reducing ambiguity and ensuring alignment with steering context.

Core Features & Use Cases

Load and interpret spec context (spec.json, brief.md, requirements.md) to seed the requirements drafting.
Apply EARS-compliant rules (ears-format.md) to produce observable acceptance criteria.
Generate a draft, boundary-aware requirements document and prepare it for formal review.

Quick Start

Run the kiro-spec-requirements workflow for your target spec to generate a draft requirements document.

Frequently Asked Questions about kiro-spec-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I draft observable requirements that reduce specification ambiguity?▼

Drafting observable requirements reduces specification ambiguity by applying EARS-compliant patterns to seed discovery from spec context sources, enforcing steering rules to produce testable, numerically identified acceptance criteria.

What is the EARS format for writing software specification requirements?▼

The EARS format structures software specification requirements by applying compliant rules to generate boundary-aware acceptance criteria, ensuring conditions are observable and verifiable for formal review.

How do I generate testable acceptance criteria from a project brief?▼

Generating testable acceptance criteria from a project brief involves loading spec context sources like brief.md and spec.json, then applying EARS-compliant patterns to produce numerically identified, boundary-aware requirements.

Does this requirements drafting workflow support existing spec.json files?▼

Yes, the requirements drafting workflow supports existing spec.json files by loading and interpreting them alongside brief.md and requirements.md to seed discovery and define boundaries for the specification draft.

What is the best way to enforce steering context rules when creating requirements documents?▼

Enforcing steering context rules when creating requirements documents is best achieved by interpreting spec context sources, applying EARS-compliant formats, and recording metadata to prepare a boundary-aware draft for formal review.

Why are numerically identified acceptance criteria needed for formal specification review?▼

Numerically identified acceptance criteria are needed for formal specification review to ensure each observable requirement is testable, traceable, and aligned with the project's steering context and boundary definitions.