just-scope
Just Scope
Gather extensive requirements through relentless questioning and brainstorming with the user. Ground the discussion in the repo and record the entire agreed scope in docs/scope-<feature-name>.md, unless the user specifies another location.
This skill ends with the scope document. UI/UX design, architecture, program design, slicing and preparing tickets, implementation, quality assurance and delivery planning are outside its responsibilities.
Record exclusions the user chooses. Do not propose cuts, smaller versions, or phases.
If no repo can be found, inform the user about that fact and assume that the current working directory is equivalent to the repo for the purpose of this skill.
1. Ground the request
Read the repo's instructions, relevant docs, code, and tests. Read only enough to describe current behavior relevant to the feature or change being scoped and answer factual questions. Stop tracing a path once it no longer affects a requirement. Cite evidence as file paths with the function, class, or test name.
Check the target path as soon as the feature name is settled, using the user's requested path or docs/scope-<feature-name>.md by default. If the user supplies a path up front, check it immediately. Update an existing scope when requested, otherwise ask before replacing it. Preserve the existing file while awaiting the answer.
Finding facts is your job. Investigate what the repo can answer. Ask the user for goals and decisions. Keep questions that depend on unfinished research pending while advancing the rest.