Pi Pragmatic Superpowers

A globally reusable Pi package inspired by obra/superpowers, but tuned for pragmatic engineering:

• broad subagents with enough context, not hyper-granular task shards
• meaningful tests that catch real regressions, not ritual assertions
• strict modern TypeScript/codebase review
• PR descriptions that are useful to humans
• optional project profiles such as fieldy

Install locally

pi install /Users/adomas/Projects/pi-superpowers

For a one-off run without installing:

pi -e /Users/adomas/Projects/pi-superpowers

What the package adds

Skills

• /skill:pragmatic-superpowers — entrypoint and workflow selection
• /skill:pragmatic-planning — lightweight design/planning before code
• /skill:pragmatic-implementation — execute coherent feature slices with broad subagents
• /skill:meaningful-testing — decide which tests are worth writing
• /skill:strict-code-review — review for modern TypeScript and project conventions
• /skill:pr-description — produce genuinely useful PR descriptions

Extension tool

pragmatic_subagent dispatches an isolated pi -p subprocess with one of the bundled broad agent prompts:

• implementer
• strict-reviewer
• test-reviewer
• pr-writer

It deliberately starts subprocesses with --no-extensions --no-skills so nested agents do not inherit noisy workflow monitors. The coordinator passes exactly the context the subagent needs.

Profiles

Profiles are reusable convention bundles that can be included in subagent prompts.

• default — generic modern TypeScript/project hygiene
• fieldy — Fieldy-specific oRPC, Drizzle, Zod, React Query, file layout, testing, and logging conventions

Philosophy

This package keeps the parts of Superpowers that improve outcomes — deliberate planning, isolated context, review loops, evidence before claims — and removes the parts that become ceremony.

Tests are required when they are useful. Useful tests encode behavior, permissions, parsing, schemas, workflow side effects, queue semantics, data mapping, or business rules that future edits might break. They are not required for pass-through wrappers, copy changes, or trivial transformations that would only prove JavaScript still works.

PR descriptions are treated as a product artifact. They should explain what changed, how it was implemented, why it was needed, why this approach was chosen, risks/tradeoffs, and how it was verified.

Development

bun install
bun run check

The package uses strict TypeScript and Vitest contract tests to make sure the Pi package resources remain loadable.