AI Agent Workflow Collection

Guided setup for the user-level project registry at ~/.pstack/config.json. Walks any user (tech or non-tech) through registering a repo + GitHub Project + per-Project defaults, so subsequent pstack skills can resolve "which project" without a cwd. Idempotent — re-running against an existing nickname offers update. Detects missing gh CLI and falls back to manual entry. Use when asked to "set up a project", "register a project", "/pstack-add-project", or "configure pstack for a new repo".

Append a failed-approach entry to docs/anti-patterns.md. Invoked manually or prompted by /pstack-pr. Use when asked to "log anti-pattern", "/pstack-anti-pattern", "this approach failed".

Reviewer-side AI brief on a PR. Summarizes the change, flags risk areas, matches against anti-patterns. Reduces reviewer context-load cost. Uses GitHub MCP — works from Claude Desktop or Claude Code without gh CLI. Use when asked to "review brief", "/pstack-brief", "brief me on PR".

Programmatic alignment audit for pstack-managed repos. Greps the repo for known-stale vocabulary, dropped invocations (gstack, codex), and posture references that drifted from the canonical conventions. Reports findings with file:line evidence; --fix applies safe auto-substitutions. Run on demand, or wire into CI via .github/workflows/pstack-doctor.yml. Use when asked to "audit pstack alignment", "/pstack-doctor", "check for drift", or "run the doctor".

Create or update a domain doc. Domains are the long-lived layer above features. Use when asked to "create a domain", "update a domain", "/pstack-domain", or "new product surface".

Pick up a GitHub issue and implement it. On the first story for an Epic, freezes the drafty spec from the Epic body into docs/specs/ .md as part of the story's PR. Worktree defaults to Y for monorepos. Orchestrates TDD, systematic debugging, and pre-completion verification via superpowers; optional Codex second opinions for architectural choices. Use when asked to "execute issue", "/pstack-execute", "pick up issue", or "implement ".

Scaffold pstack content into a project: docs/ folder structure, CLAUDE.md rendered from template, anti-patterns.md, and a .pstack-version marker. Detects monorepo vs single-app. Use when asked to "init pstack", "scaffold pstack", "set up pstack in this project", or "pstack init".

File a single GitHub issue with shape selector mapped to existing issue templates. Uses GitHub MCP — runs from Claude Desktop or Claude Code without gh CLI or a local repo clone. Skips full /pstack-plan ceremony. Shapes: story, task, bug, feature, epic, docs. Use when asked to "file an issue", "/pstack-issue", "open a bug", "open a task".

Wrap gstack /office-hours and post the result to the project's pinned Vision GitHub Issue via GitHub MCP. One-way data flow: gstack does its strategic brainstorming methodology, pstack imports the result into a team-shared GitHub Issue. gstack's local archive at ~/.gstack/projects/ is left intact. Requires Claude Code + gstack + GitHub MCP. Use when asked to "brainstorm the vision", "office hours for this project", "import office-hours to vision", "update project vision", or when starting to define what a project is about.

Full feature/refactor ceremony: brainstorm → spec → eng-review → decompose → file Epic + sub-issues. Drafty spec lives in the Epic issue body (web-UI editable); it's frozen to docs/specs/ by /pstack-execute on first story. Can promote an existing Feature Request into an Epic. Uses GitHub MCP — runs from Claude Desktop or Claude Code without gh CLI. Use when asked to "spec a feature", "plan a feature", "/pstack-plan", "promote this feature request", or "start a new feature".

End-of-implementation review and PR creation. Enforces conventional commits, orchestrates the full review gauntlet (gstack /review, /codex review + challenge, optional /qa and /design-review for UI changes, /health for the quality score), prompts for anti-patterns, opens the PR with the standard pstack body template. Stays on gh + local git (developer-side; PMs and non-tech users don't open PRs). Use when asked to "open PR", "/pstack-pr", "ship this branch".

High-fidelity prototype workflow. Monorepo: lands in apps/lab/ /. Output: working prototype + DESIGN.md + preview deploy. Uses the project's existing design system; calls gstack's audit skills (/qa-only, /design-review) for verification but never gstack's design-generation skills (which would impose foreign visual patterns). Asks about graduating to component+storybook. Use when asked to "prototype", "spike a UI", "/pstack-prototype", or "explore an idea".

Research spike. Output is a research doc, not code. Frames the question via superpowers:brainstorming; optionally consults gstack /codex consult for cross-model second opinions during the spike. Optionally graduates to /pstack-plan or /pstack-anti-pattern. Use when asked to "research", "spike", "investigate", "/pstack-research", or "do a research spike".

Scaffold release-please into a pstack-managed project for opinionated, bot-driven release automation. Copies the three pstack release-please templates (workflow, config, manifest), substitutes package name and initial version, and prints the manual GitHub-side setup steps (tag ruleset bypass for the bot). Opt-in — invoke explicitly when a project wants automated releases. Use when asked to "set up release-please", "/pstack-setup-release-please", "add release automation", or "automate releases for this project".

Detects the user's installed pstack version vs the latest marketplace version, prints CHANGELOG/release notes for the gap, runs versioned on-disk migrations, and tells the user exactly which /plugin update + restart steps to perform (Claude Code can't trigger the plugin update from inside a skill). Other pstack skills' preambles surface a one-line nudge when an upgrade is available. Use when asked to "upgrade pstack", "update pstack", "/pstack-upgrade", or "get latest pstack".

Strategic brainstorming via superpowers:brainstorming, persisted as a research doc under docs/research/ and posted to the project's pinned Vision GitHub Issue via GitHub MCP. Self-contained — no external CLIs, no ~/.gstack/ indirection. Use when asked to "brainstorm the vision", "what's our vision", "update project vision", or when starting to define what a project is about.