Workflows
Design a first task around one visible outcome
A small task reveals setup problems and unclear instructions faster than a broad assignment.
OfficeCubs · · 2 min read
A small task reveals setup problems and unclear instructions faster than a broad assignment. Pick an outcome with an obvious file and review method.
Start with a small handoff
Select a role by its working guide and deliverables, then verify the connected AI tool and workspace. Keep the first run small enough that you can inspect every output. The desktop needs to stay running while work executes. Marketplace sign-in, model access and file-generation tools are separate setup requirements; a success in one does not prove the others are ready.
Inputs for this workflow: One source document and one output requirement.
Work through the task
- Remove unrelated goals from the brief.
- Specify the destination and acceptance checks.
A brief you can adapt
Create a table of action items from notes.md in outputs/actions.md. Do not draft emails or alter the original notes.
The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.
Review the deliverable
Check every row and confirm that only the requested artifact was produced.
Where this approach can fail
A successful small task is a useful setup check, not a guarantee that a much larger task will succeed.
For the related desktop setup, see first task.