qe 0.9.0: /qe:workplan-roadmap — a project tracker drawn as mermaid flowcharts

.claude-plugin/marketplace.json

@@ -9,8 +9,8 @@
     {
       "name": "qe",
       "source": "./qe",
-      "version": "0.8.0",
-      "description": "QuantEcon's shared agent skills under one namespace — working through a PR's review feedback, advising on and scoring lecture acceleration (benchmark), bulk read-only repository audits, turning audit reports into tracked work projects, and creating, reading and carrying work-plan state across agent sessions"
+      "version": "0.9.0",
+      "description": "QuantEcon's shared agent skills under one namespace — working through a PR's review feedback, advising on and scoring lecture acceleration (benchmark), bulk read-only repository audits, turning audit reports into tracked work projects, creating, reading and carrying work-plan state across agent sessions, and drawing a project's roadmap (phases, decision gates, pathways and work items) from its tracker"
     }
   ]
 }

CATALOG.md

@@ -8,7 +8,7 @@ Everything ships in the single `qe` plugin ([#43](https://github.com/QuantEcon/s
 
 | Family | Skills | State | Tracking |
 |---|---|---|---|
-| **Author-facing** — from drafting a lecture to merging its PR | `/qe:copilot-review`, `/qe:workplan` | `/qe:copilot-review` is operational, validated from an installed plugin on 2026-08-03: plugin-root path resolution, cross-repo mode, and running from outside a working tree. `/qe:workplan` (0.5.0, consolidating 0.4.0's `workplan-issue` and `workplan-update` and adding a `read` verb — the work-plan issue's whole lifecycle: create, read/validate/recommend, resume, update, close-and-succeed) is operational for the verbs that have run: `update` and `resume` on 2026-08-20 from an installed plugin, and this repo's own work-plan issue [#25](https://github.com/QuantEcon/skills/issues/25) revised again on 2026-08-25 as the consolidated skill's first `update`. `create`, `read` and `close` are merged procedures with no run yet, and its sibling `/qe:workplan-project` (0.3.0 as `/qe:workplan`, renamed 0.4.0; report bundle → tracking issue with sub-issues) has never been run against a real bundle, so neither is listed above. Note the name reuse: `/qe:workplan` meant the report-to-project skill for one morning in 0.3.0; from 0.5.0 it is the lifecycle skill. The style skills (`check-style` and six per-category siblings) shipped as scaffolding through 0.5.0 and were removed in 0.6.0; their plan lives in [#3](https://github.com/QuantEcon/skills/issues/3), and they return once the rule snapshot and deterministic preflight land. | [#3](https://github.com/QuantEcon/skills/issues/3) |
+| **Author-facing** — from drafting a lecture to merging its PR | `/qe:copilot-review`, `/qe:workplan`, `/qe:workplan-roadmap` | `/qe:copilot-review` is operational, validated from an installed plugin on 2026-08-03: plugin-root path resolution, cross-repo mode, and running from outside a working tree. `/qe:workplan` (0.5.0, consolidating 0.4.0's `workplan-issue` and `workplan-update` and adding a `read` verb — the work-plan issue's whole lifecycle: create, read/validate/recommend, resume, update, close-and-succeed) is operational for the verbs that have run: `update` and `resume` on 2026-08-20 from an installed plugin, and this repo's own work-plan issue [#25](https://github.com/QuantEcon/skills/issues/25) revised again on 2026-08-25 as the consolidated skill's first `update`. `create`, `read` and `close` are merged procedures with no run yet, and its sibling `/qe:workplan-project` (0.3.0 as `/qe:workplan`, renamed 0.4.0; report bundle → tracking issue with sub-issues) has never been run against a real bundle, so neither is listed above. Note the name reuse: `/qe:workplan` meant the report-to-project skill for one morning in 0.3.0; from 0.5.0 it is the lifecycle skill. `/qe:workplan-roadmap` (0.9.0) is the family's third skill — a project tracker drawn as mermaid flowcharts of phases, gates, pathways and work items, kept in step with the tracker after a plan review. Its procedure was extracted from one hand run (the Lectures monorepo roadmap, 2026-09-02) and it has not yet run as an installed skill; listed because the procedure is complete and the deterministic half, `scripts/workplan/tracker-snapshot.sh`, was tested against a private and a public tracker. The style skills (`check-style` and six per-category siblings) shipped as scaffolding through 0.5.0 and were removed in 0.6.0; their plan lives in [#3](https://github.com/QuantEcon/skills/issues/3), and they return once the rule snapshot and deterministic preflight land. | [#3](https://github.com/QuantEcon/skills/issues/3) |
 | **Benchmark** — evaluating accelerated lecture implementations | `/qe:benchmark` (until qe 0.7.0: `/benchmark:review-acceleration`) | Operational for workspace runs: rubric v2, a deterministic scoring engine, and two complete worked evaluations as regression baselines. | [#4](https://github.com/QuantEcon/skills/issues/4) |
 | **Audit** — bulk, read-only repository audits | `/qe:audit-issues` (until qe 0.7.0: `/audit:issues`) | Run twice **as a skill**, against deliberately different repo types. Run 1 — a 230-item tracker on 2026-07-28, 22 minutes, seven plugin defects ([record](https://github.com/QuantEcon/skills/blob/main/reviews/audit-run-action-translation-2026-07-28.md)); both severity-1 defects fixed in audit 0.2.0 ([#34](https://github.com/QuantEcon/skills/pull/34)). Run 2 — `QuantEcon/meta`, 317 items and 138 open, 2026-08-25, ~53 minutes including a deliberate kill ([record](https://github.com/QuantEcon/skills/blob/main/reviews/audit-run-meta-2026-08-25.md)) — **settled the claim the program exists to check**: the open pass resumed across a lost session at the issue predicted beforehand, appending only, with no re-walk, skip or duplicate; and read-only moved from asserted to measured, a before/after fingerprint of all 317 issues hashing identically. What two runs still do not cover: the closed pass writes once for the whole survey, so an interrupt there loses the phase and the resume rule cannot address grouped entries ([#57](https://github.com/QuantEcon/skills/issues/57)); no run has been killed mid-write, so the truncation guard is unexercised; and the working-directory rule's `.audit/` fallback leaves a public checkout untracked-dirty ([#61](https://github.com/QuantEcon/skills/issues/61)). Further runs and the claims table: [#16](https://github.com/QuantEcon/skills/issues/16). | [#12](https://github.com/QuantEcon/skills/issues/12), [#16](https://github.com/QuantEcon/skills/issues/16) |
 

README.md

@@ -17,6 +17,7 @@ One plugin, one namespace ([#43](https://github.com/QuantEcon/skills/issues/43))
 | `/qe:audit-issues` | Maintainers sweeping a repository | Whole-tracker audit, read-only: every issue's status verified against the code, tiered into the repo's plan, delivered as a report bundle |
 | `/qe:workplan-project` | Maintainers organising work | Turns an audit or review report into a tracking issue with linked sub-issues |
 | `/qe:workplan` | Anyone carrying work across sessions | The work-plan issue's whole lifecycle — create, read (validate and recommend, writing nothing), resume, update, close-and-succeed |
+| `/qe:workplan-roadmap` | Maintainers reviewing a project plan | Draws a project tracker as mermaid flowcharts — phases, decision gates, pathways, and every work item with its dependencies — and keeps the drawing in step with the tracker after a plan review |
 
 Style checks against the QuantEcon style guide (`/qe:check-style`) are planned in [skills#3](https://github.com/QuantEcon/skills/issues/3) and land once their rule snapshot and deterministic preflight exist. Until qe 0.7.0 the benchmark and audit skills were the separate `benchmark` and `audit` plugins — if you installed those, uninstall them (`claude plugin uninstall benchmark@quantecon audit@quantecon`) so the retired names don't linger in your menu.
 

docs/using-skills.md

@@ -39,12 +39,13 @@ Two ways, equivalent:
 
 ## The skills
 
-Everything that registers in your slash menu — one plugin, five skills. Since `qe` 0.6.0 every entry is a skill that actually runs — an unbuilt skill lives only as the plan in its family's tracking issue (the style-check family, for example, is [skills#3](https://github.com/QuantEcon/skills/issues/3)). [CATALOG.md](../CATALOG.md) is the stricter list: merged, operational, *and* stating how far each has been validated.
+Everything that registers in your slash menu — one plugin, six skills. Since `qe` 0.6.0 every entry is a skill that actually runs — an unbuilt skill lives only as the plan in its family's tracking issue (the style-check family, for example, is [skills#3](https://github.com/QuantEcon/skills/issues/3)). [CATALOG.md](../CATALOG.md) is the stricter list: merged, operational, *and* stating how far each has been validated.
 
 | Skill | What it does | Status |
 |---|---|---|
 | `/qe:copilot-review` | Work through GitHub Copilot's review of a PR: a verdict and recommended fix per comment, then a threaded reply to each one so they can be resolved from the GitHub UI | operational, validated from an installed plugin 2026-08-03 — [#26](https://github.com/QuantEcon/skills/pull/26) |
 | `/qe:workplan-project`, `/qe:workplan` | The work-plan family: `workplan-project` turns an audit/review report into a tracking issue with linked sub-issues; `workplan` carries the single work-plan issue that holds state between agent sessions through its lifecycle — `create`, `read` (validate against live state and recommend next steps; writes nothing), `resume`, `update`, `close`-and-succeed. All GitHub writes are drafted first and gated on your approval | `workplan` operational for `update` and `resume` (validated from an installed plugin 2026-08-20, and again 2026-08-25 on this repo's own plan issue); its `create`, `read` and `close` verbs, and `workplan-project`, are merged procedures with no run yet — [skills#3](https://github.com/QuantEcon/skills/issues/3) |
+| `/qe:workplan-roadmap` | Draw or update a project's `ROADMAP.md` from its tracker: mermaid flowcharts of the phases, decision gates and pathways, and of every sub-issue with its dependencies, plus a gates table and node index. Structure only — an item closing changes nothing; the file, commit and PR are drafted and gated on your approval | procedure extracted from a hand run (the Lectures monorepo roadmap, 2026-09-02); no run as an installed skill yet — [skills#63](https://github.com/QuantEcon/skills/issues/63) |
 | `/qe:benchmark` | Advise whether a lecture is worth converting at all (triage — the front door), or score a submitted NumPy→JAX/Numba conversion against the rubric (review) | operational for workspace runs — [guide](../qe/references/benchmark/README.md), [skills#4](https://github.com/QuantEcon/skills/issues/4) |
 | `/qe:audit-issues` | Sweep a whole tracker: verify each issue's status against the code rather than the thread, tier the open set into the repo's plan, deliver a report bundle. Read-only — it recommends, never applies | run twice as a skill (2026-07-28, 2026-08-25); run 2 validated resume-across-a-lost-session and measured the read-only boundary, and left the closed pass's checkpointing as the open defect — [tutorial](tutorial-run-an-audit.md), [guide](../qe/references/audit/README.md), [skills#16](https://github.com/QuantEcon/skills/issues/16) |
 

qe/.claude-plugin/plugin.json

@@ -1,6 +1,8 @@
 {
   "name": "qe",
-  "description": "QuantEcon's shared agent skills under one namespace — working through a PR's review feedback, advising on and scoring lecture acceleration (benchmark), bulk read-only repository audits, turning audit reports into tracked work projects, and creating, reading and carrying work-plan state across agent sessions",
-  "version": "0.8.0",
-  "author": { "name": "QuantEcon" }
+  "description": "QuantEcon's shared agent skills under one namespace — working through a PR's review feedback, advising on and scoring lecture acceleration (benchmark), bulk read-only repository audits, turning audit reports into tracked work projects, creating, reading and carrying work-plan state across agent sessions, and drawing a project's roadmap (phases, decision gates, pathways and work items) from its tracker",
+  "version": "0.9.0",
+  "author": {
+    "name": "QuantEcon"
+  }
 }

qe/CHANGELOG.md

@@ -6,6 +6,18 @@ Versions are [semver](https://semver.org) as a user of this plugin experiences i
 
 Repository: [QuantEcon/skills](https://github.com/QuantEcon/skills) ([every commit that touched this plugin](https://github.com/QuantEcon/skills/commits/main/qe)). How a release is made: [developing-skills § Versioning and releases](https://github.com/QuantEcon/skills/blob/main/docs/developing-skills.md#versioning-and-releases).
 
+## 0.9.0 — 2026-09-02
+
+The work-plan family gains a third skill, extracted from a hand run: the roadmap drawn for the Lectures monorepo project from its tracker ([project-monorepo#30](https://github.com/QuantEcon/project-monorepo/pull/30), members-only). Tracked in [#63](https://github.com/QuantEcon/skills/issues/63).
+
+**Added**
+
+- `/qe:workplan-roadmap` — draw or update a project's `ROADMAP.md`: two GitHub-rendered mermaid flowcharts (the route — phases, decision gates, the pathways each gate can choose — and every tracker sub-issue with its dependencies), a table of what each gate can decide, and a node index. It snapshots the tracker with the new `scripts/workplan/tracker-snapshot.sh` (direct sub-issues in plan order, with the `Decision` role read from the native issue type or the QEP-6 body marker), diffs the snapshot against the roadmap's node index, and reports the *structural* changes only — an item merely closing is not one, by the file's own update rule. The file, the commit and the pull request are written after approval; the tracker itself is never edited. The roadmap lives beside the plan in the tracker's repository, never on the projects dashboard, because [C2 §2.2](https://github.com/QuantEcon/status-projects/blob/main/docs/contracts/tracker.md) withholds a private tracker's children from the public site.
+
+**Changed**
+
+- `workplan` and `workplan-project` now describe the family as three skills and link the third.
+
 ## 0.8.0 — 2026-08-26
 
 The work-plan skills gain a second reader. Since 2026-08-24 the [projects dashboard](https://quantecon.github.io/status-projects/) parses every registered project tracker nightly and publishes a per-tracker compliance block, so a tracker these skills produce is now read by a machine as well as by the next session. The two ends are pointed at one contract — [`docs/contracts/tracker.md`](https://github.com/QuantEcon/status-projects/blob/main/docs/contracts/tracker.md) (C2), which states the rules once and which the skills link to rather than restate ([#49](https://github.com/QuantEcon/skills/issues/49) item 2).

qe/scripts/README.md

@@ -1,6 +1,6 @@
 # qe plugin — scripts
 
-Each skill family's deterministic machinery lives in its own subdirectory: [`benchmark/`](benchmark/README.md) (the scoring engine and calibration behind `/qe:benchmark`) and [`audit/`](audit/README.md) (the tracker-snapshot fetcher behind `/qe:audit-issues`). `fetch-copilot.sh` predates that layout and stays at the top level, where `/qe:copilot-review` already points.
+Each skill family's deterministic machinery lives in its own subdirectory: [`benchmark/`](benchmark/README.md) (the scoring engine and calibration behind `/qe:benchmark`), [`audit/`](audit/README.md) (the tracker-snapshot fetcher behind `/qe:audit-issues`), and `workplan/` (`tracker-snapshot.sh`, which dumps a project tracker's body and direct sub-issues in plan order for `/qe:workplan-roadmap`; read-only, `--help` for the argument forms). `fetch-copilot.sh` predates that layout and stays at the top level, where `/qe:copilot-review` already points.
 
 ## `fetch-copilot.sh`