@resolutedev/pi-flow
Multi-stage development workflow orchestrator for pi
Package details
Install @resolutedev/pi-flow from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@resolutedev/pi-flow- Package
@resolutedev/pi-flow- Version
1.3.0- Published
- Jun 11, 2026
- Downloads
- not available
- Author
- maikeffi
- License
- MIT
- Types
- extension
- Size
- 21.7 KB
- Dependencies
- 0 dependencies · 1 peer
Pi manifest JSON
{
"extensions": [
"./extensions"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
pi-flow
Multi-stage development workflow orchestrator for pi.
Workflows
| Command | Stages |
|---|---|
/pi-flow:new-feature <topic> |
grill-with-docs → to-prd → to-issues → tdd |
/pi-flow:improve-arch <repo> |
improve-codebase-architecture → choose → to-prd → to-issues → tdd |
/pi-flow:debug <issue> |
diagnose → to-prd → to-issues → tdd |
Features
- Automatic model switching: design model (qwen3.7-max) for planning stages, code model (kimi2.6) for implementation
- Stage completion detection: dual-signal strategy with anti-signal override
- Gate behavior: pause after grill and issues for review, auto-advance through prd and tdd
- State persistence: survives
/newand session restarts - Session recovery: restores pipeline state on startup, re-notifies if paused at gate
Setup
pi install npm:@resolutedev/pi-flow
Configure models:
/pi-flow:setup
Or edit settings.json:
{
"extensions": {
"pi-flow": {
"models": {
"design": "opencode-go/qwen3.7-max",
"code": "opencode-go/kimi2.6"
}
}
}
}
For Maintainers: Publishing Releases
The GitHub Actions workflow automatically publishes to npm when a version tag is pushed. To enable this:
Generate an npm access token with publish permissions:
npm login npm token create --read-only=falseAdd the token to GitHub Secrets:
- Go to your repository Settings → Secrets and variables → Actions
- Click "New repository secret"
- Name:
NPM_TOKEN - Value: the token from step 1
Create a release:
npm version patch # or minor/major git push origin main --tags
The workflow will:
- Run tests
- Extract version from the tag (e.g.,
v1.2.3) - Patch
package.jsonwith the version - Publish to npm with
--access public - Create a GitHub Release with auto-generated notes
Commands
| Command | Description |
|---|---|
/pi-flow:new-feature <topic> |
Start new feature workflow |
/pi-flow:improve-arch <repo> |
Start architecture improvement |
/pi-flow:debug <issue> |
Start debug workflow |
/pi-flow:next |
Advance past a gate |
/pi-flow:skip |
Force-advance current stage |
/pi-flow:retry |
Re-send current stage prompt |
/pi-flow:cancel |
Cancel active pipeline |
/pi-flow:status |
Show pipeline status |
/pi-flow:setup |
Configure model mappings |