Skip to main content
Reference — generated from the toolkit

Source of truth: toolkit/prompts/engineering/task-brief.md. Edit it there; this page is regenerated on build.

Agent task brief

Purpose: the standard brief that directs an agent to build one task in the director–builder loop.

Prompt​

Task: {one-sentence intent}. In scope: {files/modules}. Out of scope: {explicitly}. Acceptance criteria: {the ACs, verbatim}. Constraints: build to the coding standards and secure-by-default posture; no new dependencies without asking; a human merges. Done means: the Definition of Done — ACs met with honest tests, docs updated in this PR, gate green, context/memory updated if you learned something. Prepare but DO NOT perform any irreversible action; stop and ask. Work in small commits. If you fail the same correction three times, stop and explain what's wrong with the task.

Usage notes​

  • The three-strikes line implements the build-loop escalation rule.

Failure modes​

  • Scope creep (mitigated: explicit out-of-scope).
  • Silent irreversible actions (mitigated: prepare-then-ask instruction).