AGENT SKILL

pstack-help

Guides users through pstack setup, the workflow skill, and picking the skill, playbook, or principle for a task. Type /pstack-help with a question.

License 许可
MIT
最近更新
2026-10-30
Stars
★ 0
Forks
0

01 前言 Front Matter

name
pstack-help
description
Guides users through pstack setup, the workflow skill, and picking the skill, playbook, or principle for a task. Type /pstack-help with a question.
disable-model-invocation
true

02 资源文件 2

03 SKILL.md 正文

pstack help

Answer the user's question about pstack, hand them a prompt they can send, and link the file the answer came from. For a help question, don't start the work. The user asked how, and a pstack run spends real tokens, so let them send the prompt.

A message that asks for work, such as "use pstack to fix this bug", is not a help question. Do the work under the workflow skill. Load it first if the session does not already have it.

This file maps questions to the skills and guide pages that hold the answers. Those files own the details. Read the file you route to before you quote it, and trust it when it disagrees with this map. The skill links here point into the installed skills, so give the user the installed file's absolute path. The README and guide pages are not installed, so give the user their upstream public copy: https://github.com/cursor/plugins/blob/main/pstack/ followed by its path. The guide describes Cursor, so say which steps differ in this CLI.

Find out what they need

Infer the need from the message and the conversation. A named situation, such as "which skill reviews a PR?", goes straight to its section. If the need is still unclear, ask one multiple-choice question with these options, then answer only the section they pick:

  • Get set up
  • Start a task
  • Pick a skill for a situation
  • Fix a run that went wrong
  • Make pstack my own

Check the state that changes the answer, and mention it only when it does:

  • A ~/.config/agent-workflows/models.toml that is missing or still the shipped default means /setup-pstack hasn't run for this user, so every role uses its default model.
  • No verify-* skill or other app harness in the project means agents have no scripted way to drive the app. Mention /create-verification-skill when the question is about proving a change works.

When the model registry is missing or still the default and it matters, ask whether the user wants to pick a model for each role and a reasoning budget now. It matters when the user is new, the question is about setup or cost, or the answer depends on which models run. Ask at most once per chat. If the need is also unclear, ask both questions together. Offer two choices:

  • Now: give them /setup-pstack to type, and answer their question too.
  • Later: answer their question, and add one line saying every role keeps its default model until they run /setup-pstack.

Get set up

  1. Install with this package's install.py. It installs into every CLI it finds among Claude Code, Codex, and Grok, and puts aw on the PATH.
  2. Run /setup-pstack. It asks for a reasoning budget, maps a model to each role, and writes the model registry. The registry applies from the next spawn.
  3. Start a real task with a goal and a check that can pass or fail. Type /workflow ($workflow in Codex) before it, or run aw skills always workflow once so every session loads the workflow.

Installing changes nothing until a skill runs. Auto skills load on their own when a task matches, and manual ones wait for the user or a workflow step. The workflow is manual unless the user runs aw skills always workflow. aw skills lists which is which, and aw skills auto|manual NAME changes one. The README and guide page 1 have the details. Offer to word their first prompt with them, per references/prompting.md.

If cost is the worry, say where the tokens go and how to spend fewer. pstack spends extra tokens on subagents and review panels. Rerun /setup-pstack and pick a smaller budget or cheaper models, or change one role with aw models set ROLE model:effort. aw limits shows how much of each plan is left. A role set to inherit runs on the session's model, which saves tokens when the session runs on a cheaper model. Each model's provider decides which subscription pays, so moving a busy role to the other provider spreads the load. A shorter panel list runs fewer subagents, one for each entry. Ask for a lighter pass when a task doesn't need the full playbook.

This is pstack ported from Cursor to Claude Code, Codex, and Grok. The workflow skill and skills such as /how, /why, and /teach, spawn subagents with per-role models, natively in the current CLI or through aw-run on another one. Codex invokes each skill as $name instead of /name. Custom Modes are a Cursor feature, and /loop exists in Claude Code and Grok but not in Codex.

Start a task

The workflow skill matches the task to a playbook, copies the playbook's steps into the todo list, and runs the other skills as the steps need them. A step it skips stays in the list as skip: <reason>. A good prompt states the goal and how to tell it's done. It doesn't list skills, because a hand-written sequence tends to drop or reorder steps the playbook would keep. Read references/prompting.md before you help word one. Guide page 2 has examples.

aw skills always workflow imports the workflow skill into the CLI's global instructions (~/.claude/CLAUDE.md, ~/.codex/AGENTS.md, or ~/.grok/AGENTS.md), so it applies to every session and does not fade. Without it, /workflow at the start of a task loads it for that chat. Mid-chat, "new task" makes it match a fresh playbook. It already uses delegate for the subagents its playbook steps spawn. To get the same style from a subagent of your own, spawn the delegate agent.

Pick a skill

The default answer is to describe the task. The workflow skill runs most of the others when its steps need them. Name a skill directly when the user wants more or less of something than the playbook gives. Read the skill before you recommend it, and give one example prompt.

