pstack is Lauren Tan's collection of rigorous engineering workflows for writing less, higher-quality code and parallelizing work with verifiable boundaries. This repository is a standalone Agent Plugins 1.0 port of the original cursor/plugins/pstack package, with a Kiro runtime adapter.
The root package follows Agent Plugins 1.0:
pstack-agent-plugin/
├── plugin.json
├── skills/
├── dev.kiro/
├── agent-sops/
└── docs/
Agent Plugins standardizes the manifest, Agent Skills, and optional MCP configuration. pstack ships skills and skill-local scripts; it does not ship an MCP server.
If a same-name pstack Power or native skill already exists, inspect its source before installing. Preserve an official installation and all conflicting skill targets. Do not silently replace it, rerun an installer to force discovery, or select a copy by version alone. A replacement or a new admission path needs the user's explicit scoped decision. The steps below apply to a new installation, not automatic reconciliation of an existing one.
- In Kiro IDE, open Powers and choose Add Custom Power.
- Import this repository from GitHub or select the local repository root.
- Start Kiro CLI v3 and run
/powersto confirmpstackis installed. - Ask Kiro to use
poteto-mode, or install the optionalpstack-potetoagent profile fromdev.kiro/README.md. - Run the
setup-pstackskill if you want explicit Kiro model, named-agent, or reasoning-effort routing.
Kiro agent profile installation, validation commands, runtime mappings, and unsupported hosted automation behavior are documented in dev.kiro/README.md.
Use the poteto-mode skill for non-trivial engineering work. It selects a playbook, applies the relevant principle skills, delegates bounded work when useful, and verifies the real artifact before reporting completion.
Representative skills include:
howfor code and architecture walkthroughs.poteto-helpfor installation, setup, and choosing the right skill or playbook.ketchupfor an evidence-backed plain-language catch-up and complete decision brief.ketchup-videofor the same catch-up as locally rendered subtitled slides when an authorized renderer and media channel are available.whyfor evidence-backed design history.architectandarenafor competing designs.swarmfor partitioned parallel work.interrogatefor adversarial review.pstack-tdd,blast-radius, andno-commentsfor implementation quality.benchmark-checklistandprinciple-explain-the-numberfor validating measured performance results.correctfor turning repeated agent mistakes into architecture, type, lint, CI, or test enforcement.create-formal-verification-skillandmaintain-formal-verification-skillfor bounded, code-linked properties and verification drift.statechartfor TLA+ rule checks, Mermaid state graphs, and shortest bug paths. Its optional dependencies and runtime outputs stay in authorized scratch; missing tools do not trigger an implicit installation.make-bot-uifor a bounded authenticated event UI using an actually configured external runner, with private-by-default exposure and explicit delivery proof.technical-writingandunslopfor prose.comment-sickofor independent comment review.triage-issue-reportsandreproduce-and-fix-issuesfor the portable Benny workflow contracts.sync-pstack-upstreamfor reviewing and porting parent changes without overwriting portable or Kiro adaptations.
The full guide remains under docs/guide/. Client-specific examples in the upstream guide should be interpreted through the Kiro runtime mapping. The pinned source and extraction history are recorded in docs/upstream.md.
Agent Plugins 1.0 does not standardize custom agents, model routing, transcript storage, hooks, hosted automations, or durable schedulers. The Kiro adapter provides optional custom-agent templates and explicit fallback rules. See docs/compatibility.md.
Cursor Routines, Cursor Automations, /loop, /goal, nested cloud workers, and cursor-team-kit are not represented as portable capabilities. pstack reports those capabilities as unavailable or uses a bounded Kiro fallback instead of claiming parity.
Independent changes branch from trunk. Only genuine dependencies form stacks. Verification distinguishes finished code, major behavior changes, smaller fixes, and exact-head required checks. A worker's report or green check alone is not a complete acceptance receipt. Whole-port review, accepted provenance, publication, promotion and installed delivery are separate gates.
The optional Kiro template uses a parent-supplied exact skill path before approved host discovery. It never silently selects the highest-version copy or replaces a same-name official Power. The source template does not create a Crew identity, private memory store, skill admission rule, permission grant, or schedule. Existing source and installation configuration remain under the user's control.
agent-sops/port-cursor-plugin-to-agent-plugin.sop.md defines the repeatable workflow used for this port. It covers history extraction, manifest conversion, skill normalization, client-extension isolation, Kiro adaptation, and validation.
Run:
node scripts/validate-plugin.mjs
kiro-cli agent validate --path dev.kiro/agents/pstack-poteto.json
kiro-cli agent validate --path dev.kiro/agents/pstack-comment-sicko.jsonThe Bun tools under skills/poteto-mode/scripts/ retain their existing tests and typecheck commands.
The original pstack content is by Lauren Tan and is distributed under the MIT license in LICENSE. This standalone port preserves the extracted pstack git history.