Renamed and Removed Commands

Update saved prompts and automation before upgrading; the old names no longer resolve. CHANGELOG.md has the release-by-release detail.

From kramme-cc-workflow to trackbed

Release 1.0.0 renamed the plugin and its marketplace from kramme-cc-workflow to trackbed, and the repository moved to trackbed/skills. Every skill and agent kept its name but moved from the kramme: prefix to the plugin namespace: /kramme-cc-workflow:kramme:pr:code-review in Claude Code and $kramme:pr:code-review in Codex both become trackbed:pr:code-review. The decision record explains why.

Existing installs do not move on their own. Remove the old plugin and marketplace, then install trackbed as in Installation & Updating:

# Claude Code, inside a session
/plugin uninstall kramme-cc-workflow@kramme-cc-workflow
/plugin marketplace remove kramme-cc-workflow

# Codex, from your terminal
codex plugin remove kramme-cc-workflow@kramme-cc-workflow
codex plugin marketplace remove kramme-cc-workflow

Usage records from before the rename count toward the new names. Your settings carry over:

• TRACKBED_* environment variables replace the KRAMME_* ones. The old names still work while the new ones are unset.
• git config trackbed.baseBranch replaces kramme.baseBranch, which is still read when the new key is unset.
• Hook toggles, usage records, and update-check state now live in trackbed/ state and config folders. Files already in the kramme-cc-workflow/ folders keep being used until a trackbed/ file exists.
• Diagrams and walkthrough reports now go to ~/.trackbed/diagrams/, and saved Pull Request descriptions to .trackbed/ in the repository. Older files stay where they are, and /trackbed:workflow:cleanup-artifacts still cleans old diagrams.
• Checkout installs of the Codex plugin build their marketplace under <codex-home>/.trackbed-plugin-marketplaces/.
• The plugin source moved from kramme-cc-workflow/ to trackbed/ in the repository, so local paths into a checkout change, for example claude /plugin install /path/to/skills/trackbed.

Renamed

Old → new	What to change
/kramme:siw:spec-audit:auto-fix and /kramme:siw:apply-spec-audit-fixes → /trackbed:siw:spec-audit --apply <report>	Pass the report path after --apply; --auto, --dry-run, --threshold 60-100, and --allow-dirty still work. --apply without a path audits first, then fixes the new report. --dry-run needs an existing report (--apply <report> --dry-run); audit-first dry runs are rejected before auditing or writing files. For a read-only audit, use --inline without --apply.
/kramme:docs:out-of-scope → /trackbed:docs:track-rejected-enhancements	Nothing; arguments and behavior are unchanged.
/kramme:code:cleanup-ai → /trackbed:code:refactor-pass	The replacement does not preserve the old arguments or side effects. Remove --auto; omit arguments to use the canonical branch review scope, or pass file and directory scope tokens instead of a base branch. When cleanup candidates exist, it verifies and checkpoints scoped uncommitted input, then verifies and commits each simplification separately.
/kramme:pr:ux-review → /trackbed:pr:product-review	Arguments are unchanged. It also runs the product reviewer over every changed file by default (--categories product gives the former product-only review) and writes PRODUCT_REVIEW_OVERVIEW.md with PROD-NNN finding IDs. It no longer reads, cleans up, or guards UX_REVIEW_OVERVIEW.md, so delete leftover copies by hand.
/kramme:siw:discovery → /trackbed:discovery:interview --siw	Pass --siw (or a bare siw, or siw/ paths); plain topic text no longer starts an SIW run. --apply now works only on a direct user request and confirms the edits in-session.
/kramme:siw:remove → /trackbed:workflow:cleanup-artifacts --siw	Keeps the SIW-only scope, the transfer-to-Linear-first warning, and the temporary-only, all-SIW, or abort confirmation. It cannot be combined with --auto, skips directories instead of force-deleting them when trash is missing, and skips siw/issues/ or siw/qa-intake/ when they hold unexpected files.
/kramme:pr:verify-description → /trackbed:pr:generate-description --check	Keeps --base, --strict, the drift rubric, and the report shape; the report heading is now PR Description Check. --strict also reports two clarity Suggestions: an opening that doesn't say what changes, and an untestable behavior change or risk without a Test plan scenario. Remove --fix: after Important or Critical drift, --check asks once (y/N) before regenerating and updating the PR; add --no-update for a report with no prompt.
/kramme:siw:product-audit → /trackbed:siw:spec-audit --product	Keeps --auto and --inline and adds the readiness dimensions. Product findings keep PROD-NNN IDs but are written to AUDIT_SPEC_REPORT.md alongside SPEC-NNN findings, are never auto-fixed by --apply, and resolve through /trackbed:siw:resolve-audit. No skill reads or commit-guards PRODUCT_AUDIT.md anymore; SIW spec detection still ignores it, and /trackbed:workflow:cleanup-artifacts removes leftover copies.
/kramme:visual:diagram → /trackbed:visual:explain	Nothing; the topic argument, behavior, and ~/.kramme-cc-workflow/diagrams/ output directory are unchanged.
/kramme:visual:onboarding → /trackbed:visual:explain --onboarding	Nothing; the focus-area or audience argument, behavior, and onboarding-{project-name}.html output are unchanged.
/kramme:docs:solution-refresh → /trackbed:docs:solution-note --refresh	The note-path and --all targets and --apply now follow --refresh; deletion and consolidation still ask first.
/kramme:code:weakness-audit → /trackbed:code:refactor-opportunities --ranked	Add --ranked and drop --team. The full, path, and feature scopes, --output, --max-findings, --solo, and --base are kept, and it still writes CODEBASE_WEAKNESS_REPORT.md with WA-NNN IDs. Ranked mode is user-only, so a model or another skill never starts it; automation must ask the user to run it.
/kramme:text:humanize → /trackbed:text:clarify --humanize	Takes one file or one text block per run, and treats a single-line argument that merely contains a slash, such as Fixed in src/api/orders.ts, as text. The pattern catalog, opt-in voice pass, and confirm-before-write flow are kept. /trackbed:pr:github-review keeps its humanize pass, and /trackbed:pr:github-review-reply now humanizes drafted replies only with --humanize.
/kramme:pr:plan-split → /trackbed:code:breakdown-findings --split	Keeps --base <branch>, --auto, the seam strategies, and the SPLIT or KEEP AS ONE decision. It now writes the PR_PLAN_*.md set itself instead of printing a handoff. Split plans still carry the worktree Implementation Setup; implement them by hand, then reconcile with --reconcile.
/kramme:pr:update-split-plans → /trackbed:code:breakdown-findings --reconcile	Pass the same plan paths, --all, --worktree, --source, --base, and --auto options. Former no-scope calls must add --all to preserve the removed command's active-plan-only default; zero-scope reconcile intentionally retains trackbed:code:breakdown-findings's existing all-indexed behavior.
/kramme:workflow-artifacts:cleanup → /trackbed:workflow:cleanup-artifacts	Nothing; every argument, mode, and safety gate is unchanged.
/kramme:linear:select-next → /trackbed:linear:next	Pass --agent-ready instead of --agent-ready-only; other arguments and behavior are unchanged.
--auto → default on /trackbed:git:recreate-commits, /trackbed:pr:create, /trackbed:pr:fix-ci, /trackbed:pr:generate-description, and /trackbed:pr:rebase	Typed commands, and requests that name one of these skills, now run unattended. Add --manual wherever you relied on the prompts; a leftover --auto is ignored. /trackbed:pr:rebase now skips its safety gates unless you pass --manual or --force-push. See Unattended by Default.

