wa:spec-scope

To define feature scope, you must capture a clear problem statement, measurable goals, and explicit non-goals to prevent scope creep. This structured approach aligns teams on boundaries and determines the appropriate solution shape for downstream planning.

Writing an FRD involves structuring problem statements, measurable goals, and explicit non-goals into a persistent document. This feature requirements document captures the agreed scope and solution shape to guide subsequent development stages.

Updating an existing feature requirements document involves revising or extending the scope while maintaining revision tracking. The process validates the updated problem statement and goals, persisting changes to the FRD file for subsequent spec workflows.

Yes, plan mode supports interactive user confirmation to validate feature goals and non-goals. It provides stage-based statusline updates during the scope definition process, ensuring you explicitly agree with the derived solution shape before persistence.

No, defining feature scope derives the appropriate solution type, such as a web app, API, or CLI, during the process. You provide the feature description, and the solution shape alignment determines the appropriate downstream architecture automatically.