* feat(pstack): setup-pstack budget ask (max/xhigh/high/medium)
Step 3 of /setup-pstack asks for a budget first (unlimited, large,
medium, small), rewrites the effort token of every real slug in the
working table to the budget's target, clamps to the detected set within
the same family, and then shows the roles for confirmation. Step 2 reads
the recorded budget line and step 5 writes it. No version bump.
Co-authored-by: lauren <poteto@users.noreply.github.com>
* docs(pstack): mention the setup-pstack budget in README and setup guide
Co-authored-by: lauren <poteto@users.noreply.github.com>
* refactor(pstack): tighten setup-pstack step 3 to three short parts
Drop the four-by-four example table, the repeated family and fast
explanations, and the re-run essay. Keep the four budget labels, one
remap rule with a one-line example, the confirm paragraph, and the
budget line in the written rule.
Co-authored-by: lauren <poteto@users.noreply.github.com>
* fix(pstack): setup-pstack step 3 rebuilds before the budget, keeps aliases, records the chosen budget
Bugbot on #366. The working table is built from the defaults first, on
every run, so unlimited on a re-run restores the default efforts. The
carry-over set names alias roles. Step 5 says the budget line holds the
chosen label and target effort.
Co-authored-by: lauren <poteto@users.noreply.github.com>
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
* docs(pstack): port the September skill audit cuts from the internal tree
Port of the 2026-09-01 to 2026-09-07 audit program on the internal skill
tree. Deletion-only density cuts and the mannered prose pass applied
wherever the OSS sentence is the same sentence. Two new principle leaves,
Attack the Premise and Test Behavior Not Implementation, with their index
lines. Critique mode removed from how and its callers. PR-body briefing
rules in opening-a-pr and technical-writing. Model pins stay on the
setup-pstack role mechanism. No internal path, slug, or name added.
* docs(pstack): restore the autopilot chooser rule that multi-phase-plan cites
multi-phase-plan step 4 picks between autopilot-full and autopilot-stack
"per the rule at the end of playbooks/autopilot-stack.md". The density
pass removed that paragraph and left the pointer dangling. Restore the
paragraph verbatim. The chooser is a rule, not a restatement, and no
other file states it.
Addresses the Bugbot finding on PR #329.
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
* pstack: add public usage tutorial
Co-authored-by: lauren <poteto@users.noreply.github.com>
* pstack: document verification skill workflows
Co-authored-by: lauren <poteto@users.noreply.github.com>
* pstack: mention verification setup offer
Co-authored-by: lauren <poteto@users.noreply.github.com>
* pstack: clarify optional verification setup
Co-authored-by: lauren <poteto@users.noreply.github.com>
* pstack: rewrite tutorial prompts to match real usage
The example prompts read like specs. Real prompts are short, informal,
and goal-first, so every example now uses that register. The prose
reshapes around them: friendly second-person tutorial voice, goals
before mechanics, pitfalls where readers actually trip, and the
playbook reference table replaced with prompts in context. Every
skill claim re-checked against the skill files at this commit.
* pstack: make the README guide link an invitation
Point new readers at what the guide walks them through instead of
listing its topics.
* pstack: drop the version bump
This PR only adds documentation, so the plugin manifest stays at
main's 0.11.7.
* pstack: add illustrations to the guide
One hero image per major guide page (routing, understanding, design,
verification, overnight runs, recipes), 1200px JPEGs under
docs/guide/images/.
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
lauren