scope
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.md, unless the user specifies another location.
This skill ends with the scope document. Slicing, cutting scope, preparing tickets, implementation, and delivery planning are outside its remit.
Record exclusions the user chooses. Do not propose cuts, smaller versions, or phases.
1. Ground the request
Read the repo's instructions, relevant docs, code, and tests. Read only enough to describe current behavior 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. If access to an existing repo is missing, request it and continue questions that do not depend on inspection.
If there is no repo, say so, skip the evidence steps, and ask the user where to save the document. If file access is unavailable, provide the document text and state that it has not been saved.
Check the target path early, using the user's requested path or docs/scope.md by default. If a file there describes different work, ask in the first round whether to replace it or use docs/scope-<feature-name>.md. 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.