What was measured
The vendored Method Bundle and the skills installed in this repository disagree about the shape of a grilling, found 2026-09-02 while grilling #441:
apps/claude-code/unic-archon-dlc/vendor/mattpocock-skills/skills/productivity/grilling/SKILL.md, line 8: "Ask the questions one at a time, waiting for feedback on each".
.agents/skills/grilling/SKILL.md (upstream mattpocock/skills as pinned in skills-lock.json), line 8: "Work the tree in rounds. The frontier is every decision whose prerequisites are already settled".
/specs in discuss mode composes the vendored file by path, so every Consumer running it gets the retired one-at-a-time interview. Any criterion that names the interview's shape rots on the next Bundle upgrade.
Why it is its own issue
Root AGENTS.md § The quality bar for a prose Box: upgrading a vendored Method Bundle means diffing the vendored tree against the new upstream tag by hand, in the same commit that moves the pin. Nothing in this repository watches upstream, so the gap is found only when a session reads both files, which is what happened here. #441 must not carry the upgrade: rewriting /specs and moving the Bundle in one change would make neither attributable, and #441 is held until run 3 reports anyway.
Done when
- The vendored Bundle under
apps/claude-code/unic-archon-dlc/vendor/mattpocock-skills/ matches one named upstream tag, and the commit that moves it carries the by-hand diff summary the root AGENTS.md asks for.
grilling/SKILL.md in the Bundle reads the rounds shape, and every other Method the Bundle ships is checked against the same tag, not only the one that surfaced.
- The plugin version is bumped as the pin, per
AGENTS.md, and README.md § Dependencies still agrees with what the Boxes and commands read.
Not this ticket
Whether /specs should grill differently is #441.
What was measured
The vendored Method Bundle and the skills installed in this repository disagree about the shape of a grilling, found 2026-09-02 while grilling #441:
apps/claude-code/unic-archon-dlc/vendor/mattpocock-skills/skills/productivity/grilling/SKILL.md, line 8: "Ask the questions one at a time, waiting for feedback on each"..agents/skills/grilling/SKILL.md(upstreammattpocock/skillsas pinned inskills-lock.json), line 8: "Work the tree in rounds. The frontier is every decision whose prerequisites are already settled"./specsindiscussmode composes the vendored file by path, so every Consumer running it gets the retired one-at-a-time interview. Any criterion that names the interview's shape rots on the next Bundle upgrade.Why it is its own issue
Root
AGENTS.md§ The quality bar for a prose Box: upgrading a vendored Method Bundle means diffing the vendored tree against the new upstream tag by hand, in the same commit that moves the pin. Nothing in this repository watches upstream, so the gap is found only when a session reads both files, which is what happened here. #441 must not carry the upgrade: rewriting/specsand moving the Bundle in one change would make neither attributable, and #441 is held until run 3 reports anyway.Done when
apps/claude-code/unic-archon-dlc/vendor/mattpocock-skills/matches one named upstream tag, and the commit that moves it carries the by-hand diff summary the rootAGENTS.mdasks for.grilling/SKILL.mdin the Bundle reads the rounds shape, and every other Method the Bundle ships is checked against the same tag, not only the one that surfaced.AGENTS.md, andREADME.md § Dependenciesstill agrees with what the Boxes and commands read.Not this ticket
Whether
/specsshould grill differently is #441.