Skip to content
TrustedSkillsbeta
Back to all skills

Requirements Writing

Checked
kaakati·vlatest·writing

Crafts clear, concise, and testable software requirements from ambiguous user stories and stakeholder feedback.

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 kaakati/rails-enterprise-dev --skill requirements-writing -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-writing/SKILL.md
Scanned
2 files, 798 lines
Copies in repo
2 — all of them scanned
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 allows AI agents to generate clear and concise requirements documents. It can translate high-level goals into detailed, actionable steps for development teams. The generated documents include specifications, acceptance criteria, and other necessary details for successful project execution.

When to use it

  • New Project Kickoff: Generate a foundational requirements document before starting software development.
  • Feature Definition: Clearly outline the scope and functionality of a new feature or product enhancement.
  • Stakeholder Alignment: Create a shared understanding of expectations among stakeholders, developers, and project managers.
  • Gap Analysis: Identify missing information or potential issues by formally documenting existing needs.

Key capabilities

  • Generates requirements specifications
  • Defines acceptance criteria
  • Translates high-level goals into actionable steps

Example prompts

  • "Write a requirements document for a mobile app that allows users to track their daily water intake."
  • "Generate the acceptance criteria for the user authentication feature in our new web application."
  • “Create a detailed requirements specification for an API endpoint that retrieves customer data.”

Tips & gotchas

The quality of the generated requirements depends heavily on the clarity and detail provided in the initial prompt. Be as specific as possible about desired functionality and constraints to achieve optimal results.