Removed

Removed	Use instead
/kramme:siw:issue-define	Before transfer, update the spec and run /trackbed:siw:generate-phases, choosing Append when issues exist. For a standalone issue or after transfer, use /trackbed:linear:issue-define. Existing local issue files stay valid; edit them directly and keep siw/OPEN_ISSUES_OVERVIEW.md and siw/LOG.md in sync.
/kramme:ci:design-pipeline	Ask directly for CI/CD pipeline design or gate planning. /trackbed:pr:fix-ci still handles failures in an existing Pull Request pipeline.
/kramme:product:pulse	Ask directly for a time-windowed product health recap. /trackbed:product:strategy and /trackbed:product:review still read existing reports under docs/pulse-reports/, and /trackbed:siw:spec-audit --product reads compound's reports from its configured docs_root, but nothing here generates them anymore.
/kramme:code:incremental	Use ordinary implementation requests for small verified slices and /trackbed:code:refactor-pass for narrow behavior-preserving cleanup. For structural refactors, survey candidates with /trackbed:code:refactor-opportunities, then ask for planning and implementation directly. No replacement keeps the interview-driven Decision Document and tiny-commit workflow.
/kramme:code:source-driven	Use /trackbed:code:migrate for version migrations, /trackbed:research for cited research artifacts, and the host's source tools to verify unstable third-party facts during implementation.
/kramme:test:generate	Ask directly for tests that follow the project's existing conventions, and use /trackbed:test:audit to assess an existing suite.
/kramme:git:worktree and /kramme:git:clean-gone-branches	Use Conductor workspace management, or run git worktree and git branch directly. Their helper scripts are gone too, and no replacement keeps their Conductor-path guards or confirmation-gated branch deletion.
/kramme:visual:plan-review and /kramme:visual:project-recap	Use /trackbed:pr:walkthrough --report to explain a branch or Pull Request, /trackbed:visual:explain to visualize a plan or architecture, and /trackbed:visual:explain --onboarding for a codebase overview.
/kramme:visual:generate-image	Use the image tools in your host. The Gemini image-generation script and its API-key setup are no longer bundled.
/kramme:visual:demo-reel	/trackbed:pr:generate-description no longer accepts --visual, and /trackbed:pr:create no longer captures or attaches screenshots or video; both leave a Screenshots/Videos placeholder on changes with visible UI. Ask directly for a screenshot or recording, or use /trackbed:browse or /trackbed:qa. No replacement keeps tiered capture, the secret preflight, or bounded environment startup. Earlier captures under .context/demo-reels/ remain eligible for /trackbed:workflow:cleanup-artifacts.
/kramme:session:context-setup	/trackbed:code:work-from-plan, /trackbed:code:plan-to-pr, and /trackbed:linear:issue-implement keep a shared preparation checklist with focused context loading, and a shared forward-progress reference covers context recovery. Ask directly for rules-file updates; the setup ritual, markers, and mandatory repair gate are retired.
/kramme:nx:setup-portless and the nx skill domain	Ask directly for portless setup or Nx dev:local/dev:full target wiring. No replacement keeps its target templates or certificate-trust steps.