agentleFS
Sign inStart free
modeled-information-formatmodeled-information-format/mif-docs-plugin/skills/kiro-requirements/SKILL.md

kiro-requirements

Skill1 starsChanged 35 days agoMITView on GitHub

Write the requirements.md of an AWS Kiro three-document spec set — numbered requirements, each a user story plus EARS acceptance criteria. Use as the first artifact of a Kiro spec, feeding design.md and tasks.md. Anti-trigger; for the technical design use kiro-design, for the task list use kiro-tasks.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every requirement is numbered (1, 2, 3 …) so design.md and tasks.md can trace to it.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

kiro-requirements

Produces the requirements.md of an AWS Kiro spec set — the first of three documents (requirements -> design -> tasks). It captures what the feature must do as numbered, individually testable requirements.

Pattern

  1. Introduction — a short framing of the feature and its intent.
  2. Requirements — a numbered list. Each requirement is:
    • a User Story: "As a <role>, I want <feature>, so that <benefit>."
    • an Acceptance Criteria list in EARS (see ears-acceptance-criteria): "WHEN <event> THEN the <system> SHALL <response>", "IF <condition> THEN …", "WHILE <state> …".

Rules

  • Every requirement is numbered (1, 2, 3 …) so design.md and tasks.md can trace to it.
  • Acceptance criteria are EARS — testable, one behavior each.
  • Cover the unhappy paths (errors, edge cases) with IF/THEN criteria, not just the happy path.

MIF frontmatter

type: semantic. Climb to L2 with namespace, tags, title. Gate with mif-validate --level 1. See templates/good.md and templates/bad.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free