Create Product Requirement Document

Produce it_{current_iteration}_product-requirement-document.md in .agents/flow/ by interviewing the user about the feature or change they want to build.

Important: Do NOT start implementing. Just gather the requirement and write the document.

The Job

1. Check if .agents/state.json exists. If it does, read it to obtain current_iteration (and any other required fields). If it does not exist, ask the user to provide the required information:
   • A. Enter the 6-digit iteration number (e.g. 000037)
2. Understand the project first. Read AGENTS.md, .agents/PROJECT_CONTEXT.md, and explore the codebase structure (main entry points, conventions, existing features) before starting the interview. This context will make your questions more relevant and the PRD better aligned with the project.
3. Ask 3–5 clarifying questions (see Questions Flow).
4. Generate the document following the Output Structure.
5. Write to .agents/flow/it_{current_iteration}_product-requirement-document.md.
6. If .agents/state.json exists, update it: requirement_definition.status = "in_progress", requirement_definition.file = filename. If it does not exist (standalone mode), skip this step and notify the user: "Running standalone — state.json not found, skipping state update."