req-scope
Domain: req · Model class: free
Description
Section titled “Description”Use this skill when the user wants to work on Explicitly bounding work, separating must-haves from nice-to-haves, and preventing scope creep. Triggers include “clarify the scope”, “what is in and out of scope”, “bound the work”. Do NOT use when extract requirements (use core-requirements-analysis).
Purpose
Section titled “Purpose”Explicitly bounding work, separating must-haves from nice-to-haves, and preventing scope creep. This skill provides structured guidance, references, and worked examples to help produce high-quality, actionable outputs.
Trigger Phrases
Section titled “Trigger Phrases”- “clarify the scope”
- “what is in and out of scope”
- “bound the work”
- “prevent scope creep”
- “must-have vs nice-to-have”
Anti-Triggers
Section titled “Anti-Triggers”- extract requirements (use core-requirements-analysis)
- frame strategic decision (use core-strategy-advisor)
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