Record the lesson of a unit
Gate: L10-lessons. Every unit with a passed build has a dated lesson.
- Add an entry to
LESSONS.md, newest first: a heading## YYYY-MM-DD, <unit>and lines that start with-(C19): what happened and what to do differently. Say it generically and concretely; no private names, no machine paths. - Check that every unit with a passed build has a lesson line:
python "${CLAUDE_PLUGIN_ROOT}/scripts/batuta.py" lessons check - Revisit the decisions whose review trigger fired; a change goes through a new ADR that supersedes the old one:
python "${CLAUDE_PLUGIN_ROOT}/scripts/batuta.py" adr lint - Record the gate after the
verifyskill passed (a dry run until you add--apply):python "${CLAUDE_PLUGIN_ROOT}/scripts/batuta.py" gate status FEATURE --set L10-lessons=passed
On a non-zero exit: exit 1 from lessons check names the unit without a lesson or a blank field: write the line. Exit 1 from
adr lint is a malformed ADR or a broken supersession link: fix it. Exit 2 is a warning (an overdue review): schedule the
review or write the new ADR.