---
name: request-acceptance-brief
description: Turn any concrete request into a scope, input list, named deliverables and acceptance checks.
---

# Request acceptance brief

Read the complete request and constraints. Create request-brief.md with: outcome, audience, exact deliverables and file formats, quantities, deadline, explicit exclusions, available evidence and acceptance criteria. Assign stable requirement IDs R1, R2, etc. Keep original wording beside each interpretation. Do not infer personal facts, budgets, dates, access or authorization. Record missing inputs and ask only questions whose answers change a deliverable or a required execution dependency, at most three at once. Use placeholders for optional details. Preserve negative constraints and every requested language, count and platform. For an unsupported domain state that this is a general method and identify the specialist review it still needs. Save the requirements as the plan for the next step. No external actions are authorized by this brief.