requirements-definition

The phase sequence /define executes, so the command file does not restate it, plus question design and requirement formatting.

Read-only throughout: no file or memory is created or modified, and no code is written. Return the document in the response. Report any memory candidates for a later write-authorized phase.

Phases

prepare: Load serena-usage before any memory operation and any other companion this run needs: fact-check when a claim needs an external source, workflow-patterns for the shared decision-criteria structure. Then activate the project when Serena is available, check the memory catalog once, and read only relevant entries. If the store is unavailable, continue from repository evidence and report the limitation.

analyze: Extract the core requirements from the request, identify the technical constraints its context implies, name the design decisions that will need user input, and take a first read on feasibility.