pi-workflows

Add planning, specification, debugging, code review, and QA commands to PI Agent, with bundled development skills.

@prjct.app/pi-workflows · Workflow commands plus three bundled skills: tdd, code-review, diagnosing-bugs.

Install

Requires Pi installed separately and Node.js 22.19 or later. Compatibility is tested with Pi 0.85.1; newer versions are not yet verified. This is an independent community package.

Install with Pi's package manager:

pi install npm:@prjct.app/pi-workflows

For project-only installation, add -l: pi install -l npm:@prjct.app/pi-workflows. Restart Pi after installation. Do not install the same extension from both GitHub and npm: Pi treats those as different package identities.

For /work, install the companion separately as well:

pi install npm:@prjct.app/pi-plan

Usage

Command	Purpose
/work <task>	Activate Pi Plan, investigate, and seek approval before implementation
/spec <task>	Draft a specification before saving it
/debug <problem>	Diagnose a problem before applying changes
/review [context]	Review changes
/qa [context]	Examine test evidence
/ship [context]	Assess readiness; does not publish or deploy
/quality [mode] [context]	Select review, qa, or ship; defaults to qa
/skill-workflow <name> [arguments]	Run an installed skill as a workflow

Example:

/work Add pagination to the customer list

/work needs Pi Plan installed and enabled. The other commands do not require it. Instructions apply to the active run and are removed from later model requests after agent_settled; commands entered while Pi is busy are queued as follow-ups.

The bundled skills are package resources, not separate npm dependencies. They are declared through pi.skills and are enabled by default. The extension guides the model; normal Pi permissions and project instructions still apply.

Manage the package

For an npm installation:

pi list
pi update npm:@prjct.app/pi-workflows
pi remove npm:@prjct.app/pi-workflows

Use pi config to enable or disable individual resources. Use pi config -l for project settings and add -l to removal when you installed locally.

To pin version 0.1.3, use pi install npm:@prjct.app/pi-workflows@0.1.3. Pi skips pinned npm versions during package updates. For a Git installation, update or remove using the same git:github.com/prjct-app/pi-workflows source instead of the npm source.

When switching from GitHub to npm, remove the Git installation first, then install the npm package and restart Pi.

Troubleshooting

If /work cannot activate planning, install and enable Pi Plan. For an unknown skill, check pi config and use the skill name shown by Pi. /ship is an assessment command, not a deployment command.

Package and API documentation

Uses public commands, message APIs, lifecycle events, context transforms, and pi.events. Skills are included in the tarball and declared as ./skills; Pi Plan communicates through the public event bus rather than a module import.

See Package structure and compatibility for the manifest, dependency policy, shipped resources, and official references. This package follows the official Pi package guide and extension API guide for the tested version.

Development

From a repository checkout:

npm ci --ignore-scripts
npm run check
npm test
npm run check:package

Pi loads the TypeScript entry point directly; no build step is required. To try this checkout for one run, use pi -e .. Tests use isolated temporary state and do not call model APIs. See CONTRIBUTING.md for contribution rules and CHANGELOG.md for release notes.

License

MIT.

Third-party code or assets are credited in THIRD_PARTY_NOTICES.md; the accompanying licenses are included.