Repository navigation
feat(planning): give acceptance criteria ids and trace them to plan phases and decompose slices #10039
Description
Refs: #6924
What to do
W5 of #6917. Give each Brief and plan acceptance criterion an id, and have /planning:plan map each id to the phases that satisfy it and /work-items:decompose map each id to the slices that carry it, so a criterion no phase or slice covers is reported.
Done when
- A test under
plugins/planning/exits 0 with a case where a plan leaves one criterion id unmapped and the check reports that id. -
git grep -non the plan and decompose skills shows the criterion-id trace step. -
bash plugins/skill-quality/scripts/check-skill.sh plugins/planning/skillsexits 0. -
bash plugins/skill-quality/scripts/check-skill.sh plugins/work-items/skillsexits 0. -
ci-statusis green on the PR, and the PR body carriesRefs: #6917.
Split by the owner's HITL session (2026-10-24, owner decisions C12 and Q93-Q95). Intake triage sets its fields.
Activity
github-actions commentedon Oct 25, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: give each Brief and plan acceptance criterion an id. Have /planning:plan map each id to the phases that satisfy it. Have /work-items:decompose map each id to the slices that carry it. A criterion no phase or slice covers gets reported. The done-when items are concrete and lane-checkable: a planning test, a grep, two check-skill runs, and CI. No likely duplicates found among the open issues. #10037 is a nearby planning check, but it covers file:line citations, not criterion ids.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Oct 25, 2026
The token broker refused the work-resolve-issue run that
agent-readystarted because the lanes kill switch was on, so it did no work. work-unblock removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.