Engineering
Client feedback to Codex prompt: an orchestrator, intake, and PM bot chain
Client feedback arrives in one place, tasks live in another, and briefs get written last.
What hurt
Snapper AI (@SnapperAI) built a team of bots to run web dev projects that hand off work to each other in a shared room. Not affiliated with xAI.
What to install or create
The Orchestrator picks up client feedback from Vercel, Client Intake logs it as a task in Notion, and the Website PM writes the brief and drafts the Codex prompt. If something's unclear, the PM asks a follow-up question before going ahead.
Bots
Orchestrator
Collects client feedback.
Client Intake
Logs feedback as Notion tasks.
Website PM
Writes the brief and drafts the Codex prompt.
Plugins
Notion
Optional
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/SnapperAI/status/2108562550438908261 (credit @SnapperAI).
- 2Create three bots with one job each: collect feedback, log tasks, write briefs.
- 3Put them in one shared room so handoffs are visible.
- 4Tell the PM to ask a question whenever a request is unclear.
- 5Review each drafted Codex prompt before running it.
Approval fence
The chain drafts briefs and prompts; you decide what gets built and shipped.
What to tweak
Make "ask before going ahead" part of the PM's job.
Source
Snapper AI @SnapperAI · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.