Skip to content
TrustedSkillsbeta
Back to all skills

Specify Requirements

Checked
rsmdt·vlatest·other·MIT

This skill extracts specific details from text to create a structured list of requirements, streamlining data organization and analysis.

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 rsmdt/the-startup --skill specify-requirements -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

rsmdt

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 rsmdt/the-startup at 88d447c7fb.

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

Commit
88d447c7fb
Manifest
plugins/start/skills/specify-requirements/SKILL.md
Scanned
8 files, 616 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 helps AI agents extract specific details from text to create structured Product Requirements Documents (PRDs). It acts as a product requirements specialist, focusing on defining what needs to be built and why it's important. The skill structures information around four key dimensions: what, why, who, and when. It is designed to exclude technical implementation details which belong in Software Design Documents (SDDs).

When to use it

  • When you need to organize unstructured text into a formal PRD format.
  • To clarify requirements for a new product or feature by defining user personas, journeys, and acceptance criteria.
  • When ensuring that documented requirements are MECE (Mutually Exclusive, Collectively Exhaustive).
  • To create a clear understanding of the problem being solved and its value proposition.

Key capabilities

  • Extracts information related to "what," "why," "who," and "when" from text.
  • Structures extracted data into PRD sections including user personas, journeys, feature requirements, and acceptance criteria.
  • Enforces the MECE principle for structured enumerations within the PRD.
  • Identifies areas needing clarification (using topic?: string in the PRDSection interface).

Example prompts

  • "Analyze this document and create a PRD outlining the requirements for a new mobile app."
  • "Based on this user feedback, generate a list of feature requirements and acceptance criteria."
  • "Extract the key personas and their journeys from this meeting transcript and structure them into a PRD section."

Tips & gotchas

  • This skill focuses solely on defining what needs to be built and why, excluding technical implementation details.
  • The output will adhere to the MECE principle, ensuring requirements are distinct and comprehensive.
  • If areas require further clarification, the agent will flag them using a topic field within the PRDSection.