Skip to main content
VOIDFORGE
← Tutorial Hub

MIGRATE

From legacy packages to voidforge-build

Old Tom remembers the old names. thevoidforge, @voidforge/cli, @voidforge/methodology — all retired. The forge answers to one name now: voidforge-build. The commands you love? Every one of them still works.

Bombadil avatarBombadil

WHAT CHANGED

VoidForge moved to a domain-matched package name. The CLI and methodology packages were renamed so npm install voidforge-build matches the site you're reading now: voidforge.build.

Legacy package names to new voidforge-build package names — 5 mappings
Legacy packageNew package
thevoidforgevoidforge-build
@voidforge/clivoidforge-build
thevoidforge-methodologyvoidforge-build-methodology
@voidforge/methodologyvoidforge-build-methodology
voidforge(bare, unscoped — squatter; only if previously installed via that name)voidforge-build

See ADR-061 for the rationale.

GLOBAL CLI USERS

If you installed the CLI globally under any of the old names, uninstall them and install voidforge-build:

$ npm uninstall -g thevoidforge @voidforge/cli voidforge 2>/dev/null
$ npm install -g voidforge-build@latest

The 2>/dev/null is intentional — it silences errors for any of the three names that aren't installed on your system.

PROJECT DEPENDENCIES

If your project's package.json lists the old methodology package, rename it:

# In package.json, rename:
"thevoidforge-methodology" → "voidforge-build-methodology"
"@voidforge/methodology" → "voidforge-build-methodology"
$ npm install

The new package ships the same .claude/ tree, the same CLAUDE.md, the same agents and commands. Nothing about your build protocol changes.

COMMANDS ARE UNCHANGED

The bin name is still voidforge. Every slash command you already know works exactly the same:

/prd/build/campaign/assemble/gauntlet/review/qa/security/ux/deploy/devops/git

The only thing that moves is the npm package name. The methodology, the agents, and the build protocol are the same canon — just served from a package whose name matches this domain.

VERIFY THE MIGRATION

Confirm the new CLI is on your PATH:

$ voidforge --version→ 23.x.x
$ npm ls -g voidforge-build→ shows installed version

Want cryptographic proof the package you installed came from the real VoidForge build workflow? Head to the provenance verification guide.