Skip to content
TrustedSkillsbeta
Back to all skills

Spec Gathering

Listed
oimiragieo·vlatest·writing

Spec Gathering efficiently extracts key details from text, streamlining research and providing focused information for analysis or documentation.

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 oimiragieo/agent-studio --skill spec-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

oimiragieo

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.

Nobody has reviewed this code. TrustedSkills indexes and links skills; it does not audit, run or scan them. A skill runs with whatever access you give your agent — read the source before you install it.

Automated safety checks

scanned

We could not read this skill's source, so none of the checks below were run.

Not scanned. none of the 73 skills in the repository match this slug — it was most likely renamed or removed upstream after the registry indexed it Source recorded as oimiragieo/agent-studio.
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, Spec Gathering, transforms vague task descriptions into actionable, structured requirements through a series of guided questions. It helps clarify user needs and validates those requirements before proceeding with detailed specification writing. The core principle is to ask smart questions and produce validated, structured output for improved clarity and efficiency.

When to use it

  • Starting a new feature or project.
  • Clarifying ambiguous task descriptions.
  • When users provide high-level goals without specifics.
  • Before beginning the process of writing detailed specifications.

Key capabilities

  • Structured questioning to elicit requirements.
  • Identification of affected services and scope based on project context and task description.
  • Workflow type determination (feature, refactor, investigation, migration, simple).
  • Integration with a "context-compressor" skill for progressive disclosure during clarification.
  • Reads project structure files (product.md, tech-stack.md) if they exist to understand the project context.

Example prompts

  • "I need to build a new user authentication system."
  • "Can you help me clarify the requirements for improving the search functionality?"
  • “What would you like to build or fix? Please describe the feature, bug, or change you need.”

Tips & gotchas

  • User confirmation of both the task description and workflow type is crucial before proceeding.
  • The skill relies on existing project structure files (.claude/context/product.md, .claude/context/tech-stack.md) for context; if these are missing, it will proceed without them.
  • This skill focuses solely on requirements gathering and validation – it does not write specifications.