Tasks
A brief, a log, and a status that let people and agents continue each other's work.
Anatomy of a task.
A task belongs to one project and can't move. Its ref combines the project key and a number, such as web-app-3. Agents can use the ref instead of its ID.
- Brief: the current objective, constraints, and completion criteria.
- Log: updates with a summary, Markdown body, and the person and agent who wrote them.
- Status: where the work stands.
- Artifacts: deliverables saved to the task.
An initial task read includes the brief and recent updates. Focused reads and later pages may omit the brief.
The brief stays current.
When requirements change, update the brief and explain the change in a log entry. Agents can do both in one call. State the outcome, how to check it, and where it will be delivered.
Statuses.
Venom's agent guidance uses these meanings. Your organization can add its own conventions in skills.
| Status | Meaning |
|---|---|
open | Agreed, but not started. |
in_progress | Started; work or verification remains. |
blocked | Something prevents the next step. Record what will unblock it. |
done | Delivered and checked, with evidence in the outcome entry. |
cancelled | Intentionally stopped. Record why. |
Each status change has an explanatory entry. Completions, cancellations, and reopenings also appear in the project Log.
For software delivery, the default workflow includes deployment and verification in the agreed environment, unless the user scoped the task to an earlier deliverable. A research task can finish when its report is available and checked.
What belongs in the log.
Save outcomes, decisions and their reasons, useful evidence, blockers, and next actions. Skip routine tool calls and transcripts; never include secrets. Link to large outputs or save an artifact.
Summary: Payment step moved behind the new-checkout flag
Card form now renders inside the single-page flow. Stripe test cards pass
locally (12/12). Apple Pay still uses the old path.
Next: wire Apple Pay, then deploy to staging and run the checkout smoke test.Editing and recovery.
Entries can be corrected or deleted; the brief can be corrected but not deleted. Replaced and deleted text is recoverable for 30 days. Restoring an entry restores its text and visibility, not task status or external work.