PI PACKAGE EXTENSION

Dev Workflow

Daily developer workflow for pi: plan review, self-review, standards pass, CI checks, PR review comments, release PR prep, docs, and shipping. 15 core prompts plus run, prompts, and flow.

Overview

Daily developer workflow for pi: plan review, self-review, standards pass, CI checks, PR review comments, release PR prep, docs, and shipping. 15 core prompts plus run, prompts, and flow.

Package docs also remain available on the package summary page at /docs/dev-workflow, but this page focuses on the Pi-native extension surface: commands, tools, environment variables, packaged skills, and extension files.

Packaged Skills

This package ships Pi-local skills alongside the extension code:

Commands

CommandDoes
/workflow:plan Fresh-eyes review of the plan before implementing
/workflow:self Implementor rereads own code with fresh eyes
/workflow:standards Coding standards pass (lint, types, ORM, imports, Ruff)
/workflow:ci CI check — /ci, /ci-detail, logs, ours-vs-flake analysis
/workflow:docs Documentation pass — explain the why
/workflow:ship Smart ship — verify CI, atomic commit, PR description, open/update PR
/workflow:pr-review-comments Address PR review comments, validate, push, resolve threads, re-request review
/workflow:release-prs Prepare backend/frontend/optimo-frontend/design-system release PRs
/workflow:context Load context from existing PRs (local or remote), deep-read diff
/workflow:handoff Generate handoff message for new engineer or fresh subagent
/workflow:onboard Generate onboarding message for engineers
/workflow:scout Codebase recon — files, data flow, risks
/workflow:oracle Second opinion — challenge assumptions, no editing
/workflow:reviewer Independent review with forked context
/workflow:parallel Parallel reviews (correctness, tests, complexity)
/workflow:help or Ctrl+Shift+/ Interactive TUI prompt browser — browse, run, queue, edit
/workflow:flow Text overview of the full workflow
/workflow:run Run a core, project, or user prompt by stable code
/workflow:prompts or /workflow:prompts studio Open native TUI Prompt Studio for adding user prompts or overriding core prompts
/workflow:prompts add Open a field-based form to add/update a user.* prompt
/workflow:prompts override [workflow.code] Pick or directly override a core workflow.* prompt with a field-based form
/workflow:prompts delete [code] Delete a user prompt, remove a user override, or hide a project prompt after confirmation
/workflow:prompts restore [code] Restore a prompt hidden by a user-level disabled override
/workflow:prompts list List loaded prompts with source labels and hidden prompts
/workflow:prompts paths Show project/user/legacy config paths
/workflow:prompts validate Validate prompt config and show warnings
/workflow:prompts init Create a starter user config
/workflow:prompts reload Reload prompt config for dynamic help/run usage

Environment

  • PI_WORKFLOW_CMUX_MODE (default: auto) - auto = subagent-style workflow commands prefer a seeded cmux split when available; inline = always stay in the current session
  • PI_WORKFLOW_CMUX_SPLIT_DIRECTION (default: right) - Split direction for subagent-style workflow commands: right or down

Extension Files

Primary extension path: pi-packages/dev-workflow/extensions/dev-workflow

  • help-panel.ts
  • index.ts

Installation

bash
# From the agent-skills-marketplace repo root
pi install "$PWD/pi-packages/dev-workflow"

# From the Diversio monolith root
pi install "$PWD/agent-skills-marketplace/pi-packages/dev-workflow"

Local test or verification snippet:

bash
# From the agent-skills-marketplace repo root
cd pi-packages/dev-workflow && npm install && cd ../..

Configuration

Optional environment variables:

Help panel

/workflow:help opens a tabbed TUI panel:

Rows show source labels such as [core], [project], [user], [override:project], and [override:user].

Prompt Studio uses native Pi TUI forms: short metadata fields are single-line inputs, while the prompt body opens a multi-line editor so prompts can be formatted with readable sections and newlines. The form validates before saving, including required fields, user.* code format, and duplicate code collisions. Renaming a user prompt removes the old code entry instead of leaving a duplicate. Deletion is confirmed before writing: user prompts are removed from user config, user overrides are removed, and project prompts are hidden through a user-level disabled override rather than mutating project config. Hidden prompts remain discoverable through /workflow:prompts list and can be restored with /workflow:prompts restore .

  • ↑↓ navigate prompts · ←→/Tab switch tabs
  • ↵ run prompt · configured app.message.followUp key (default Alt+Enter / Option+Enter) queues the selected prompt · d details
  • e edits the prompt before running on core tabs, but edits the saved prompt/config on the CUSTOM tab
  • n adds a user prompt · o overrides the selected prompt · x deletes/hides a custom prompt after confirmation
  • In edit mode: Ctrl+Y copy, configured app.message.followUp queues the edited prompt, configured tui.input.newLine inserts a newline, Esc close/back

Prompt customization

Core prompts are bundled in the extension. Add project or user prompts using JSON config:

Create a starter config:

Example:

Rules:

  • user prompt codes must start with user.
  • project prompt codes must start with project.
  • core prompts use reserved workflow.* codes
  • invalid config warns and falls back to valid prompts instead of crashing pi
  • custom prompts are immediately usable via /workflow:help and /workflow:run
  • custom top-level slash command aliases are intentionally not registered dynamically yet
text
project: <git-root>/.pi/dev-workflow/prompts.json
user:    ${XDG_CONFIG_HOME:-~/.config}/pi/dev-workflow/prompts.json
legacy:  ~/.pi/agent/dev-workflow/prompts.json
text
/workflow:prompts init

Subagent chain

The optional workflow pipeline chain is bundled at agents/workflow-pipeline.chain.md. If your pi-subagents setup only scans .pi/agents/, copy it there after install:

Run with:

bash
mkdir -p .pi/agents
cp pi-packages/dev-workflow/agents/workflow-pipeline.chain.md .pi/agents/workflow-pipeline.chain.md
text
/run-chain workflow-pipeline -- <task>