/roadmap-reconcile
Check the roadmap and canvas tables against recent chronicles, merged PRs, and freshly-filed tickets. See drift with --dry-run. Apply edits with --apply. Runs before /longrun prep and /sprint.
/roadmap-reconcileType it bare, or paste it with loose context after — Claude figures out the rest.
Canvas roadmap tables get stale. Shipped work sits marked pending. Sequencing drifts from reality.
Diffs the roadmap against merged PRs plus fresh session logs. Applies edits so the canvas matches reality.
Takes in
- Optional --dry-run or --apply flag
- Roadmap path or canvas ref
Returns
- Diff report of drift
- Applied edits when --apply
- Status per row
What it does
This skill uses only mechanical inputs — git log, gh pr list, gh issue list, grep across canvas + goal doc files. No paid API. No LLM dispatch. Same procedure runs identically at lite, standard, and ultra. Lite adopters get the full drift check.
The lib/tier-check.sh gate reads adopter tier from .claude/bassclef-configs.jsonc. This skill's body has no tier branch — one procedure serves every reader. Future extension (LLM-based semantic drift) would add a tier branch at the point of divergence; today no branch is needed.
Read the full skill
The complete instructions live at .claude/skills/roadmap-reconcile/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.
Where in the SDLC
Also relevant in: Concept, Design, Ship.
Why this phase: Check the roadmap and canvas tables against what actually shipped. Drift shows up as rows marked pending after their work merged. Runs before /longrun prep and /sprint.
Related
- Skills catalog — browse all skills grouped by lifecycle phase
- Tier system — what each tier gives you
FAQ
Terms from bassclef vocabulary that appear on this page.
- primitive
- A building block of bassclef — a skill, a rule, a hook, a luminary, or an agent. Adopters compose primitives into workflows. The lite tier ships one primitive of each kind (except luminaries — lite ships 4, standard adds more, ultra loads the full 96). See: /docs/config/tier-system
- load-bearing
- A part of the system that other parts depend on — remove it and downstream things break. Bassclef uses the word for artifacts that other artifacts read: a canvas is load-bearing when a spec cites it, a spec is load-bearing when Builder uses it. Plain equivalent: 'actually used' or 'counted on'.
- chronicle
- A narrative log of what a session shipped — what worked, what did not, what got deferred. Written at session-end. Bassclef's chronicles live under `docs/chronicles/YYYY-MM-DD-slug.md`. Chronicles are how future sessions understand context that the code alone cannot show. See: /docs/skills/session-log
- whereami
- The authoritative project-state snapshot — current phase, active goals, subsystem status, gate progress, session recap history. Read at session-start; updated at session-end. The one file every new session should read first to know where the project stands. See: /docs/skills/whereami
- hook
- A shell script bassclef wires into Claude Code's tool-invocation lifecycle. Hooks fire at events like PreToolUse (before an Edit lands) or SessionStart (when a session opens). Hooks enforce rules mechanically — a rule says 'don't do X'; a hook fires and BLOCKs if X happens.
- rule
- A markdown file auto-loaded into every session's context. Rules pin discipline the agent applies to every response (plain-English writing, blocked-items protocol, temperance gates). Different from a hook — rules are steering; hooks are enforcement.
- skill
- A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.
- adopter
- A repo that has bassclef installed — either via `bassclef init` (lite tier from npm) or via the symlink pattern (standard tier with an Anthropic key). Bassclef's discipline: never break adopters. Every change to a downstream-observable surface ships with a compat shim.
- bassclef-upstream
- The private repo where bassclef substrate is authored. Ships to a public `bassclef` npm package + a public `bassclef-web` docs site. Adopters read the public tier; the operator maintains upstream.
Shipped by @kingofrock · Read the essays
/longrun
Run a long autonomous session that paces itself. Prepares scope. Checkpoints at phase boundaries. Closes with session log and retrospective. Three modes: prep, checkpoint, closeout.
/sprint
Show what's in flight and what's next. Reads project state, open issues, and the active goal. Proposes the next sprint at thread level, not just the nearest leaf. Run at session start.