Skip to content
TrustedSkillsbeta
Back to all skills

Requirements Engineering

Checked
jasonkneen·vlatest·other·MIT

This skill extracts key needs and constraints from user input to build clear, actionable requirements – crucial for successful project outcomes.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jasonkneen/kiro --skill requirements-engineering -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jasonkneen

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jasonkneen/kiro at 22577b636d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
22577b636d
Manifest
skills/requirements-engineering/SKILL.md
Scanned
1 file, 241 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The requirements-engineering skill provides a framework for AI agents to systematically analyze, document, and manage project specifications. It enables agents to break down complex user needs into actionable technical tasks and maintain structured requirement artifacts throughout the development lifecycle.

When to use it

  • Translating vague stakeholder requests into detailed functional and non-functional requirements.
  • Generating comprehensive checklists to ensure all project constraints are met before coding begins.
  • Updating documentation dynamically as project scope evolves during iterative development.
  • Validating that proposed solutions align with initial business goals and technical standards.

Key capabilities

  • Systematic requirement elicitation and analysis.
  • Structured documentation of functional and non-functional specs.
  • Task decomposition based on defined constraints.
  • Iterative refinement of project scope and deliverables.

Example prompts

  • "Analyze this user story and generate a detailed requirements document including acceptance criteria."
  • "Break down the feature request for 'user authentication' into specific technical tasks and prerequisites."
  • "Review our current project requirements against these new compliance regulations and suggest necessary updates."

Tips & gotchas

This skill is most effective when paired with clear initial context about the project domain. Ensure you provide sufficient background information on existing constraints, as the agent relies on this data to generate accurate and relevant engineering specifications.