skills.rest
BarryYin
BarryYinCOMMUNITY
Explore all skills by this author →
GitHub

kiro-spec-requirements

Generate EARS-format requirements documents from project descriptions and steering context.

Updated Apr 17, 2026
Search Tags:#spec-driven#requirements#generate#ears#hermes#requirements-review
One-click install
npx skills add https://github.com/BarryYin/Hermes-sdd --skill kiro-spec-requirements-barryyin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-spec-requirements
Source: https://github.com/BarryYin/Hermes-sdd/tree/main/skills/kiro-spec-requirements
Command: npx skills add https://github.com/BarryYin/Hermes-sdd --skill kiro-spec-requirements-barryyin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns project descriptions and steering context into clear, testable EARS-format requirements, reducing ambiguity and ensuring requirements are reviewable and machine-readable for downstream design and implementation.

Core Features & Use Cases

  • Draft Requirements: Produce grouped, EARS-compliant acceptance criteria and a requirements draft for a feature stored under .kiro/specs.
  • Quality Gate & Metadata: Run a requirements review gate enforcing numeric headings, testability, and EARS syntax, then update spec.json metadata and write requirements.md only after passing.
  • Context-Aware Research: Optionally delegate subagents to scan code, steering docs, or web resources to inform requirement scope for brownfield projects.

Quick Start

Ask the kiro-spec-requirements skill to generate EARS-format requirements for a named feature using the project's steering context and spec metadata.

Frequently Asked Questions about kiro-spec-requirements

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

FAQPage Schema
How do I generate EARS-format requirements from a project description?▼

To generate EARS-format requirements, provide a feature-level project description and steering context. The skill drafts grouped, EARS-compliant acceptance criteria stored under .kiro/specs for spec-driven development workflows.

What is the EARS syntax for writing testable acceptance criteria?▼

EARS syntax structures acceptance criteria into unambiguous, testable requirement statements. It enforces numeric headings and specific phrasing patterns, ensuring requirements are machine-readable and reviewable for downstream design and implementation.

How do I enforce a requirements review gate before finalizing spec metadata?▼

A requirements review gate enforces numeric headings, testability, and EARS syntax validation. It updates spec.json metadata and writes requirements.md only after all acceptance criteria successfully pass the quality checks.

Can I generate requirements for brownfield projects by scanning existing code?▼

For brownfield projects, subagents can optionally scan existing code, steering docs, and web resources. This context-aware research informs the requirement scope, producing EARS-compliant acceptance criteria that match the current codebase.

Do I need spec-driven development setup to use EARS requirements generation?▼

Spec-driven development setup under .kiro/specs is required. The skill applies to feature-level specs, utilizing spec.json metadata and steering context to draft, review, and finalize EARS-compliant acceptance criteria accurately.

Related Skills

Explore More Product & Management Skills→
taku-otaku-o
1

kiro-spec-requirements

Generate EARS-format requirements drafts from project specs and steering files.

Community
Advanced
skanehiraskanehira
88

requirements-analysis

Analyze ambiguous requests and generate TODO.md and DESIGN.md plans.

Community
Basic
gotalabgotalab
3.6k

kiro-spec-requirements

Generate EARS-format requirements and update spec.json metadata.

Community
Advanced
notta50notta50

kiro-spec-requirements

Translate project briefs and steering context into EARS-format requirements drafts.

Community
Advanced