requirements-elicitation
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 with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "requirements-elicitation" from https://skillstore.io/skills/doubleslashse-requirements-elicitation.md and its manifest at https://skillstore.io/api/skills/doubleslashse-requirements-elicitation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "requirements-elicitation". Stakeholder says checkout must be faster and support guest purchases.
Expected outcome:
- Functional requirement: Customers can complete checkout without creating an account.
- Non-functional requirement: Checkout response time target needs a measurable threshold.
- Follow-up question: What checkout duration is acceptable for the main customer segment?
Using "requirements-elicitation". Team wants to replace an internal reporting tool but has unclear scope.
Expected outcome:
- Current state: Reporting depends on manual spreadsheet updates.
- Desired state: Users can generate approved reports from trusted system data.
- Gap: Ownership, source systems, retention rules, and rollout timing need confirmation.
Using "requirements-elicitation". Product manager has a backlog with mixed priorities.
Expected outcome:
- Must have: Items needed for launch or compliance.
- Should have: Items with strong value but manageable delay impact.
- Could have: Items that improve experience but do not block core outcomes.
Security Audit
SafeAll 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.
Risk Factors
⚙️ External commands (7)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/doubleslashse-requirements-elicitation/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/doubleslashse-requirements-elicitation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/doubleslashse-requirements-elicitation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/doubleslashse-requirements-elicitation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/doubleslashse-requirements-elicitation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
DoubleslashSE. (2026). requirements-elicitation security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/doubleslashse-requirements-elicitation/audits/8BibTeX citation
@techreport{doubleslashse-doubleslashse-requirements-elicitation-2026,
author = {DoubleslashSE},
title = {requirements-elicitation security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/doubleslashse-requirements-elicitation/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "requirements-elicitation security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "DoubleslashSE"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/doubleslashse-requirements-elicitation/audits/8"
identifiers:
- type: other
value: "skillstore:doubleslashse-requirements-elicitation:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
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.
Try These Prompts
Help me prepare questions for a new software project. The product idea is [summary]. Ask about users, goals, scope, and success criteria.
Review these stakeholder notes: [notes]. Group findings into functional requirements, non-functional requirements, constraints, assumptions, and open questions.
Compare our current state [current] with desired state [desired]. Identify gaps, missing stakeholders, risky assumptions, and follow-up questions.
Turn this discovery material into prioritized requirements with business objectives, user stories, acceptance criteria, validation checks, and traceability links: [material].
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.
Avoid
- 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.
Frequently Asked Questions
What does this skill help me do?
Can it create user stories?
Does it cover non-functional requirements?
Can it support existing system replacement?
Does it make final project decisions?
How should I prepare inputs?
Developer Details
Author
DoubleslashSELicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
72d5025b022c77f7a51bdf5c1637c689c80e89d1
Maintenance freshness
7/18/2026
Usage
8 downloads · 197 views
File structure