Skip to content
T1KTheOneKit

agent-completion-discipline

Agent Completion Discipline — Commit Before Summary

Section titled “Agent Completion Discipline — Commit Before Summary”

Rule

Section titled “Rule”

COMMIT BEFORE YOU SUMMARIZE. Any agent that has made edits or completed implementation work MUST commit + push BEFORE composing any summary, wrap-up, or report. Order: dispatch pending Writes → commit via pathspec (git commit -m "…" -- <explicit paths> — never a separate git add + git commit, which a concurrent teammate’s add can sweep into) → push → open the PR → report the URL. A pushed branch is not delivered work. If there is no PR, say there is no PR.

A background sub-agent’s final text does NOT reach its spawner — only SendMessage does (worktree-isolated async agents excepted; the task returns their result). “Return findings as your final message” yields nothing — the highest-frequency fan-out failure. Send before going idle: a report left in your own transcript is undelivered.

An explicit no-commit brief overrides this for that turn — forward it to any sub-agent you spawn. Never commit to the default branch regardless.

Budget checkpoint, deliverable-class obligations, delivery-channel naming, the no-commit override, and orchestrator-side handling of [t1k:agent-stopped-dirty] / [t1k:agent-stopped-empty]: skills/t1k-team/references/agent-completion-discipline.md.