Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From slice-roadmap
Bootstrap a repo's roadmap graph (docs/roadmap/roadmap.yaml) when none exists — a PM-style interview that warm-starts from any existing roadmap docs, then writes the YAML and renders SLICES.md. Use to onboard a new repo to slice-roadmap.
npx claudepluginhub connorbritain/roadmap --plugin slice-roadmapHow this skill is triggered — by the user, by Claude, or both
Slash command
/slice-roadmap:slice-init [--cold][--cold]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You bootstrap `docs/roadmap/roadmap.yaml` through an interview. This is interactive — stay in the main loop; ask, don't guess.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
You bootstrap docs/roadmap/roadmap.yaml through an interview. This is interactive — stay in the main loop; ask, don't guess.
/slice-sync instead. Stop unless the user wants to re-bootstrap.docs/sprints/**, a STATUS doc, git log. If found, invoke the roadmap-bootstrapper agent to draft a roadmap.yaml from them, then run a confirmation interview that mainly fills the gaps: est_sessions per open sprint, the deps edges (confirm each inferred one — data-dep vs sequencing), touches for shared-file sprints, and gated_on for human-gated steps.--cold or no material). Interview from scratch, one dimension at a time: vision/north-star → the PIs + themes → per-PI sprints + session sizing (anchor to "a focused Claude session", not hours) → dependencies → shared-file contention (touches) → human gates + who → the default verification gate + per-sprint overrides → concurrency appetite + terminal + worktree root → cadence. Also offer to set meta.links (narrative/status/tracker docs) so SLICES.md cross-links them.docs/roadmap/roadmap.yaml (schema: see the plugin's schema/roadmap.schema.json), then roadmap validate and roadmap render. Print the initial roadmap plan as a sanity check. Launch nothing.est_sessions, statuses, and deps are the author's calls — propose, confirm, don't invent. Keep invoke keys short, stable, and unique.