Skip to content
TrustedSkillsbeta
Back to all skills

Requirements Gathering

Checked
aj-geddes·vlatest·productivity·MIT

This skill efficiently extracts user needs & specifications by prompting targeted questions, streamlining project planning and minimizing ambiguity.

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 aj-geddes/useful-ai-prompts --skill requirements-gathering -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

aj-geddes

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 aj-geddes/useful-ai-prompts at 3f5182cfd7.

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

Commit
3f5182cfd7
Manifest
skills/requirements-gathering/SKILL.md
Scanned
7 files, 460 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 systematically extract, clarify, and organize project needs from raw user input. It transforms vague requests into structured requirements suitable for planning or execution.

When to use it

  • You have a client providing a messy email about a new website but no clear scope.
  • A stakeholder describes a complex workflow verbally without defining specific constraints.
  • You need to convert a rough product idea into a checklist of functional and non-functional requirements.
  • An AI agent needs to pause execution to ask clarifying questions before generating code or content.

Key capabilities

  • Identifies missing information in ambiguous user prompts.
  • Structures unorganized thoughts into logical requirement categories.
  • Generates targeted follow-up questions to fill knowledge gaps.
  • Summarizes complex narratives into actionable bullet points.

Example prompts

  • "Act as a requirements analyst. Here is my rough idea for an app: [paste text]. List the missing details you need to build this."
  • "Convert this client email into a structured requirements document with sections for features, constraints, and success metrics."
  • "I want to automate my invoicing. Ask me 5 questions to gather all necessary requirements before suggesting a solution."

Tips & gotchas

Ensure the AI agent knows whether to output the final requirements list immediately or stop to ask clarifying questions first. For best results, provide context about the target audience or technical constraints alongside the raw request.