pstack
AGENTS.md96 starsChanged 7 months agoMITView on GitHub
pstack is a collection of SKILL.md files that give AI agents structured roles for software development. Each skill is a specialist: CEO reviewer, eng manager, designer, QA lead, release engineer, debugger, and more. Skills live in .agents/skills/. Invoke them by name (e.g., /validate).
- Deletes or force-pushes
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 47
Run bun run gen:skill-docs --host codex to regenerate Codex-specific output.
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
pstack — AI Engineering Workflow
pstack is a collection of SKILL.md files that give AI agents structured roles for software development. Each skill is a specialist: CEO reviewer, eng manager, designer, QA lead, release engineer, debugger, and more.
Available skills
Skills live in .agents/skills/. Invoke them by name (e.g., /validate).
| Skill | What it does |
/validate | Start here. Reframes your product idea before you write code. |
/plan-ceo-review | CEO-level review: find the 10-star product in the request. |
/plan-eng-review | Lock architecture, data flow, edge cases, and tests. |
/plan-design-review | Rate each design dimension 0-10, explain what a 10 looks like. |
/design-consultation | Build a complete design system from scratch. |
/review | Pre-landing PR review. Finds bugs that pass CI but break in prod. |
/debug | Systematic root-cause debugging. No fixes without investigation. |
/design-review | Design audit + fix loop with atomic commits. |
/qa | Open a real browser, find bugs, fix them, re-verify. |
/qa-only | Same as /qa but report only — no code changes. |
/ship | Run tests, review, push, open PR. One command. |
/document-release | Update all docs to match what you just shipped. |
/retro | Weekly reflect with per-person breakdowns and shipping streaks. |
/browse | Headless browser — real Chromium, real clicks, ~100ms/command. |
/setup-browser-cookies | Import cookies from your real browser for authenticated testing. |
/careful | Warn before destructive commands (rm -rf, DROP TABLE, force-push). |
/freeze | Lock edits to one directory. Hard block, not just a warning. |
/guard | Activate both careful + freeze at once. |
/unfreeze | Remove directory edit restrictions. |
/pstack-upgrade | Update pstack to the latest version. |
Build commands
bun install # install dependencies
bun test # run tests (free, <5s)
bun run build # generate docs + compile binaries
bun run gen:skill-docs # regenerate SKILL.md files from templates
bun run skill:check # health dashboard for all skillsKey conventions
- SKILL.md files are generated from
.tmpltemplates. Edit the template, not the output. - Run
bun run gen:skill-docs --host codexto regenerate Codex-specific output. - The browse binary provides headless browser access. Use
$B <command>in skills. - Safety skills (careful, freeze, guard) use inline advisory prose — always confirm before destructive operations.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository31 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- benchmarkSkill
- browseSkill
- carefulSkill
- codexSkill
- connect-chromeSkill
- csoSkill
- design-consultationSkill
- design-reviewSkill
- design-shotgunSkill
- document-releaseSkill
- freezeSkill
- guardSkill
- investigateSkill
- land-and-deploySkill
- monitorSkill
- plan-ceo-reviewSkill
- plan-design-reviewSkill
- plan-eng-reviewSkill
- planSkill
- pstack-upgradeSkill
- qa-onlySkill
- qaSkill
- reflectSkill
- reviewSkill
- setup-browser-cookiesSkill
- setup-deploySkill
- shipSkill
- pstackSkill
- unfreezeSkill
- validateSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.