Context
Sibling to #13403 (the one-time ROADMAP.md trim). @tobiu flagged the roadmap-bloat (2026-06-16). Diagnosis this session (read origin/dev:.agents/skills/update-roadmap/references/update-roadmap-workflow.md): the update-roadmap skill (#13380) is strong on next-scope SHAPE (cornerstones + rationale + deferred set + stewards, NOT exhaustive lists) but missing the rule that keeps the roadmap next-only — so applying it lets the roadmap re-accumulate history (the #13403 bloat).
The Problem
The skill's "What a roadmap SHOULD / MUST NOT contain" list governs the next-scope's shape but never forbids accumulated prior-release history or a framework-vision restatement. Its "Celebrate first" beat correctly says an A2A / release-note acknowledgement suffices — but it doesn't forbid a permanent roadmap celebration section either. Net: each run ADDS the next scope without REPLACING the prior layers → the roadmap accretes a ## Shipped: vN + foundation sediment every release. The skill nails shape but is silent on the temporal / replace axis.
The Architectural Reality
.agents/skills/update-roadmap/references/update-roadmap-workflow.md (the World-Atlas directives; the always-loaded SKILL.md router stays a one-liner). Relocation homes the rule will point at: .github/VISION.md, resources/content/release-notes/. Steward of the skill (#13380): @neo-opus-ada.
The Fix
Extend the workflow with the temporal/replace axis:
- A "replace, don't append" rule: the roadmap holds the CURRENT next-release ONLY; each run REPLACES the prior next-scope, it does not stack
## Shipped: vN sections.
- Two MUST-NOTs added to the existing list: "no framework-vision restatement (→
.github/VISION.md; a 1-line pointer suffices)"; "no prior-release shipped-history (→ resources/content/release-notes/; a 1-line pointer suffices)."
- A Verify checkbox: "no prior-release history or vision-restatement remains inline (relocated, not duplicated)."
- Clarify step 1 (Celebrate): the celebration is the A2A / release-note beat — never a permanent
ROADMAP.md section.
Decision Record impact
aligned-with the skill's existing cornerstones-not-lists rule (extends it from the breadth axis to the temporal/replace axis). No ADR.
Slot-rationale (Substrate-Accretion-Defense)
Additions land in the conditionally-loaded references/ workflow (the World Atlas), not the always-loaded router → keep in the payload. Net-positive: ~6 lines that prevent a recurring per-release roadmap-bloat (higher standing cost than the addition).
Acceptance Criteria
Out of Scope
- The one-time ROADMAP.md trim = sibling #13403.
Related
Steward: @neo-opus-ada (the update-roadmap skill #13380). Sibling: #13403 (roadmap trim — B prevents A from re-bloating). Skill: #13380.
Release classification: substrate/process (NOT v13-release-blocking) → boardless.
Origin Session ID: c5cc7e13-6f5d-4090-908c-c8dfa496163a
Context
Sibling to #13403 (the one-time ROADMAP.md trim). @tobiu flagged the roadmap-bloat (2026-06-16). Diagnosis this session (read
origin/dev:.agents/skills/update-roadmap/references/update-roadmap-workflow.md): theupdate-roadmapskill (#13380) is strong on next-scope SHAPE (cornerstones + rationale + deferred set + stewards, NOT exhaustive lists) but missing the rule that keeps the roadmap next-only — so applying it lets the roadmap re-accumulate history (the #13403 bloat).The Problem
The skill's "What a roadmap SHOULD / MUST NOT contain" list governs the next-scope's shape but never forbids accumulated prior-release history or a framework-vision restatement. Its "Celebrate first" beat correctly says an A2A / release-note acknowledgement suffices — but it doesn't forbid a permanent roadmap celebration section either. Net: each run ADDS the next scope without REPLACING the prior layers → the roadmap accretes a
## Shipped: vN+ foundation sediment every release. The skill nails shape but is silent on the temporal / replace axis.The Architectural Reality
.agents/skills/update-roadmap/references/update-roadmap-workflow.md(the World-Atlas directives; the always-loadedSKILL.mdrouter stays a one-liner). Relocation homes the rule will point at:.github/VISION.md,resources/content/release-notes/. Steward of the skill (#13380): @neo-opus-ada.The Fix
Extend the workflow with the temporal/replace axis:
## Shipped: vNsections..github/VISION.md; a 1-line pointer suffices)"; "no prior-release shipped-history (→resources/content/release-notes/; a 1-line pointer suffices)."ROADMAP.mdsection.Decision Record impact
aligned-withthe skill's existing cornerstones-not-lists rule (extends it from the breadth axis to the temporal/replace axis). No ADR.Slot-rationale (Substrate-Accretion-Defense)
Additions land in the conditionally-loaded
references/workflow (the World Atlas), not the always-loaded router →keepin the payload. Net-positive: ~6 lines that prevent a recurring per-release roadmap-bloat (higher standing cost than the addition).Acceptance Criteria
update-roadmap-workflow.mdcarries the replace-don't-append rule + the 2 MUST-NOTs + the Verify checkbox + the clarified Celebrate beat.skill-manifest-lintgreen (sync the manifest + downstream docs if the frontmatterdescriptionchanges).Out of Scope
Related
Steward: @neo-opus-ada (the
update-roadmapskill #13380). Sibling: #13403 (roadmap trim — B prevents A from re-bloating). Skill: #13380.Release classification: substrate/process (NOT v13-release-blocking) → boardless.
Origin Session ID: c5cc7e13-6f5d-4090-908c-c8dfa496163a