Clarify Scope

Prompt file imported from LazyWorkshopCreate/agent-based-workflow (.github/prompts/clarify-requirement-scope.prompt.md). Copyright stays with the author.

Clarify one ambiguous request, capability, or feature scope before technical design starts.

Requirements:

• Read workspace instructions.
• Read requirements clarification module.
• Read the relevant live baseline in docs/design/, docs/plans/, and docs/status/ before drawing conclusions.
• Use docs/reference/ only as supporting evidence, not as runtime dependencies.
• Make the following explicit: target outcome, owning service or module, in-scope work, out-of-scope work, tenant and authorization boundaries, acceptance signals, assumptions, unresolved questions, and missing evidence.
• When more than one viable ownership split, scope boundary, or delivery interpretation exists, write 2-3 concrete options and recommend one path.
• If evidence provenance is the blocker, use trace-evidence-workflow for that evidence question and then return to this clarification result rather than producing competing scope notes.
• If the ambiguity is still blocking, keep the result as a clarification note rather than forcing a design conclusion.
• Keep active documentation in English.

Expected output:

• Produce or update a clarification note using the repository template at docs/templates/REQUIREMENT_CLARIFICATION_TEMPLATE.md.
• State which live document should be updated next: docs/design/, docs/decisions/, docs/plans/, or docs/status/outstanding-items.md.
• End with one of three outcomes: ready-for-design, needs-targeted-evidence, or blocked.