# Elicit Clear Software Requirements

Requirements work often stalls when stakeholder input is vague or incomplete. This skill provides interview structures, question prompts, and validation methods for usable requirements.

## Install

```bash
npx skillstore add doubleslashse/requirements-elicitation
```

## Metadata

- Status: approved
- Slug: doubleslashse-requirements-elicitation
- Skillstore revision: r1
- Version status: missing
- Tree hash: 031e0afd0f74be7037e00a20c0b58eb97d2422847f3d826389aeac67999575dd
- Author: DoubleslashSE
- GitHub username: DoubleslashSE
- License: MIT
- Repository: https://github.com/DoubleslashSE/claude-workflows/tree/main/Plugins/business-analyst/skills/requirements-elicitation
- Ref: 72d5025b022c77f7a51bdf5c1637c689c80e89d1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/doubleslashse-requirements-elicitation
- Manifest: https://skillstore.pages.dev/api/skills/doubleslashse-requirements-elicitation/manifest

## Capabilities

- Provides structured interview techniques for gathering stakeholder needs.
- Separates functional requirements, non-functional requirements, constraints, and assumptions.
- Uses MoSCoW and value versus effort methods for prioritization.
- Supports gap analysis between current and desired system states.
- Defines output formats for requirement lists, user stories, and traceability.
- Offers role-based and scenario-based question templates.

## Use Cases

- Run Stakeholder Interviews: Prepare focused questions for business owners, users, technical teams, operations, and external stakeholders.
- Shape MVP Scope: Separate must-have launch needs from future enhancements using scope, value, effort, and assumption checks.
- Clarify Delivery Requirements: Convert discovery notes into user stories, acceptance criteria, and traceable requirements for implementation planning.

## Prompt Templates

### Start a Requirements Interview

```
Help me prepare questions for a new software project. The product idea is [summary]. Ask about users, goals, scope, and success criteria.
```

### Classify Stakeholder Notes

```
Review these stakeholder notes: [notes]. Group findings into functional requirements, non-functional requirements, constraints, assumptions, and open questions.
```

### Find Requirement Gaps

```
Compare our current state [current] with desired state [desired]. Identify gaps, missing stakeholders, risky assumptions, and follow-up questions.
```

### Build Traceable Requirements

```
Turn this discovery material into prioritized requirements with business objectives, user stories, acceptance criteria, validation checks, and traceability links: [material].
```

## Limitations

- Does not replace direct stakeholder validation or domain expert review.
- Does not generate legally binding specifications without human approval.
- Does not inspect live systems unless the user provides documents or access.
- Does not estimate delivery timelines beyond supplied project context.

## Best Practices

- Start with open questions, then narrow details through role-specific follow-up.
- Validate each requirement for clarity, measurability, traceability, and testability.
- Record assumptions and open questions beside the related requirement.

## Anti Patterns

- Do not treat vague stakeholder preferences as confirmed requirements.
- Do not skip non-functional needs such as security, performance, reliability, and supportability.
- Do not prioritize features without business value, effort, and risk context.

## Security Audit

- Audited at: 2026-07-06T11:27:22.262\+00:00
- Summary: All seven static findings are false positives caused by Markdown code fences in SKILL.md. The skill contains business-analysis guidance and question templates, with no evidence of prompt injection, credential handling, network access, or command execution.

## Stats

- Views: 197
- Downloads: 11
- Favorites: 0
- Popularity score: 0