consume: plan report should justify each note's inclusion, not only trace provenance #13
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
The plan report the skill requires (step 5) is provenance-oriented: a contribution map of which file fed which note. In practice the map was the least useful part for deciding what to keep.
Problem
The report lets you audit coverage but not judge the bar. What actually made the plan reviewable was a per-note trigger line — one sentence answering "why would anyone retrieve this" — added only after the acceptance test was clarified.
Proposed change
Require, per note, the acceptance rationale (its trigger) alongside the contribution map, so the report can be reviewed against the real selection bar rather than only checked for provenance coverage.
Files
consume/SKILL.md, step 5. Builds on the trigger-ability acceptance test (#9).— Claude