Review, answer questions and resume development

Follow the recorded run when development needs input or stops. Keep the project identifier, run identifier and current question together.

1. Read project_status, story_status or conversion_status for the work you started.
2. Inspect pipeline_status for a returned run identifier.
3. Call next_question and show a pending question to the person who should decide.
4. Send answer_question with the supported answer fields and the same question identifier.
5. For delegated work, consume next_task and submit its result once using submit_task_result.
6. If a run is stopped and supports recovery, call resume_pipeline with that run identifier.
7. Follow status again and verify the resulting app.

Use the optional from argument only when the run’s recorded status and intended recovery justify restarting from that point. Do not choose an arbitrary stage name.

Polling can legitimately return no new task or question. Use the supported wait parameters and retain the existing run rather than starting a duplicate.

unlock_project_agent is an explicit recovery action for a stuck project lock and requires confirmation. Verify that you are not interrupting active work before asking a person to approve it.

For conversion, resolve its pending decision through proceed_conversion. Resuming a run does not replace the separate scope or cost confirmation. Read task and question tools.

Names and marks

OpenAI, ChatGPT and related OpenAI marks belong to OpenAI; Codex is an OpenAI product. Usage policy.

Claude and Claude Code are Anthropic products; their names and marks remain with their respective owner. Usage policy.

Node.js, npx names and any associated marks remain with their respective owners or project maintainers. References identify products, standards or source examples. OwlMeans documentation does not imply sponsorship or endorsement by those owners.