requirements-elicitation
Installation
SKILL.md
Requirements Elicitation
Core Principle
The quality of requirements is determined by the quality of questions asked, viewed through multiple stakeholder lenses, and verified across all dimensions of completeness. This workflow transforms incomplete descriptions into actionable, comprehensive specifications.
When to Use This Workflow
- Receiving brief notes or incomplete descriptions
- Gathering requirements for new features or systems
- Reviewing existing specifications for completeness
- Requirements have gaps between stated need and actionable specification
- Unclear stakeholder intent or missing cross-functional requirements
- Temptation to "fill in" gaps with assumptions
- Before starting implementation of any significant feature
Related skills
More from 89jobrien/steve
meta-cognitive-reasoning
Meta-cognitive reasoning specialist for evidence-based analysis, hypothesis
176dead-code-removal
Detects and safely removes unused code (imports, functions, classes)
143file-converter
This skill handles file format conversions across documents (PDF, DOCX,
80python-scripting
Python scripting with uv and PEP 723 inline dependencies. Use when creating
77network-engineering
Network architecture, troubleshooting, and infrastructure patterns. Use
66golang-performance
Go performance optimization techniques including profiling with pprof,
57