project-intake

Clarify project scope for a vague feature request by walking through a structured intake checklist to document Goals, Non-Goals, Facts, and Unknowns. This ensures consistent coverage and reduces ambiguity before implementation begins.

Handle cross-agent handoffs by generating a concise intake document that captures assumptions, constraints, and a validation plan. This reduces ambiguity and provides a clear scoping path for downstream engineering or design tasks.

Align stakeholder goals and identify project unknowns by rapidly collecting consensus during initial intake meetings using a structured checklist. This outputs a clear validation plan to support scoping and estimation.

Use a checklist to estimate and start work on incomplete change requests by producing a validation plan alongside documented Facts and Unknowns. This allows the team to identify blockers and create a verification path before implementation.

You need a project intake checklist for requirements gathering when a stakeholder submits a request with incomplete details or when facing ambiguous change requests. It helps rapidly collect consensus and necessary assumptions to move from vague requests to actionable work.