consume: plan report should justify each note's inclusion, not only trace provenance #13

Closed
opened 2026-07-24 21:38:06 -04:00 by alexion · 0 comments
Owner

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

## 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
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alexion/skills#13