Agent Ledger And Delivery

Overview

Define how agent work is recorded so reviewers can see prompt, intent, changes, validation, risks, and linked tasks or commits.

This skill focuses on delivery evidence and long-term traceability, not commit splitting or task-state ownership. A ledger may reference tasks and commits, but tasks.md, an issue tracker, or another work-state surface remains responsible for current task status and acceptance criteria. For shared harness terms, see ../../references/harness-patterns.md; when ledger files are absent, use references/build-when-missing.md. For ledger coupling and skip policy, see references/delivery-coupling.md.

When To Use

• The user asks to create, refactor, or evaluate agent_chats, agents_chat, review descriptions, delivery records, linked tasks, or linked commits.
• A project requires AI collaboration records for each delivery.
• Validation, risk, next steps, and artifact references need a stable format.

Inputs Needed

• Existing ledger directory and naming rules.
• User goal, change summary, validation commands, artifacts, task IDs, reviews, or commits.
• Whether the repository requires ledger updates in the same commit.