Multi-Role Spec and Task Breakdown
mylukin/agent-foreman
Runs a requirement through four research-backed specialist agents, a PM, a UX designer, a tech architect and QA, to produce implementable tasks.
Extract complete, unambiguous requirements from specifications.
Install Requirements Elicitation
$ npx skills add bitwarden/ai-plugins --skill requirements-elicitation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bitwarden/ai-plugins 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/bitwarden/ai-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/bitwarden-product-analyst/skills/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/bitwarden/ai-plugins/tree/main/plugins/bitwarden-product-analyst/skills/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/bitwarden/ai-plugins/tree/main/plugins/bitwarden-product-analyst/skills/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 bitwarden/ai-plugins --skill requirements-elicitation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bitwarden/ai-plugins requirements-elicitation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/bitwarden-product-analyst/skills/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/bitwarden/ai-plugins/tree/main/plugins/bitwarden-product-analyst/skills/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 bitwarden/ai-plugins --skill requirements-elicitation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bitwarden/ai-plugins requirements-elicitation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/bitwarden-product-analyst/skills/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/bitwarden/ai-plugins/tree/main/plugins/bitwarden-product-analyst/skills/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/bitwarden/ai-plugins.git --path plugins/bitwarden-product-analyst/skills/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 bitwarden/ai-plugins --skill requirements-elicitation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bitwarden/ai-plugins requirements-elicitation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/bitwarden-product-analyst/skills/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/bitwarden/ai-plugins/tree/main/plugins/bitwarden-product-analyst/skills/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 bitwarden/ai-plugins 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 bitwarden/ai-plugins --skill requirements-elicitation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/bitwarden-product-analyst/skills/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/bitwarden/ai-plugins/tree/main/plugins/bitwarden-product-analyst/skills/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 bitwarden/ai-plugins --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 bitwarden/ai-plugins requirements-elicitation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/bitwarden-product-analyst/skills/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/bitwarden/ai-plugins/tree/main/plugins/bitwarden-product-analyst/skills/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
- 154
- Token cost
- ~1.3k tokens
- SKILL.md length
- 412 words
- Files
- 2
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Extract complete, unambiguous requirements from specifications.
- Works in 6 steps: Read and Understand → Extract Explicit Requirements → Identify Implicit Requirements → …
- Analyzing feature requests
- SKILL.md covers Key Capabilities, Approach, Bitwarden-Specific… and Example, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Requirements Elicitation is an agent skill from bitwarden/ai-plugins, published by the product's own GitHub organization. Extract complete, unambiguous requirements from specifications. Use when analyzing feature requests, processing enhancement specifications, or identifying missing information. Trigger phrases: "extract requirements", "analyze specification", "identify requirements", "clarify ambiguities". After extracting requirements, use the work-breakdown skill.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `examples/export-functionality.md`).
It sits in Agent Workflows, covering Task breakdown. The repository describes itself as: AI plugin marketplace.
When your agent uses it
- Analyzing feature requests
- Processing enhancement specifications
- Identifying missing information
- Phrases: extract requirements
Example prompts
- “extract requirements”
- “analyze specification”
- “identify requirements”
- “/requirements-elicitation”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Read and Understand
- Extract Explicit Requirements
- Identify Implicit Requirements
- Flag Ambiguities and Gaps
- Document Constraints
- Create Acceptance Criteria
What it can do on your machine
Read from SKILL.md and the folder at commit 3e6bea3. 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 (its code samples are markdown).
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 95 tokens; SKILL.md has 412 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 412 words (~1,319 tokens).
- name
- requirements-elicitation
Files
SKILL.md and 1 other file in plugins/bitwarden-product-analyst/skills/requirements-elicitation of bitwarden/ai-plugins.
- SKILL.md
- examples/export-functionality.md
Open the folder on GitHubat commit 3e6bea3
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 skillbitwarden/ai-plugins | 154 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Multi-Role Spec and Task Breakdownmylukin/agent-foreman | 250 | — | ~5.1k | Automated safety check: Notes | None | |
| Scope KnifeMAGA2010/hackathon-run | 390 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Wayfinder Planning Mapsrengwu/wayfinder-maps | 138 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Roadmap Generatoralirezarezvani/claude-cto-team | 117 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Autospec Tasksariel-frischer/autospec | 144 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Scope Knife
MAGA2010/hackathon-run
Forces a KEEP, CUT, or DEFER decision on every feature when scope is too large, no MVP consensus exists, or time is running out.
Wayfinder Planning Maps
rengwu/wayfinder-maps
Plans work too big for one agent session as a shared map of investigation tickets, resolved one at a time until the route to the destination is clear.
Roadmap Generator
alirezarezvani/claude-cto-team
Generate phased implementation roadmaps with Epic/Story/Task breakdown, effort estimates, and validation checkpoints.
Autospec Tasks
ariel-frischer/autospec
Generate YAML task breakdown from implementation plan. An agent skill from ariel-frischer/autospec.
Oma Pm
first-fluke/oh-my-agent
Product manager that decomposes requirements into actionable tasks with priorities and dependencies.
More from bitwarden/ai-plugins
All 35 skills in this repo- Official
Reading Mailcatcher API
bitwarden/ai-plugins
Retrieves a link from Mailcatcher. An agent skill from bitwarden/ai-plugins.
- Official
Using Stripe CLI
bitwarden/ai-plugins
Query read-only Stripe test-mode data and advance an already-attached test clock.
- Official
Reviewing Claude Config
bitwarden/ai-plugins
Reviews Claude configuration files for security, structure, and prompt engineering quality.
- Official
Managing Workflow Secrets
bitwarden/ai-plugins
Bitwarden's canonical pattern for using a secret inside a GitHub Actions job: authenticate to Azure with the OIDC triad, pull the secret from an Azure Key Vault via the bitwarden/gh-actions…
- Official
Reviewing Security Architecture
bitwarden/ai-plugins
This skill should be used when the user asks to "review the security architecture", "check authentication patterns", "evaluate trust boundaries", "review encryption implementation", "assess…
- Official
Auditing External Claude Plugins
bitwarden/ai-plugins
Audits an external (third-party) Claude Code plugin pinned in this marketplace for security risk before it is vendored, and writes the report to a file for downstream posting.
Related
Questions about Requirements Elicitation
What does Requirements Elicitation do?
Extract complete, unambiguous requirements from specifications. Requirements Elicitation is an agent skill from bitwarden/ai-plugins, published by the product's own GitHub organization. Extract complete, unambiguous requirements from specifications.
When should I use Requirements Elicitation?
Requirements Elicitation fits situations like: analyzing feature requests; processing enhancement specifications; identifying missing information; phrases: extract requirements.
How do I install Requirements Elicitation in Claude Code?
Run `npx skills add bitwarden/ai-plugins --skill requirements-elicitation -a claude-code`. Or copy the skill folder (plugins/bitwarden-product-analyst/skills/requirements-elicitation in bitwarden/ai-plugins) 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 bitwarden/ai-plugins --skill requirements-elicitation -a codex`. Or copy the skill folder (plugins/bitwarden-product-analyst/skills/requirements-elicitation in bitwarden/ai-plugins) 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 bitwarden/ai-plugins --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 has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Requirements Elicitation use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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: Multi-Role Spec and Task Breakdown (mylukin/agent-foreman, 250 stars), Scope Knife (MAGA2010/hackathon-run, 390 stars), Wayfinder Planning Maps (rengwu/wayfinder-maps, 138 stars) and Roadmap Generator (alirezarezvani/claude-cto-team, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Requirements Elicitation?
bitwarden (a GitHub organization, an official publisher) maintains it in bitwarden/ai-plugins, which has 154 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 9, 2026.
Source: bitwarden/ai-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.