Generate an app and develop its user stories

Drive creation as a sequence you can review. Keep the returned project and story identifiers for later status checks.

1. Call describe_platform to inspect the available workflow.
2. Call create_project with a focused prompt.
3. Poll project_status for the returned projectId until the specification is ready.
4. Show the specification to the person requesting the app. Apply the supported changes when they ask for corrections.
5. Call confirm_project only after that review. Initialization builds the application foundation and screens.
6. Follow project_status until the project is ready for feature development.
7. Call list_stories, choose one useful story and review its wording.
8. Call develop_story for that story once, then follow story_status.
9. Try the completed behavior in the preview and check permissions.

{
  "prompt": "Create Task Grove, a task board for a small team. Members update their own tasks. Managers manage projects and all tasks. Include title, assignee, due date and status."
}

Screens can exist as placeholders before their stories are implemented. Review actual behavior before describing a feature as complete.

Use create_story or update_story for focused follow-up requirements. Read story tools and allowances. For delegated inference, the agent must continue handling tasks and questions while the run progresses.

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.