This skill should be used when the user needs to "clarify requirements", separate "functional vs non-functional requirements", "scope the problem", figure out "what questions should I ask", state the "requirements for <X>", or otherwise pin down a vague design prompt before building. It turns an ambiguous ask into functional requirements, non-functional constraints, and an explicit out-of-scope. Use it whenever a prompt is broad or under-specified ("design Twitter", "build a chat app") even if the user doesn't say "requirements".
$npx -y skills add proyecto26/system-design-skills --skill requirements-scopingInstalls into the current project.
Run `npx skills use "https://github.com/proyecto26/system-design-skills" --skill "proyecto26/system-design-skills/requirements-scoping"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/proyecto26/system-design-skills" that are relevant to the current task. Run `npx skills add "https://github.com/proyecto26/system-design-skills"` and select the relevant skills, then follow their instructions.