plastic-roadmap

Solid

Use when the user wants to plan a delivery batch, order waves of intents, ship a batch of intents in one go, track a named collection of intents toward a goal, or asks for a "roadmap". Creates and maintains a roadmap file, a delivery-side collection of intents (the counterpart to a release), separate from INDEX.md status tracking.

AI & Automation 9 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
33
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Roadmap A roadmap is a named, ordered, delivery-side collection of intents: the delivery-side counterpart to a release (completion-side, `CHANGELOG.md`). It lives at `roadmaps/{slug}.md`, a sibling of `INDEX.md` wherever `INDEX.md` lives: the global tier's `~/.plastic/roadmaps/` (beside `~/.plastic/INDEX.md`), or a project's root, `~/.plastic/projects/{slug}/roadmaps/` (beside that project's `INDEX.md` and `project.yml`). It never sits inside `store/`, which holds intent directories, not project artifacts. A roadmap file has four parts: a title/meta header, `## Goal` (prose), `## Batches` (ordered; entries inside a batch are parallel-safe, batches run sequentially), and an append-only dated `## Log`. A roadmap written before owner ruling 145 may instead use the legacy `## Waves` heading; reading accepts both, but every new roadmap is scaffolded with `## Batches`, and an existing roadmap file's heading is never renamed to migrate it. Each batch entry mirrors that intent's status in `INDEX.md` (`queued`/`delivering`/`delivered`/`abandoned`/`blocked`). **`INDEX.md` is the single writer of intent status; on any conflict INDEX wins and the roadmap entry is corrected to match.** The skill operates on the roadmap file directly via Read/Edit. The one deterministic helper it uses is the savepoint ledger writer (`scripts/roadmap-savepoint`, `append`/`rebuild`); every verb's closing step calls `append` after its Read/Edit, and the roadmap `.md` file itself stays Read/Edit-only. #...

Details

Author
zalom
Repository
zalom/plastic
Created
2 months ago
Last Updated
1 weeks ago
Language
Ruby
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

plastic-roadmap-continuing

Use when the user wants to continue or resume a roadmap, pick up a mid-flight delivery batch, asks "where is the roadmap", or wants to resume the batch that was shipping, including an indirect ask that never names a roadmap directly (for example "where did that batch of intents land"). This is the roadmap route of plastic-continuing: it finds the tier's mid-flight roadmap, presents its state, then asks how to proceed exactly once.

9 Updated 1 weeks ago
zalom
AI & Automation Solid

roadmap

Tracks features across their lifecycle in a live, per-repo roadmap — every RD, plan, and task and the lifecycle stage each is in. Layout-aware: a single plans/00-roadmap.md in flat layout, or a two-tier per-feature + portfolio roadmap under codeops/ in nested layout. Use when the user says "roadmap", "make_roadmap", "update_roadmap", "review_roadmap", "show_roadmap", "archive_roadmap", or "compact_roadmap". Covers six actions: make_roadmap (create + seed rows from disk), update_roadmap (re-infer stages, sync to disk, cascade to the portfolio), review_roadmap (read-only health check for drift/broken links), show_roadmap (read-only status overview — progress, stages, and next steps), archive_roadmap (move a completed feature to the archive), and compact_roadmap (slim a bloated roadmap: strip the legacy Notes log and trim fat cells). Detects the action from the user's phrasing or arguments and branches. The roadmap is the cross-session source of truth at the RD/plan altitude, above any single execution plan.

4 Updated 2 days ago
blendsdk
AI & Automation Solid

roadmap-planning

Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.

3 Updated 6 days ago
rampstackco