From a7de6c82f1a605fc948f359316f7a471bd46af3a Mon Sep 17 00:00:00 2001 From: Rahul Krishna Date: Thu, 6 Aug 2026 09:18:22 -0400 Subject: [PATCH] Point the roadmap reference at the org template The skeleton was prose in a fenced block here: not copyable, not where the artifact lands, and its editorial phrasing shipped into every roadmap made from it. Template now lives in codellm-devkit/.github next to the issue forms (codellm-devkit/.github#33), on the same principle issue bodies already follow -- org repo owns the shape, skill owns when and why. Reference drops from 63 lines to 19: a link plus the four rules that are genuinely skill-side. --- .claude-plugin/plugin.json | 2 +- CHANGELOG.md | 10 +++ .../references/roadmap-template.md | 74 ++++--------------- 3 files changed, 26 insertions(+), 60 deletions(-) diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json index 13acd49..0d76c1d 100644 --- a/.claude-plugin/plugin.json +++ b/.claude-plugin/plugin.json @@ -2,7 +2,7 @@ "name": "cldk-devtools", "displayName": "CLDK DevTools", "description": "The CLDK developer's mode ladder: skills for designing, building, maintaining, and releasing CodeLLM-DevKit โ€” from a language's backend analyzer through the frontend SDKs, plus day-to-day upkeep across the codellm-devkit org.", - "version": "0.4.0", + "version": "0.4.1", "author": { "name": "Rahul Krishna", "email": "i.m.ralk@gmail.com" diff --git a/CHANGELOG.md b/CHANGELOG.md index a0e1025..74ddaaf 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,16 @@ All notable changes to the CLDK DevTools plugin are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). +## [0.4.1] โ€” 2026-08-06 + +### ๐Ÿ”ง Changed + +- The roadmap skeleton moves to `codellm-devkit/.github` โ†’ + `docs/design/roadmap-template.md`, beside the issue forms. It was prose in a fenced + block inside this skill's reference โ€” not copyable, not where the artifact lands, + and carrying editorial voice into every roadmap made from it. The reference now + links the template and keeps only the skill-side rules. + ## [0.4.0] โ€” 2026-08-04 ### โœจ Added diff --git a/skills/planning-cldk-work/references/roadmap-template.md b/skills/planning-cldk-work/references/roadmap-template.md index 054ebc3..d2a4e91 100644 --- a/skills/planning-cldk-work/references/roadmap-template.md +++ b/skills/planning-cldk-work/references/roadmap-template.md @@ -1,63 +1,19 @@ -# Roadmap template +# The roadmap artifact -The artifact `planning-cldk-work` produces. Lives at **`codellm-devkit/.github` โ†’ -`docs/design/roadmap.md`**, committed, next to the epics and cross-repo specs it coordinates. +**Template:** `codellm-devkit/.github` โ†’ [`docs/design/roadmap-template.md`](https://github.com/codellm-devkit/.github/blob/main/docs/design/roadmap-template.md). +Copy it; do not re-derive the sections here. Same rule as issue bodies โ€” the org repo +owns the shape, this skill owns when and why. -One roadmap per planning pass, amended in place rather than duplicated per quarter โ€” the git -history is the record of how thinking changed, which is exactly what an issue body cannot give you. +**Lands at:** `codellm-devkit/.github` โ†’ `docs/design/roadmap.md`, committed, beside the epics and +cross-repo specs it coordinates. -## Template +## Skill-side rules -```markdown -# CLDK roadmap - -**Pass:** ยท **Planned with:** -**Status:** current (supersede by editing, not by adding a second roadmap) - -## Candidates - -| # | Feature | Moves schema v2? | Collision group | Blocked by | -| - | ------- | ---------------- | --------------- | ---------- | -| 1 | | yes โ€” / no | A | โ€” | -| 2 | | yes โ€” | A | 1 | -| 3 | | no โ€” SDK surface only | โ€” | 1 | - -## Collision groups - -Candidates that touch the same schema vocabulary. **Each group is ONE design session for the -shared part**, even where the features ship far apart โ€” the parity clause makes a term coined -twice permanently wrong. - -- **Group A โ€” **: candidates 1, 2. - - Design session: . - -## Dependency order - - - - 1 (vocabulary) โ”€โ”€โ–ถ 2 (linking) โ”€โ”€โ–ถ 3 (surface) - -## Release trains - -| Train | Carries | Notes | -| ----- | ------- | ----- | -| | 1 | schema major โ€” SDK pins only once cut | -| | 3 | after the analyzer release lands | - -Candidates sharing a schema major ride **one** migration, not one each. - -## Not now - -**The list that makes the rest mean something.** What is excluded from this pass, and why. - -- โ€” - -## Starting now - - -Everything else on this roadmap has no issue yet, by design. -``` - -Amend in place. A dropped candidate moves to **Not now** with its reason rather than being deleted -โ€” that it was considered is often the most useful thing the roadmap records. +- **One roadmap, amended in place.** Never a second file per quarter โ€” git history is the record of + how thinking changed, which is what makes the doc worth more than an issue. +- **Rows are contract decisions, not themes.** A theme decomposes into several rows before the + collision sweep can compare anything. This is the gate, not a style preference. +- **`Starting now` holds exactly one candidate.** Everything else on the roadmap has no issue yet, + by design โ€” filing ahead is what turns a plan into inventory. +- **Dropped candidates move to `Not now` with a reason**, rather than being deleted. That a thing + was considered and rejected is often the most useful fact the roadmap carries.