Task Briefs and Examples

Definition

Task Briefs and Examples

A task brief is a compact specification for an agent run: goal, scope, relevant files, constraints, allowed actions, non-goals, acceptance criteria and required evidence. Good examples show both the desired output and the boundaries of acceptable implementation, which helps agents avoid broad rewrites, hidden assumptions and unverified claims of completion.

Why It Matters

A useful task brief separates outcome, user need, scope, constraints, acceptance criteria and verification. It gives the agent enough context to make local choices while keeping the human in charge of intent and risk.

# Outcome
Add document citations to the answer view.

# User need
Users must be able to inspect the source behind an AI-generated claim.

# Scope
- API response schema and web answer component
- Existing retrieval pipeline only

# Constraints
- Preserve backward compatibility
- No new production dependency
- Do not expose internal storage identifiers

# Acceptance criteria
- Every grounded claim can show one or more source links
- Missing citations degrade gracefully
- Contract and UI tests pass
- Accessibility is verified by keyboard

# Verification
- Run: npm test
- Run: npm run lint
- Render and inspect the answer view

Failure mode

The recurring risk is treating this concept as a label rather than an engineering decision with trade-offs, evidence needs and operational consequences.

Evaluation check

Ask what observable evidence would show that this concept has been applied well in a real system, repository or learning exercise.

Related Concepts

• The ten-step working method
• Acceptance criteria

Further study: OpenAI Codex task guidance and GitHub issue/PR templates for reproducible engineering work.