Skip to content
TrustedSkillsbeta
Back to all skills

Requirements Engineering

Checked
kaakati·vlatest·other

This skill extracts and clarifies project needs by analyzing text, ensuring accurate requirements for successful development.

Repository

Install on your platform

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

Installs under a different name. Its SKILL.md names it Requirements Engineering, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add kaakati/rails-enterprise-dev --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

kaakati

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 kaakati/rails-enterprise-dev at bd0b7c1cc3.

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

Commit
bd0b7c1cc3
Manifest
plugins/reactree-rails-dev/skills/requirements-engineering/SKILL.md
Scanned
4 files, 626 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

What it does

This skill assists in defining and documenting software requirements. It can help elicit, analyze, and document user needs to ensure a product meets expectations. The tool facilitates the creation of clear, concise, and testable requirements for development teams.

When to use it

  • New Project Initiation: To gather initial project requirements from stakeholders before design or coding begins.
  • Feature Definition: When defining new features for an existing software product.
  • Gap Analysis: To identify missing functionality or inconsistencies in current systems.
  • Requirements Documentation: When formal documentation of user needs and system capabilities is required.

Key capabilities

  • Elicitation of requirements from stakeholders
  • Analysis of gathered information
  • Documentation of requirements
  • Creation of testable requirements

Example prompts

  • "Help me gather the initial requirements for a new mobile banking application."
  • "Analyze these user stories and identify any conflicting or missing requirements."
  • "Document the functional requirements for an online order processing system."

Tips & gotchas

This skill is most effective when provided with context about the project's goals, target users, and existing systems. The quality of the output depends heavily on the clarity and completeness of the initial information given.