research-scope

Scoping a codebase topic involves a guided discussion to define a research objective, followed by a proposed outline and title. This process ensures alignment and reduces rework before any durable research files are created.

Outlining a bug investigation requires clarifying the topic scope and research objective through discussion first. You then receive a structured research-note outline to review before committing any notes to memory-bank.

Preparing a design review outline starts with a scoping discussion to define objectives. The system proposes a title and outline, then awaits your explicit confirmation before generating any research files.

Yes, the scoping workflow reads existing context directly from memory-bank to inform the discussion. It uses this context to propose a relevant research-note outline tailored to your codebase topic.

Yes, explicit human confirmation is enforced prior to creating any research entries. The workflow proposes a title and outline first, ensuring you approve the structure before notes are written to memory-bank.

You should scope a topic when investigating complex codebase issues or design reviews where misalignment is likely. This guided discussion defines objectives first, preventing rework on premature or incorrect research notes.