skills.rest
I2olanD
I2olanDCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requirements-elicitation

Transform vague requirements into clear, testable specifications using elicitation techniques and documentation templates.

Updated Dec 28, 2025
Search Tags:#requirements#traceability#elicitation#user-stories#acceptance-criteria#stakeholders
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill requirements-elicitation-i2oland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-elicitation
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/requirements-elicitation
Command: npx skills add https://github.com/I2olanD/dotfiles --skill requirements-elicitation-i2oland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams transform vague ideas into clear, testable requirements that align stakeholders and guide implementation.

Core Features & Use Cases

  • Structured elicitation: The 5 Whys, boundary identification, stakeholder interviews, and observation/shadowing to uncover root needs.
  • Documentation and traceability: User stories with acceptance criteria, non-functional considerations, and a traceability mindset.
  • Validation and governance: Prototype validation, review checklists, and conflict resolution templates to ensure alignment before delivery.

Quick Start

  • Review the elicitation guide and templates.
  • Conduct a stakeholder interview using the included prompts, then draft user stories with acceptance criteria.
  • Validate requirements with a lightweight prototype or formal review, updating the traceability matrix as needed.

Frequently Asked Questions about requirements-elicitation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write clear acceptance criteria from vague stakeholder requests?▼

Requirements traceability is maintained by mapping elicited user stories and acceptance criteria to stakeholder needs using a traceability matrix. This tracks requirement origins and validation status throughout the product delivery lifecycle.

What elicitation techniques help uncover root needs during stakeholder interviews?▼

Elicitation techniques that help uncover root needs during stakeholder interviews include the 5 Whys, boundary identification, observation, and shadowing. These methods clarify vague ideas and align stakeholders on testable specifications.

How do I validate requirements with stakeholders before development starts?▼

To validate requirements with stakeholders before development starts, use prototype validation, formal review checklists, and conflict resolution templates. This governance process ensures alignment and catches discrepancies early in the elicitation phase.

What is the best way to document non-functional considerations for product teams?▼

The best way to document non-functional considerations for product teams is to integrate them directly into user story documentation alongside functional acceptance criteria. This captures system constraints during the elicitation process.

Can I use requirement documentation templates for resolving stakeholder conflicts?▼

Yes, you can use requirement documentation templates for resolving stakeholder conflicts by applying included conflict resolution templates and review checklists. These governance tools ensure alignment during the elicitation and validation phases.

Related Skills

Explore More Education & Research Skills→
co-cddoco-cddo
4

bmad-agent-analyst

Translate vague business needs into detailed, actionable requirements.

Official
Advanced
onshoreoutsourcingonshoreoutsourcing

requirements-coverage-analysis

Analyze business requirements coverage across feature plans and wave plans.

Official
Intermediate
theandyalvarez7-rubytheandyalvarez7-ruby

agile-product-owner

Turn epics into structured user stories with INVEST-aligned acceptance criteria.

Community
Advanced
qa-amanqa-aman
19

requirements-elicitation

Facilitate structured stakeholder requirement elicitation across interviews, workshops, observation, and document analysis.

Community
Advanced