The user wants to Skill
Do any non-trivial task with rigor Type /workflow and describe it, or just describe it when the workflow is always on
Check that the agent understood their goal and the problem before it starts /in-your-own-words
Aim a task higher before starting: more expert, more outcome-focused, not overspecified /sharpen
Know how code works now, or where new code should live /how
Know why code is shaped this way, or where a number came from /why
Understand a change or subsystem, explained plainly /teach
Catch up on their own recent work on a topic /recall
Catch up on what changed in this chat since their last message, in a few plain sentences and small visuals, with enough context to decide each action item /ketchup
Know what a small diff could break outside itself /blast-radius
Settle types and module shape before code that crosses a function boundary /architect
Get several attempts at one brief, merged into the best one /arena
Run parallel checks over slices, or race workers, in separate worktrees /swarm
Have different models review a diff and try to break it /interrogate
Fix a bug test-first when a cheap local test exists /tdd
Apply TypeScript rules to .ts or .tsx work /typescript-best-practices
Strip comments before review, using a reviewer that didn't write them /no-comments
Clean AI tells out of prose /unslop
Write docs, an RFC, a README, a PR description, or a commit message to a standard /technical-writing
Hear the last reply again in plain words /bro
Give agents a scripted way to drive the app and prove behavior /create-verification-skill
Bring a verification skill and its feature map back in line with the app /maintain-verification-skill
Vet a performance number before reporting or acting on it /benchmark-checklist
Run a large or cross-cutting change, or one to review after stepping away /figure-it-out
Keep a decision log during a run, and review it afterward /show-me-your-work
Pick a model for each role and a reasoning budget /setup-pstack
Turn their own working habits into a personal mode skill /automate-me
Turn what a finished task taught into skill edits /reflect
Stop agents from repeating the same mistakes in this repo /correct
Find their way around pstack /pstack-help

If a skill directory next to this one is missing from the table, read its frontmatter and route by its description. The principle-* directories are covered under principles below.

Close calls:

  • /how explains what the code does. /why explains the reasons. /teach runs one or both and explains the result plainly.
  • /arena gives every worker the same brief and merges the best parts. /swarm splits work into slices or a race and returns one report.
  • /architect implements right after it settles the design. Add "with checkpoint" to review the design before it writes code.
  • /interrogate reviews the diff. /blast-radius looks for breakage outside the diff and proves the one fact that makes the change safe.
  • /recall rebuilds context across recent chats. /ketchup covers only this chat since the user's last message. Resuming one specific chat or branch is the Session pickup playbook.
  • /figure-it-out designs one rigorous run. The Orchestrate playbook runs a program that spans days and many PRs. The Autonomous run playbook drives one task to a finish condition.

Not in pstack:

  • /deslop, control-cli, and control-ui ship in the cursor-team-kit plugin.
  • /loop is built into Claude Code and Grok. Codex has none. skill-creator comes with the CLI.
  • pstack has no /orchestrate skill. Orchestrate is a workflow playbook. If the slash menu shows /orchestrate, another plugin provides it.

Playbooks and principles

Playbooks are step lists inside the workflow skill, not skills, so they have no slash command. Describing the task picks one, and these phrases name one directly:

  • "babysit this pr" or "check on pr 123" runs Babysit. It drives the PR to merge-ready and stops there. It doesn't merge unless the user asks to merge, land, or ship.
  • "land the stack" runs Shipping.
  • "take over this branch" runs Session pickup.
  • "pause safely" runs Pause safely.
  • "full autopilot on this queue" runs Autopilot-full. "stack them, don't ship" runs Autopilot-stack.
  • "run the eval playbook" runs Eval.

The Playbooks section of workflow lists every playbook and when it applies. Guide page 6 covers opening, babysitting, and landing a PR.

pstack has no planning skill. Claude Code's plan mode works alongside it. For work that spans phases or stacked PRs, asking for a plan runs the Multi-phase plan playbook, which writes the plan and doesn't implement it. For a design question, the Prototype playbook or /architect settles it in code first.

Principles are one-rule skills that the workflow skill reads and cites in its replies. The user rarely invokes one. They steer with the names instead, as in "apply prove it works. show me the real output." Typing /principle-<name> still loads one on demand. Guide page 8 lists them.

Fix a run that went wrong

Symptom Fix
The workflow stopped applying Check that the install's block is still in ~/.claude/CLAUDE.md, ~/.codex/AGENTS.md, or ~/.grok/AGENTS.md.
A question got treated as the next step of the last task Say "new task", or say the turn doesn't need a playbook.
A new model choice had no effect Check the role with aw-run --resolve <role>. A role set to inherit follows the session's model.
Runs cost more than expected See the cost paragraph under Get set up.
A skill didn't load on its own Only /setup-pstack loads from the user's words. The others load when the user types them or when the workflow skill runs them, and it doesn't run every skill.
Parallel agents overwrote each other Give each agent its own worktree.
An overnight run moved but finished nothing /loop (Claude Code) needs a check that can pass or fail, not a duration. See guide page 7.
The reply claims success from a green build Ask for the real command, flow, stored value, or profile. That's the prove-it-works principle.

For a run that drifts, references/prompting.md has one-line steers. Guide page 10 has more pitfalls and the recipes worth copying.

Make pstack my own

  • /automate-me drafts a personal mode skill from the user's own history, to use alongside the workflow skill.
  • /reflect after a session turns its lessons into skill edits the user approves.
  • write a skill for <workflow> runs the authoring playbook. The eval playbook tests a skill change blind.
  • Fix a misbehaving skill in its own PR, not inside the feature work where it went wrong.

Guide page 9 covers each of these.

Reply

Lead with the answer. Give at most one example prompt in a code block, adapted from references/recipes.md when one fits, then the link to that file. Keep it short unless the user asked for the whole map.

04 同仓库更多 Skills

shreshthkapai
shreshthkapai/agent-workflows

workflow

Concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work, with each task routed to a playbook. Use for /workflow, or for requests to work in this style. `aw skills always workflow` loads it into every session.

★ 0
shreshthkapai
shreshthkapai/agent-workflows

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 0
shreshthkapai
shreshthkapai/agent-workflows

unslop

Cut AI tells from any writing.

★ 0
shreshthkapai
shreshthkapai/agent-workflows

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 0
shreshthkapai
shreshthkapai/agent-workflows

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

★ 0
shreshthkapai
shreshthkapai/agent-workflows

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

★ 0