atlas-requirements-elicitation-requirements-elicitation
Systematic framework for analyzing product documents (PRDs, feature specs, user stories, roadmaps, one-pagers) to identify gaps, generate clarifying questions for PMs and engineers, and assess technical risks. This skill should be used when engineers or technical leads need to bridge PM documents and implementation by eliciting missing technical details rather than making assumptions. Use when asked to extract technical requirements, review specs, identify what's missing, or prepare clarifying questions from product documents.
Pinned to revision 2529473ff777, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/atlas-requirements-elicitation-requirements-elicitation/SKILL.md
- skills/atlas-requirements-elicitation-requirements-elicitation/ATTRIBUTION.md
- skills/atlas-requirements-elicitation-requirements-elicitation/LICENSE
- skills/atlas-requirements-elicitation-requirements-elicitation/assets/clarifying_questions_template.md
- skills/atlas-requirements-elicitation-requirements-elicitation/assets/gap_analysis_template.md
- skills/atlas-requirements-elicitation-requirements-elicitation/references/question_templates.md
- skills/atlas-requirements-elicitation-requirements-elicitation/references/risk_assessment.md
- skills/atlas-requirements-elicitation-requirements-elicitation/references/technical_dimensions.md
Every link opens the file at its source, pinned to the revision this page describes.