requirements-clarification

To break down a vague implementation request into atomic requirements, decompose the raw instruction into individual needs and normalize each into fixed records with explicit attribute statuses like user_provided, repo_derivable, public_fact, or unknown.

Normalizing ambiguous requirements involves splitting a raw instruction into atomic needs and assigning each an explicit attribute status, producing an execution-ready artifact that reduces ambiguity and guides downstream planning.

Assigning attribute statuses to incomplete requirements involves categorizing each atomic need as user_provided, repo_derivable, public_fact, or unknown, ensuring explicit tracking of missing information before execution begins.

Clarified requirements artifacts are written to .opencode/work/req-requirements-clarification.md, providing a normalized record of atomic needs alongside a single handoff recommendation for downstream execution.

Use a requirements clarification process for ordinary implementation-shaped tasks where the initial instruction is incomplete, ambiguous, or contains multiple atomic needs that require decomposition before execution.

Processing multiple atomic needs within a single request involves splitting the raw instruction into individual atomic requirements, normalizing each into fixed records, and assigning explicit attribute statuses to prepare them for execution.