Written Workflow Brief
Use this to scope the pilot async. No call, meeting, calendar booking, phone screen, live walkthrough, or live onboarding is required.
How It Works
1. Fill the brief
Answer with safe, non-secret inputs. Use a public repo, test data, or sanitized example.
2. Confirm scope
The sprint proceeds only if the workflow can be handled async and proof can be captured honestly.
3. Pay deposit
Use the deposit link after the written scope is clear. No live call is part of the process.
Brief Template
Codex Operator Sprint written brief 1. Workflow: What recurring workflow should the sprint improve? 2. Example input: Give one safe test input, public link, sample file, or sanitized example. 3. Desired output: What should the final artifact look like? 4. Allowed tools/data: List only accounts, files, repos, docs, pages, or data that are safe to use. 5. Human-approved actions: What actions must stay explicitly approved before they happen? 6. Public-proof constraints: What must not appear in public proof, screenshots, logs, or docs? 7. Reviewer: Who reviews the final proof/handoff asynchronously? 8. Success condition: What would count as a useful proof that the workflow worked?
Hard Boundaries
Do not send secrets or production credentials.
No private customer data, payment details, API keys, password material, private screenshots, private inbox dumps, legal/security claims, or public claims without evidence.