Updated today
by creedants
pstack-t3
Lauren Tan's pstack agent skills, ported to T3 Code so any model can lead and other models can review the work. Adds brigade, a standing coordinator per project that runs each unit of work in its own git worktree, has another model family review the commit when one can run, and lands it through a queue that is the only writer to trunk.
11 GitHub stars (11)
+11 in 14 days
- 30 skills (30 skills found in its SKILL.md files)
- 4 forks (4 forks)
- Today last update (Last updated today)
Install
Skills CLI
npx skills add creedants/pstack-t3
Asks which skills and agents to install. Just one: npx skills add creedants/pstack-t3 --skill architect — add -g for every project.
Claude Code
git clone https://github.com/creedants/pstack-t3cp -r "pstack-t3/skills/architect" ~/.claude/skills/
Copies the architect skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add creedants/pstack-t3
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 81 files.
-
architect
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
skills/architect/SKILL.md on GitHub (opens in a new tab) -
arena
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
skills/arena/SKILL.md on GitHub (opens in a new tab) -
automate-me
Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via pstack-author-skill + unslop, installed for every T3 provider, optionally pulling fresh evidence from recent T3 threads.
skills/automate-me/SKILL.md on GitHub (opens in a new tab) -
benchmark-checklist
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.
skills/benchmark-checklist/SKILL.md on GitHub (opens in a new tab) -
blast-radius
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
skills/blast-radius/SKILL.md on GitHub (opens in a new tab) -
brigade-admin
Run the executive admin for the brigade coordinators on one repository. It is one pinned T3 thread that forwards the user's requests, files shared intake once, rules on conflicts between coordinators by published rules the user can overrule, and writes one plain-language update. Use for 'executive admin', 'open an executive admin', 'an admin over the coordinators on one repository', 'recover the…
skills/brigade-admin/SKILL.md on GitHub (opens in a new tab) -
brigade
Give a project or a focus area its own standing head chef. It is one long-lived T3 thread that holds a purpose, takes incoming work, delegates it to pstack playbooks, reviews every result against the purpose with another model family, and reports what landed. Use for 'brigade', 'open a restaurant', 'head chef for X', 'chief of staff for this project', 'a standing coordinator for this goal', or ru…
skills/brigade/SKILL.md on GitHub (opens in a new tab) -
bro
Restate the last message in plain human language, with no jargon.
skills/bro/SKILL.md on GitHub (opens in a new tab) -
correct
Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.
skills/correct/SKILL.md on GitHub (opens in a new tab) -
create-verification-skill
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
skills/create-verification-skill/SKILL.md on GitHub (opens in a new tab) -
figure-it-out
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions. Use for /figure-it-out or 'figure it out'.
skills/figure-it-out/SKILL.md on GitHub (opens in a new tab) -
how
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
skills/how/SKILL.md on GitHub (opens in a new tab) -
in-your-own-words
Restate in your own words what you think the user's goals are and what problem they're trying to solve. Use for /in-your-own-words.
skills/in-your-own-words/SKILL.md on GitHub (opens in a new tab) -
interrogate
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
skills/interrogate/SKILL.md on GitHub (opens in a new tab) -
ketchup
Catch the user up on what changed in this chat since their last message, in a few plain sentences and small visuals. Give each action item just enough context to make the call. Use for /ketchup.
skills/ketchup/SKILL.md on GitHub (opens in a new tab) -
landing
Let many agents write to one repository at once without collisions: a per-repository landing contract, path leases claimed before work starts, one queue that is the only writer to trunk, and a machine-wide slot governor for builds and tests. Use for 'landing', 'land this', 'merge queue', 'many agents on one repo', 'where does this work land', or before any coordinator (brigade, Orchestrate, Autop…
skills/landing/SKILL.md on GitHub (opens in a new tab) -
maintain-verification-skill
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
skills/maintain-verification-skill/SKILL.md on GitHub (opens in a new tab) -
make-bot-ui
Use when building a custom UI (page, dashboard, buttons) that should wake an existing bot over its webhook (for example a Grok Bot or Cursor automation routine), when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
skills/make-bot-ui/SKILL.md on GitHub (opens in a new tab) -
no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
skills/no-comments/SKILL.md on GitHub (opens in a new tab) -
poteto-help
Guides users through pstack setup, $poteto-mode, and picking the skill, playbook, or principle for a task. Type $poteto-help with a question.
skills/poteto-help/SKILL.md on GitHub (opens in a new tab) -
poteto-mode
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
skills/poteto-mode/SKILL.md on GitHub (opens in a new tab) -
principle-attack-the-premise
Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.
skills/principle-attack-the-premise/SKILL.md on GitHub (opens in a new tab) -
principle-boundary-discipline
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
skills/principle-boundary-discipline/SKILL.md on GitHub (opens in a new tab) -
principle-build-the-lever
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
skills/principle-build-the-lever/SKILL.md on GitHub (opens in a new tab) -
principle-encode-lessons-in-structure
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
skills/principle-encode-lessons-in-structure/SKILL.md on GitHub (opens in a new tab) -
principle-exhaust-the-design-space
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
skills/principle-exhaust-the-design-space/SKILL.md on GitHub (opens in a new tab) -
principle-experience-first
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
skills/principle-experience-first/SKILL.md on GitHub (opens in a new tab) -
principle-explain-the-number
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
skills/principle-explain-the-number/SKILL.md on GitHub (opens in a new tab) -
principle-fix-root-causes
Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
skills/principle-fix-root-causes/SKILL.md on GitHub (opens in a new tab) -
principle-foundational-thinking
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
skills/principle-foundational-thinking/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.