p3-stack

A maintained T3 Code adaptation of Lauren Tan's pstack, forked from uzairansaruzi/p3-stack.

The reviewed baseline is pstack 0.15.25, commit 6f131f137de64fdaf928278c0fd9ecec520ccbee. All 54 skills, 24 principles, and 23 playbooks are included. Principles stay exact. T3 adaptations and imported-file hashes are recorded in PORTING.md and upstream.lock.json.

pstack helps agents write less, higher quality code through deliberate design, independent review, and proof on the real application. Use individual skills when you need them, or let /p3-mode route rigorous work.

Install in WSL or Linux

Requires Node.js 22 or newer. The executable helper tooling also requires Bun 1.4.3 or newer and Git. GitHub workflows use gh.

mkdir -p ~/src
git clone https://github.com/mrdbstn/p3-stack.git ~/src/p3-stack
cd ~/src/p3-stack
node install.mjs

Use Linux-native Git, Node, and Bun from PATH. Keep this checkout, project checkouts, and dependency stores under your Linux home, not /mnt/c. Run the installer inside WSL using the same Linux user/environment as T3's agent. A Windows installation of the skills is not a WSL installation.

For one project, use node install.mjs --project /home/you/src/project. The installer links skills into ~/.agents/skills/ or the project's .agents/skills/, preserves existing real directories, and can be rerun. Keep this checkout while its skills are installed. ./install.sh is an equivalent Unix convenience wrapper. Native Windows is also supported through node install.mjs, using directory junctions.

Use

1. Run /setup-p3 to choose your budget and available model roles.
2. Prefix a task needing rigor with /p3-mode and state how to tell it is done.
3. Ask /p3-help when unsure which skill fits.

Project-root p3-models.md overrides ~/.agents/p3-models.md. Settings are read at task start. Unconfigured roles inherit the parent model; configure panels to obtain model diversity. Installation alone does not invoke the skills. Save the full mode for work that needs its extra review and verification.

T3 must expose the orchestration tools used by the chosen workflow. Models and options come from orchestrator_capabilities. Writers use isolated delegated worktrees. The parent owns PR watches. Ordinary top-level conversations are created only when explicitly requested. See the runtime contract.

Proof tooling

The original executable plan checker and orchestration CLI are bundled:

node skills/p3-mode/scripts/check-plan.mjs /path/to/plan.md
bun skills/p3-mode/scripts/orch/orch.ts --store /path/to/project/orchestrate/run init

Installed skills resolve these paths from their own location. The store retains atomic writes, locking, current-head verification verdicts, inboxes, and derived status. Native T3 links and schedules complement that store.

Verify and maintain

node scripts/check.mjs
node --test tests/*.test.mjs
bun install --cwd skills/p3-mode/scripts --frozen-lockfile
bun test --cwd skills/p3-mode/scripts
bun run --cwd skills/p3-mode/scripts typecheck

CI runs the same checks on Linux and Windows. UPSTREAM.md explains the read-only upstream status, three-way proposal, review, and lock-recording process. New source revisions require review; nothing automatically overwrites the T3 adaptations.

These checks establish source coverage and tool behavior. A live T3 model-behavior smoke run is still required to validate an installed app/provider combination.

Credit

The skills, principles, and engineering approach are Lauren Tan's pstack. The original T3 adaptation is by uzairansaruzi. This fork maintains the source sync, native runtime mappings, packaging, and verification. MIT, see LICENSE.