req-analysis
Domain: req · Model class: free
Description
Section titled “Description”Use this skill when the user wants to work on Extracting and structuring requirements from vague or incomplete user inputs. Triggers include “extract requirements from this description”, “structure these requirements”, “turn this brief into requirements”. Do NOT use when detect ambiguities (use core-ambiguity-detection).
Purpose
Section titled “Purpose”Extracting and structuring requirements from vague or incomplete user inputs. This skill provides structured guidance, references, and worked examples to help produce high-quality, actionable outputs.
Trigger Phrases
Section titled “Trigger Phrases”- “extract requirements from this description”
- “structure these requirements”
- “turn this brief into requirements”
- “requirements from user stories”
Anti-Triggers
Section titled “Anti-Triggers”- detect ambiguities (use core-ambiguity-detection)
- write acceptance criteria (use core-acceptance-criteria)
Intake Questions
Section titled “Intake Questions”- What is the user’s goal and current state?
- What constraints (time, team, compliance) apply?
- Are there existing artifacts (specs, code, benchmarks) to reference?
Output Contract
Section titled “Output Contract”- structured requirements
- constraints or acceptance criteria
- scope boundaries
- prioritized next actions
Related Skills
Section titled “Related Skills”req-ambiguity-detection · req-acceptance-criteria · req-scope