https://github.com/periant-llc/pstack
Power Stack — a Claude Code workflow toolkit for AI-paced development. Composes gstack, Superpowers, and GitNexus into a domain → feature → story workflow.
https://github.com/periant-llc/pstack
ai-development claude-code claude-code-skills developer-tools workflow-automation
Last synced: about 1 month ago
JSON representation
Power Stack — a Claude Code workflow toolkit for AI-paced development. Composes gstack, Superpowers, and GitNexus into a domain → feature → story workflow.
- Host: GitHub
- URL: https://github.com/periant-llc/pstack
- Owner: periant-llc
- License: mit
- Created: 2026-05-01T19:37:54.000Z (about 2 months ago)
- Default Branch: main
- Last Pushed: 2026-05-12T17:01:57.000Z (about 1 month ago)
- Last Synced: 2026-05-12T18:33:20.584Z (about 1 month ago)
- Topics: ai-development, claude-code, claude-code-skills, developer-tools, workflow-automation
- Language: Shell
- Size: 115 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# pstack
> Power Stack — a Claude Code workflow toolkit for AI-paced development.
A skill bundle that combines the best of gstack (planning, design, QA), Superpowers (TDD, plans, brainstorming), GitHub MCP (Issues/PRs without `gh`), GitNexus (knowledge graph), and team-specific conventions into a coherent workflow for shipping AI-paced code.
## Philosophy
- **Three-layer content model.** Vision (strategic, in a pinned GitHub Issue) → Domain (long-lived, in `docs/domains/`) → Feature/Story (drafty Epic body → frozen `docs/specs/`).
- **Author/Dev split.** Non-tech authors file Feature Requests via GitHub web UI; technical leads run `/pstack-plan` to promote them to Epics with specs; engineers run `/pstack-execute` to build. Pstack runs in Claude Desktop or Claude Code.
- **Compose, don't reinvent.** Pstack recipes orchestrate gstack and Superpowers skills rather than reimplementing them.
- **Drafty in GitHub, stable in git.** Specs iterate in Epic issue bodies (web-UI editable, no PR ceremony) and freeze to `docs/specs/.md` on the first story's PR.
- **Smaller PRs, faster reviews.** Decomposition is a first-class step.
## Install
### Option A — Claude Code plugin (recommended)
From any Claude Code session:
```
/plugin marketplace add periant-llc/pstack
/plugin install pstack@pstack
```
The `pstack@pstack` form is `@` — both happen to be `pstack` since this repo is a single-plugin marketplace.
After install, pstack's skills are available as `/pstack-*` commands.
**Claude Desktop note:** Claude Desktop's Code-mode plugin browser supports the same marketplace format. Author-side skills use GitHub MCP for GitHub operations, so they work in Desktop without `gh` CLI or a local clone (for `/pstack-plan`, `/pstack-issue`, `/pstack-office-hours`, `/pstack-brief`).
### Option B — Legacy clone + setup (for hacking on pstack itself)
```bash
git clone https://github.com/periant-llc/pstack ~/Development/ai/pstack
~/Development/ai/pstack/scripts/setup.sh
```
This symlinks each skill into `~/.claude/skills/` (10 canonical + 10 `ps-*` aliases) and installs a `pstack-init` CLI shim into `~/.local/bin/` for terminal use. Restart Claude Code to pick up the skills. Best for contributors editing pstack itself — for normal use, prefer the plugin path.
## Usage
From a Claude Code session inside a project, the workflow commands:
| Skill | Purpose |
|---|---|
| `/pstack-init` | scaffold project structure (`docs/`, `CLAUDE.md`, `.pstack-version`) |
| `/pstack-office-hours` | brainstorm strategic Vision; posts to a pinned GitHub Issue editable by non-tech authors |
| `/pstack-plan []` | full feature/refactor ceremony; promote a Feature Request to an Epic with sub-stories |
| `/pstack-prototype` | exploratory build (monorepo: lands in `apps/lab//`) |
| `/pstack-research` | spike with research doc as output |
| `/pstack-issue` | single GitHub issue with shape selector (story/task/bug/feature/epic/docs) |
| `/pstack-domain` | create or update a domain doc |
| `/pstack-execute <#>` | pick up an issue, freeze spec on first story, TDD-implement |
| `/pstack-pr` | enforce conventional commits, run full review gauntlet, open PR |
| `/pstack-brief ` | reviewer-side AI brief on a PR |
| `/pstack-anti-pattern` | log a failed approach to `docs/anti-patterns.md` |
| `/pstack-setup-release-please` | opt-in: scaffold pstack's standardized release-please automation into the project |
Aliases: `ps-init`, `ps-plan`, `ps-prototype`, etc. (legacy install only — the plugin uses the canonical `pstack-*` names).
See [`docs/architecture/commands.md`](docs/architecture/commands.md) for the full locked command set.
## Architecture
Four layers map work from strategic context down to single PRs:
- **Vision** (pinned GitHub Issue, `label:vision`) — strategic context. Web-UI editable by non-tech authors.
- **Domain** (`docs/domains/.md`) — long-lived product surface. Living doc. `paths:` frontmatter maps code locations; `depends_on:` / `consumers:` document inter-domain interfaces.
- **Feature** — drafty spec lives in a GitHub Epic body; frozen to `docs/specs/.md` by `/pstack-execute` on the first story.
- **Story** — GitHub issue. Linked to a spec via `Parent Epic: #N`. Maps to one of: User Story, Task, Bug, Feature, Epic, Docs.
`pstack-plan` orchestrates feature definition: brainstorms with the author, writes the spec into a new Epic body, decomposes into 2–3 stories, and files them all on GitHub. `pstack-execute` then handles implementation, freezing the spec into git as the first commit of the first story's PR.
See [`docs/architecture/`](docs/architecture/) for full details:
- [`commands.md`](docs/architecture/commands.md) — the locked command set
- [`three-layer-model.md`](docs/architecture/three-layer-model.md) — domain/feature/story layers (Vision will be added soon)
- [`frontmatter.md`](docs/architecture/frontmatter.md) — YAML frontmatter conventions for rendered docs
## Roadmap
Active deferred work — commands and patterns to build when real usage demands them — is tracked in [`IDEAS.md`](IDEAS.md). Includes:
- Domain-aware subagent dispatch (v0.3) — load only relevant domain context per subagent
- `/pstack-handover` + `/pstack-resume` for cross-session work
- `/pstack-hotfix` for production-bug-specific ceremony
- pstack-lite DXT for non-tech authors in Claude Desktop (collapsed into the plugin path above — pstack now works in Desktop directly via GitHub MCP)
## Releases
Pstack uses [release-please](https://github.com/googleapis/release-please) for automated, bot-driven releases. On every push to `main`, the workflow reads conventional-commit prefixes since the last tag and opens a "Release vX.Y.Z" PR with an auto-generated CHANGELOG. Merging the PR creates the tag + GitHub Release.
This is the **standardized release tooling for pstack-managed projects**. Apply it to your own project on demand: `/pstack-setup-release-please`.
## Status
**v0.2.0** — Vision layer + drafty-spec-in-Epic-body + MCP-based author-side skills + full review-gauntlet orchestration + Claude Code plugin packaging + release-please automation. 12 skills total. Next: dogfood against a real project, observe gaps, fill in GitNexus query endpoints.