Operator craft

Write better AI task briefs

By Justin Helmer · 8 August 2026 · ~15 minute read

Most “the agent failed” stories start as vague human briefs. Models fill gaps with guesses. Coding agents invent success. This guide is a reusable brief format used on chatagent.ca projects and Continuum seals.

The six-block brief

1. Goal — one sentence, observable outcome.
2. Why now — context in three lines max.
3. Inputs — paths, URLs, pasted excerpts (no secrets).
4. Constraints — stack, style, banned actions, privacy.
5. Done checks — bullets a skeptic can verify.
6. Handoff — who receives what next.

Copy-paste template

GOAL:
WHY NOW:
INPUTS:
CONSTRAINTS:
- no network unless stated
- no secrets in chat
DONE CHECKS:
- [ ] …
CONTINUUM CLAIMS (optional):
- file_exists: …
- file_contains: …
HANDOFF:
- next owner:
- packet:

Examples

Documentation brief

Goal: “Publish a 800+ word guide on X with internal links.” Done checks: word count, TOC, author box, sitemap entry. Constraints: original prose, no scraped copies.

Code brief

Goal: “Add Continuum sample claims for the login module.” Done checks: self_check passes, capsule seals green, README note. Constraints: stdlib only.

Review brief

Goal: “Δ9RA pass on this release note.” Done checks: list of overclaims removed, evidence links added.

Why this helps AdSense-quality publishing too

Clear briefs produce specific articles and tools. Thin sites often ship features without explaining them. On chatagent.ca, every major tool should earn a guide with templates, limits, and human responsibility language.