Skip to main content

write-the-review-decisions-back

Writes the new owners and the new dates back against each item, and keeps every move of a date with the review that moved it, so a commitment that has slipped twice can be seen to have slipped twice. Use it when running `ref/prt/review-a-joint-plan`.

Source facts

Repository
jeffrschneider/agentcatalog
Last source activity
August 22, 2026 at 14:12
Detected SKILL.md language
English
Stars
0
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
write-the-review-decisions-back
description
Writes the new owners and the new dates back against each item, and keeps every move of a date with the review that moved it, so a commitment that has slipped twice can be seen to have slipped twice. Use it when running `ref/prt/review-a-joint-plan`.
license
CC-BY-4.0
metadata
{"agent":"commitment-keeper","agent-version":"1"}
# Write the review decisions back ## What it does Writes the new owners and the new dates back against each item, and keeps every move of a date with the review that moved it, so a commitment that has slipped twice can be seen to have slipped twice. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Record the Decisions and the Dates** - `ref/prt/review-a-joint-plan`, activity 15 - [Review a Joint Plan](../../../../processes/partners/review-a-joint-plan.md) ## What to record Each commitment as an item carrying one owner, one date and a state, traceable to the line of the signed plan it came from. At every review, the roll-call of all of them with the late ones counted. Each closed commitment with the reason it was given up on and the date. The decisions from the review with the new owners and the new dates, and every move of a date with the review that moved it, so a commitment that has slipped twice can be seen to have slipped twice. The review dates set for the year, and whose calendars they landed on. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
View on GitHub