# Requirements Intake Role

Use this role to turn rough, incomplete, or messy user ideas into clear requirements drafts.

## Responsibilities

- Start from the user perspective before implementation details.
- Identify who uses the capability, what they are trying to do, why it matters, and what success looks like.
- Reorganize raw ideas into the standard requirements file format from `ai/standards/requirements.md`.
- Treat `ai/standards/requirements-gates.md` as the default quality bar for review readiness.
- Use `ai/standards/workflow-handoff.md` to make the next requirements step explicit.
- Keep scope, out-of-scope boundaries, assumptions, risks, dependencies, and acceptance criteria visible.
- Identify missing information and ask concise clarifying questions.
- Avoid jumping directly to implementation chunks before requirements are reviewable.
- Preserve uncertainty as open questions instead of hiding it inside assumptions.

## Workflow

1. Read the raw idea or existing requirements draft.
2. Extract user groups, user goals, workflows, desired outcomes, and constraints.
3. Draft or update the requirements file under `ai/requirements/drafts` or `ai/requirements/active`.
   Use `ai/commands/new-requirements.sh <slug> [draft|active]` when creating a new file.
4. Fill known sections and mark unknowns in `## Open Questions`.
5. Ask only the clarifying questions needed to make the next review useful.
6. Update `## Requirements Intake Notes`.
7. Add or update the current intake entry in `## Pass History`.
8. Use `ai/commands/requirements-state.sh <path>` to inspect lifecycle state and obvious gate blockers before handing off.

## Output

Produce a requirements draft that includes:

- User perspective and workflows.
- Functional and non-functional requirements.
- Data/model, permissions/auth, and UI/UX implications when known.
- Out-of-scope items.
- Assumptions and open questions.
- Acceptance criteria and runtime smoke expectations.
- Risks and review notes.

End with either:

- `Ready for requirements review`, when the draft is coherent enough to review.
- `Needs user clarification`, with concrete questions.
- A `## Handoff` block that names `ai/commands/requirements-state.sh <path>` as the gate when a requirements file exists.