@cleepi/crew

Cleevio-flavored crew of subagents (oracle, scout, planner, reviewer, worker + custom historian/spec-critic) wired on top of pi-subagents and pi-intercom, with @cleepi/git conventions wired into the worker/reviewer/planner skill stacks. Glue layer; pi-sub

Packages

Package details

extensionskillprompt

Install @cleepi/crew from npm and Pi will load the resources declared by the package manifest.

$ pi install npm:@cleepi/crew
Package
@cleepi/crew
Version
0.5.0
Published
Jun 2, 2026
Downloads
not available
Author
honem
License
MIT
Types
extension, skill, prompt
Size
129.6 KB
Dependencies
0 dependencies · 6 peers
Pi manifest JSON
{
  "extensions": [
    "./extensions"
  ],
  "skills": [
    "./skills"
  ],
  "prompts": [
    "./prompts"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

@cleepi/crew

Cleevio-flavored crew of subagents on top of pi-subagents, wired for the @cleepi/sdd workflow. One install, a crew that pushes back instead of just doing whatever you typed.

Status: v0.4.0 shipped 2026-06-01. v0.3.0 shipped 2026-05-28. v0.1.0 (2026-05-27) per spec 0004; v0.2.0 follows @cleepi/sdd v0.2.0+ conventions (decisions in spec ## Decision sections, journals for in-flight thinking, ADR artifact gone); v0.3.0 swaps bundled deps for peer deps per DRAFT-003. v0.3.0 changes the install flow — see Installation below.

What you get

  • oracle — flavored with Cleepi's "partner not order-taker" voice. Pushes back. Proposes alternatives. Asks before building.
  • scout, reviewer, planner — knows the Cleepi monorepo, the SDD lifecycle (v0.2.0+ ticket-keyed layout, spec Decision sections, journals, optional CONSTITUTION), where decisions live.
  • cleepi-crew.historian — reads accepted specs (with their ## Decision sections), CONSTITUTION.md invariants, changelogs, and v0.1.x ADR archives across the repo.
  • cleepi-crew.spec-critic — narrower oracle, specifically for draft specs. Catches missing or stub ## Decision sections, filler optional sections (non-goals / risks that fail the delete test), scope creep against the parent SPEC.md.
  • /spec-with-crew <title> — historian → scout → drafter → spec-critic. Hands off to /spec if @cleepi/sdd is loaded (scaffolds into docs/<ticket-id>-slug/spec.md).
  • /implement-spec <spec-id-or-path> — scout → worker → reviewer, with optional oracle pre-step. Worker updates the spec's sibling journal.md when it hits friction.

Installation

Crew v0.4.0 requires four peer pi packages (pi-subagents, pi-intercom, pi-web-access, @cleepi/git). The included first-run dialog installs them automatically in crew's scope after you confirm. No prepack, no bundled tarball.

@cleepi/git is required because worker/reviewer/planner load the git-commit, git-branch, and git-pr skills from it (per DRAFT-005).

Default (user scope — available in every project):

pi install npm:@cleepi/crew
# On first pi session: "Crew needs 4 more package(s) ... Install? [Y/n]"
# Say Y, then /reload.

Project-scope only:

cd <project>
pi install -l npm:@cleepi/crew
# Same dialog, scoped to ./.pi/.

Power-user one-liner (skip the dialog):

pi install npm:@cleepi/crew npm:pi-subagents npm:pi-intercom npm:pi-web-access
# Or with -l for project scope.

After peers are installed, the extension also merges its agentOverrides defaults into the matching settings.json and symlinks the shipped agents and chains into pi-subagents' discovery dirs. Idempotent; subsequent runs are quiet.

Recovery: declined the first-run dialog, or upgrading from v0.1.0 / v0.2.0? Run /crew-setup to re-enter the same flow.

CI/non-interactive: CLEEPI_CREW_AUTO_CONFIRM=1 skips all confirms; missing peers are installed without prompting.

Tuning a crew agent

Don't edit the package source — it gets overwritten on pi update. Instead, copy the symlinked file into your project (or user) scope and edit there. Project scope wins on collision:

cp .pi/agents/cleepi-crew/historian.md .pi/agents/my-historian.md
# edit .pi/agents/my-historian.md

For tweaking the builtins (oracle, scout, planner, reviewer), use subagents.agentOverrides in your settings.json directly — see settings.example.json for the shape.

Why peer-deps, not bundled?

Through v0.2.0 crew bundled pi-subagents, pi-intercom, and pi-web-access for a one-line install. v0.3.0 dropped that for three reasons: bundled tarballs hit npm's hard-link rejection at publish time, crew lagged six minor versions behind pi-subagents, and the tarball was ~22 MB. Peer-deps fix all three; the cost is a y/N dialog on first run. See DRAFT-003 for full rationale.

Uninstall

pi remove npm:@cleepi/crew
# pi has no uninstall hook; clean up the symlinks yourself:
rm -rf .pi/agents/cleepi-crew/ .pi/chains/cleepi-crew/
# and remove the `subagents.agentOverrides` block from .pi/settings.json

# The three peer packages stay installed (other Cleepi packages
# or your own setup might use them). Remove them too if you want:
pi remove npm:pi-subagents npm:pi-intercom npm:pi-web-access

Related

  • Spec 0004 — v0.1.0 plan (shipped 2026-05-27).
  • Spec 0005 — the SDD v0.2.0 redesign that drove this package's v0.2.0 rewrite.
  • DRAFT-003 — v0.3.0 peer-deps shift, supersedes the bundling decision.
  • ADR 0007 — archive: the original bundling decision, superseded by DRAFT-003.
  • pi-subagents — the runtime.
  • @cleepi/sdd — the workflow this crew is built for (v0.2.0+).