skills.rest
ryowatanabe
ryowatanabeCOMMUNITY
Explore all skills by this author →
GitHub

kiro-spec-requirements

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

Updated Feb 25, 2024
Search Tags:#requirements#governance#spec#generate#ears#boundary
One-click install
npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-spec-requirements-ryowatanabe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-spec-requirements
Source: https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper/tree/main/.claude/skills/kiro-spec-requirements
Command: npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-spec-requirements-ryowatanabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate EARS-format requirements based on project description and steering context. Use when converting project briefs into structured acceptance criteria.

Core Features & Use Cases

  • Generate EARS-compliant requirements focused on user-observable behavior
  • Group related functionality into coherent requirement areas and clearly define boundaries
  • Update metadata and track generation status across phases

Quick Start

Provide the project description and steering context to generate an initial EARS-based requirements draft.

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 brief?▼

To generate EARS-format requirements, provide your project description and steering context to produce structured, testable acceptance criteria focused on user-observable behavior.

What is EARS requirement syntax used for in software governance?▼

EARS requirement syntax is used for software governance to convert project briefs into testable, non-technical acceptance criteria with clear boundaries across discovery, requirements, and design phases.

How do I group related functionality into coherent requirement areas?▼

Group related functionality into coherent requirement areas by applying boundary terminology across discovery and design, ensuring your requirements document defines clear scope for user-observable behavior.

Can I use project steering context to create testable acceptance criteria?▼

Yes, you can use project steering context to create testable acceptance criteria by applying the EARS format, which ensures requirements remain non-technical and focused on observable behavior.

What's the best way to track requirements generation status across project phases?▼

Track requirements generation status across project phases by updating metadata after the requirements review gate passes, ensuring the structured requirements document reflects the current governance state.

Related Skills

Explore More Product & Management Skills→
notta50notta50

kiro-spec-requirements

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

Community
Advanced
BarryYinBarryYin

kiro-spec-requirements

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

Community
Advanced
snicmakinosnicmakino
2

kiro-spec-requirements

Extract project briefs and steering context into EARS-format requirements.

Community
Advanced
JeffallanJeffallan
10.9k

feature-forge

Clarify feature requirements and write EARS-format specifications with acceptance criteria.

Community
Advanced