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`.

Datos de origen

Repositorio
jeffrschneider/agentcatalog
Última actividad en el origen
22 de agosto de 2026 a las 14:12
Idioma detectado de SKILL.md
inglés
Estrellas
0
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
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`.
Ver en GitHub