Publishing PlanRun to npm

PlanRun ships three public packages under the @planrun scope:

Package	Role
@planrun/skill-provider	28 bundled skills + config/roles.json
@planrun/workflow	Cordis plugin (growth · run-start · run-stop · persona)
@planrun/bundle	DSH profile bundle (dsh.bundle.patch)

Directory packages/bundle-planrun/ maps to npm name @planrun/bundle.

User install (one line)

dsh plugin --profile web add @planrun/bundle

Restart the profile after bundle changes (dsh web).

Maintainer publish

Prerequisites

• Node ^22.19 or >=24
• npm login with access to @planrun scope
• Clean pnpm run build · pnpm run verify · pnpm run verify:publish

Publish order

Dependencies must publish in order:

1. @planrun/skill-provider
2. @planrun/workflow
3. @planrun/bundle

pnpm run build
pnpm run verify:publish          # structural pack checks (no upload)
pnpm run publish:packages        # upload to npm (requires npm login)

Dry-run pack only:

bash scripts/publish-packages.sh --pack-only

Workspace dev vs publish

• Local monorepo: bundle uses workspace:^ for skill-provider and workflow; pnpm links siblings.
• npm consumers: pnpm publish rewrites workspace:^ to semver ranges automatically.

Git install (alternative)

Not the primary path for v1.5. See Harness publish docs for prepare + allowBuilds if needed.

Project growth + guard

After the bundle is installed:

# from planrun checkout, or after cloning install-planrun.sh from release tag
./scripts/install-planrun.sh --here --copy-plan

This seeds .dsh/growth/ and copies guard scripts to scripts/ with npm scripts merged into package.json.

Related

• quickstart.md / zh/quickstart
• workflow-guard.md
• naming.md