User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation.
Install Requirements Elicitation
$ npx skills add rsmdt/the-startup --skill requirements-elicitation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rsmdt/the-startup requirements-elicitation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/team/skills/cross-cutting/requirements-elicitation .claude/skills/requirements-elicitation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "requirements-elicitation" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/team/skills/cross-cutting/requirements-elicitation into .claude/skills/requirements-elicitation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-elicitation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rsmdt/the-startup/tree/main/plugins/team/skills/cross-cutting/requirements-elicitationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rsmdt/the-startup --skill requirements-elicitation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rsmdt/the-startup requirements-elicitation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/team/skills/cross-cutting/requirements-elicitation .agents/skills/requirements-elicitation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "requirements-elicitation" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/team/skills/cross-cutting/requirements-elicitation into .agents/skills/requirements-elicitation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-elicitation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rsmdt/the-startup --skill requirements-elicitation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rsmdt/the-startup requirements-elicitation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/team/skills/cross-cutting/requirements-elicitation .cursor/skills/requirements-elicitation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "requirements-elicitation" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/team/skills/cross-cutting/requirements-elicitation into .cursor/skills/requirements-elicitation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-elicitation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rsmdt/the-startup.git --path plugins/team/skills/cross-cutting/requirements-elicitation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rsmdt/the-startup --skill requirements-elicitation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rsmdt/the-startup requirements-elicitation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/team/skills/cross-cutting/requirements-elicitation .gemini/skills/requirements-elicitation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "requirements-elicitation" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/team/skills/cross-cutting/requirements-elicitation into .gemini/skills/requirements-elicitation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-elicitation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rsmdt/the-startup requirements-elicitationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rsmdt/the-startup --skill requirements-elicitation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/team/skills/cross-cutting/requirements-elicitation .github/skills/requirements-elicitation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "requirements-elicitation" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/team/skills/cross-cutting/requirements-elicitation into .github/skills/requirements-elicitation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-elicitation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rsmdt/the-startup --skill requirements-elicitation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rsmdt/the-startup requirements-elicitation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/team/skills/cross-cutting/requirements-elicitation .opencode/skills/requirements-elicitation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "requirements-elicitation" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/team/skills/cross-cutting/requirements-elicitation into .opencode/skills/requirements-elicitation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-elicitation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
requirements-elicitation- GitHub stars
- 560
- Token cost
- ~1.3k tokens
- SKILL.md length
- 547 words
- Files
- 5
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- MIT
At a glance
Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation.
- Works in 5 steps: Assess Situation → Select Technique → Elicit Requirements → …
- Clarifying vague requirements
- SKILL.md covers Persona, Interface, Constraints and Reference Materials, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Requirements Elicitation is an agent skill from rsmdt/the-startup. Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation. Use when clarifying vague requirements, resolving conflicting needs, documenting specifications, or validating requirements with stakeholders.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `examples/interview-questions.md`, `examples/user-stories.md` and `reference/techniques.md`).
It sits in Product & Project Management, covering User stories. The repository describes itself as: The Agentic Startup - A collection of Claude Code commands, skills, and agents. The licence is MIT.
When your agent uses it
- Clarifying vague requirements
- Resolving conflicting needs
- Documenting specifications
- Validating requirements with stakeholders
Example prompts
- “/requirements-elicitation”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 88d447c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Requirements Elicitation loads about 1.3k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 547 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from rsmdt/the-startup at commit 88d447c, republished under its MIT licence (© rsmdt). 547 words, ~1,346 tokens.
Download SKILL.mdSave it as
.claude/skills/requirements-elicitation/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- requirements-elicitation
- description
- Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation. Use when clarifying vague requirements, resolving conflicting needs, documenting specifications, or validating requirements with stakeholders.
Persona
Act as a requirements analyst specializing in transforming vague ideas into clear, testable specifications. You systematically uncover root needs, resolve stakeholder conflicts, and produce documentation that aligns teams and guides implementation.
Elicitation Target: $ARGUMENTS
Interface
Requirement { id: string // REQ-001 format description: string source: string // stakeholder, observation, analysis priority: MUST | SHOULD | COULD | WONT status: DRAFT | REVIEWED | APPROVED | REJECTED | IMPLEMENTED | VERIFIED acceptanceCriteria: string[] testCases: string[]? }
StakeholderProfile { name: string role: string interest: HIGH | MEDIUM | LOW influence: HIGH | MEDIUM | LOW communication: string // frequency and channel }
ElicitationResult { requirements: Requirement[] stakeholders: StakeholderProfile[] openQuestions: string[] outOfScope: string[] }
State { target = $ARGUMENTS situation = null technique = null rawRequirements = [] requirements: Requirement[] stakeholders: StakeholderProfile[] openQuestions = [] }
Constraints
Always:
- Drill past surface requests to discover root needs (5 Whys or equivalent).
- Transform every abstract requirement into at least one concrete, testable scenario.
- Define explicit scope boundaries — what is in, out, and deferred.
- Document all assumptions and open questions visibly.
- Validate requirements against the review checklist before finalizing.
- Every requirement must have: ID, description, source, priority, acceptance criteria.
- Group requirements by feature area, not by stakeholder.
- Include an out-of-scope section to prevent scope creep.
Never:
- Accept solution-first requirements without uncovering the underlying need.
- Leave "common sense" requirements undocumented — make everything explicit.
- Add unrequested features beyond documented scope (gold plating).
- Use technical jargon when domain language would be clearer.
- Present requirements without acceptance criteria.
Reference Materials
- reference/techniques.md — 5 Whys, Concrete Examples, Boundary Identification, Stakeholder Interviews, Observation, Stakeholder Analysis, RACI, Conflict Resolution, Validation, Traceability
- reference/templates.md — User Story, Acceptance Criteria, Edge Cases, NFR, Feature Request, Requirements Document templates
Workflow
1. Assess Situation
Identify:
- What is being specified (feature, system, integration, change)
- Who the stakeholders are (interest × influence mapping)
- What information exists already vs what is missing
- Whether there are conflicting needs among stakeholders
match (situation) { vague request, unclear need => needs root cause analysis (5 Whys) abstract quality attributes => needs concretization multiple stakeholders disagree => needs conflict resolution well-defined but undocumented => needs formal documentation documented but unvalidated => needs validation review }
Show full SKILL.md (226 more words)Show less
2. Select Technique
match (situation) { unclear root need => 5 Whys — drill to underlying problem abstract requirements => Concrete Examples — make testable scope ambiguity => Boundary Identification — in/out/deferred new domain or stakeholder => Stakeholder Interview — structured extraction workflow optimization => Observation — watch real usage conflicting priorities => Conflict Resolution — find common ground }
Read reference/techniques.md for the selected technique. Read reference/templates.md for relevant templates.
3. Elicit Requirements
Apply selected technique per reference/techniques.md.
For each requirement discovered:
- Identify the root need (not the proposed solution).
- Make it concrete and testable.
- Define acceptance criteria (Given-When-Then).
- Identify edge cases and exceptions.
- Classify priority (Must/Should/Could/Won't).
- Note source and confidence level.
Accumulate open questions for anything unresolved.
4. Document Requirements
Structure requirements using templates from reference/templates.md:
- User stories for functional requirements
- NFR template for quality attributes
- Edge case tables for exception handling
- Traceability matrix linking requirements to sources
5. Validate Requirements
Apply review checklist from reference/techniques.md:
- Complete: everything needed documented?
- Consistent: no contradictions?
- Correct: matches stakeholder intent?
- Unambiguous: only one interpretation?
- Testable: can we verify it's met?
- Traceable: links to business goal?
- Feasible: can it be implemented?
- Prioritized: importance clear?
Flag any failing criteria. Suggest resolution for each gap.
Avoid anti-patterns:
- Solution First — ask "Why?" to find the real need
- Assumed Obvious — document everything explicitly
- Gold Plating — stick to documented requirements
- Moving Baseline — establish change control
- Single Stakeholder — ensure all perspectives represented
© rsmdt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files in plugins/team/skills/cross-cutting/requirements-elicitation of rsmdt/the-startup.
- SKILL.md
- examples/interview-questions.md
- examples/user-stories.md
- reference/techniques.md
- reference/templates.md
Open the folder on GitHubat commit 88d447c
Compare with similar skills
Requirements Elicitation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Requirements Elicitation this skillrsmdt/the-startup | 560 | — | ~1.3k | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| To Specbestofjs/bestofjs | 3.1k | 21 repos | ~757 | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
To Spec
bestofjs/bestofjs
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
More from rsmdt/the-startup
All 27 skills in this repoAnalyze
rsmdt/the-startup
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots.
Implement
rsmdt/the-startup
Implementation entry point. An agent skill from rsmdt/the-startup.
Implement Factory
rsmdt/the-startup
Factory loop orchestrator for multi-feature or multi-component implementation manifests.
Agentic Patterns
rsmdt/the-startup
Context enrichment for agentic AI application development using LangChain, Vercel AI SDK, and assistant-ui.
API Contract Design
rsmdt/the-startup
REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns.
Architecture Selection
rsmdt/the-startup
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria.
Related
Categories
Questions about Requirements Elicitation
What does Requirements Elicitation do?
Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation. Requirements Elicitation is an agent skill from rsmdt/the-startup. Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation.
When should I use Requirements Elicitation?
Requirements Elicitation fits situations like: clarifying vague requirements; resolving conflicting needs; documenting specifications; validating requirements with stakeholders.
How do I install Requirements Elicitation in Claude Code?
Run `npx skills add rsmdt/the-startup --skill requirements-elicitation -a claude-code`. Or copy the skill folder (plugins/team/skills/cross-cutting/requirements-elicitation in rsmdt/the-startup) into .claude/skills/requirements-elicitation in your project. Claude Code loads it when a task matches its description.
How do I install Requirements Elicitation in Codex?
Run `npx skills add rsmdt/the-startup --skill requirements-elicitation -a codex`. Or copy the skill folder (plugins/team/skills/cross-cutting/requirements-elicitation in rsmdt/the-startup) into .agents/skills/requirements-elicitation in your project. Codex loads it when a task matches its description.
Can I use Requirements Elicitation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rsmdt/the-startup --skill requirements-elicitation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/requirements-elicitation, .gemini/skills/requirements-elicitation, .github/skills/requirements-elicitation and .opencode/skills/requirements-elicitation in your project.
What does Requirements Elicitation need to run?
SKILL.md names no scripts, command-line tools or credentials: Requirements Elicitation is instructions for the agent only.
Does Requirements Elicitation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Requirements Elicitation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Requirements Elicitation use?
Requirements Elicitation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Requirements Elicitation use?
About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Requirements Elicitation?
Skills that share tags, products or a category with Requirements Elicitation: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Requirements Elicitation?
rsmdt (a GitHub user) maintains it in rsmdt/the-startup, which has 560 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on August 3, 2026.
Source: rsmdt/the-startup on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.