Enterprise Stack
The single install point for the liyown/superpower-enterprise collection. This meta-skill is a router: it names every skill the collection ships, the install command for each, and the closest obra/superpowers skill for the concerns the collection deliberately does not cover.
Relationship to superpowers
This collection is the enterprise augment layer for obra/superpowers. The two are complementary, not competing:
superpowers covers generic author-craft: TDD (test-driven-development), debugging (systematic-debugging), brainstorming (brainstorming), writing plans (writing-plans), requesting/receiving code review (requesting-code-review, receiving-code-review), finishing a branch (finishing-a-development-branch), subagent-driven work, using git worktrees, using superpowers itself, and writing skills.- This collection covers what
superpowers deliberately refuses to assume: language-specific production-risk review, spec-to-code orchestration, durable post-impl knowledge, doc/spec drift, and the planned enterprise-only skills (data lineage, CODEOWNERS, incident trace, compliance, rollout, RFC, observability, pr-authoring).
Install both. A consumer who loads only superpowers is missing production-risk review depth and the org / multi-team / regulated layer; a consumer who loads only this collection is missing the generic author-craft.
Required Loading
Always load prompts/inventory.md — the one-line-per-skill index that names the install command, the trigger, and the superpowers neighbour for every skill in the collection.
Combined Install
# superpowers (the base layer)
npx skills add obra/superpowers
# superpower-enterprise (the augment layer — one line per skill)
npx skills add liyown/superpower-enterprise --skill java-code-reviewer
npx skills add liyown/superpower-enterprise --skill react-code-reviewer
npx skills add liyown/superpower-enterprise --skill go-code-reviewer
npx skills add liyown/superpower-enterprise --skill python-code-reviewer
npx skills add liyown/superpower-enterprise --skill node-code-reviewer
npx skills add liyown/superpower-enterprise --skill spec-doc-linter
npx skills add liyown/superpower-enterprise --skill goal-driven-development
npx skills add liyown/superpower-enterprise --skill project-knowledge-capture
npx skills add liyown/superpower-enterprise --skill enterprise-stack
npx skills add liyown/superpower-enterprise --skill data-lineage-trace
npx skills add liyown/superpower-enterprise --skill code-ownership-impact
npx skills add liyown/superpower-enterprise --skill incident-call-trace
npx skills add liyown/superpower-enterprise --skill progressive-rollout-checklist
npx skills add liyown/superpower-enterprise --skill compliance-control-walk
npx skills add liyown/superpower-enterprise --skill observability-coverage-audit
npx skills add liyown/superpower-enterprise --skill cross-team-rfc-draft
npx skills add liyown/superpower-enterprise --skill pr-authoring
# or install everything in the collection
npx skills add liyown/superpower-enterprise
Install is idempotent — re-running updates existing skills in place.
Skills In This Collection (today)
| Skill |
Trigger |
Superpowers neighbour |
java-code-reviewer |
reviewing a Java / Spring / MyBatis / Kafka / Reactor change |
— |
react-code-reviewer |
reviewing a React / TypeScript / Next.js / Vite change |
— |
go-code-reviewer |
reviewing a Go / gRPC / sqlx / GORM change |
— |
python-code-reviewer |
reviewing a Python / asyncio / SQLAlchemy / FastAPI change |
— |
node-code-reviewer |
reviewing a Node.js / Express / Fastify / Koa / Hono / Prisma / TypeORM / Sequelize / Knex change |
— |
goal-driven-development |
turning an existing spec into code with verification, review gates, and knowledge capture |
executing-plans |
project-knowledge-capture |
done with a task and want durable post-impl knowledge persisted into docs/knowledge/ |
— |
spec-doc-linter |
syncing a module's DevAgent.md or a domain's CONTEXT.md with the code |
— |
enterprise-stack |
single install point that inventories the whole collection |
— |
data-lineage-trace |
where does a regulated field come from / who reads it / deletion propagation |
(none) |
code-ownership-impact |
rename / deprecate / schema change / cross-team / CODEOWNERS |
writing-plans |
incident-call-trace |
incident / outage / postmortem / on-call / SLO breach |
systematic-debugging |
progressive-rollout-checklist |
feature flag / canary / dark launch / rollout / rollback |
finishing-a-development-branch |
compliance-control-walk |
SOX / ISO / SOC 2 / GDPR / HIPAA / PCI / audit / control walkthrough |
verification-before-completion |
observability-coverage-audit |
blind spot / missing alert / coverage audit / gap analysis |
test-driven-development |
cross-team-rfc-draft |
RFC / design doc / cross-team review / dependency request |
brainstorming → writing-plans |
pr-authoring |
写 PR / PR 描述 / 整理 commit / 准备合入 |
requesting-code-review |
The collection has 17 skills as of v0.6.1. The 8 planned skills from the v0.5.0 RFC have all shipped.
When To Load This Skill
- An agent is being set up for the first time and the operator wants "everything enterprise".
- A consumer is choosing between two skills that look adjacent and wants a quick answer to "which one?" plus the install command.
- A consumer is writing a new skill in this collection and wants to know which neighbours it must declare cross-references for.
- A consumer wants the up-to-date list of "what is shipped" vs "what is planned" before deciding which release to pin (
#v0.5.0 vs #v0.6.1).
Examples
There are no bad-* / good-* pairs for this meta-skill. The "output" of this skill is the inventory itself; the consumer reads the table to decide which concrete skill to load. See prompts/inventory.md for the per-skill one-liner with the install command.
See Also
- The root
README.md for the combined install + the full Relationship to superpowers table.
docs/rfcs/2026-06-10-enterprise-flow-skills.md for the 8 planned skills and the boundary each draws vs superpowers.docs/knowledge/2026-06-10-v0.6.0-rename.md for the rename rationale and migration from the pre-v0.6.0 liyown/skills-registry repo path.
1---2name: enterprise-stack3description: Use when an agent needs the full enterprise-dev-flow skill set: language-specific code review (java/react/go/python/node), spec-to-code orchestration (goal-driven-development), durable post-impl knowledge (project-knowledge-capture), doc drift linting (spec-doc-linter), and (planned) data lineage / CODEOWNERS / incident trace / compliance / rollout / RFC / observability skills. Triggers on: 'set up enterprise skills', 'install the full stack', 'enterprise-stack', 'give me the augment', 'what skills should I load', 'superpower-enterprise'. Do NOT use for: a single review (load the matching `*-code-reviewer` directly); a generic TDD/debugging/brainstorming request (use obra/superpowers).4---56# Enterprise Stack78The single install point for the [`liyown/superpower-enterprise`](https://github.com/liyown/superpower-enterprise) collection. This meta-skill is a router: it names every skill the collection ships, the install command for each, and the closest `obra/superpowers` skill for the concerns the collection deliberately does not cover.910## Relationship to superpowers1112This collection is the **enterprise augment layer** for [`obra/superpowers`](https://github.com/obra/superpowers). The two are complementary, not competing:1314- `superpowers` covers generic author-craft: TDD (`test-driven-development`), debugging (`systematic-debugging`), brainstorming (`brainstorming`), writing plans (`writing-plans`), requesting/receiving code review (`requesting-code-review`, `receiving-code-review`), finishing a branch (`finishing-a-development-branch`), subagent-driven work, using git worktrees, using superpowers itself, and writing skills.15- This collection covers what `superpowers` deliberately refuses to assume: language-specific production-risk review, spec-to-code orchestration, durable post-impl knowledge, doc/spec drift, and the planned enterprise-only skills (data lineage, CODEOWNERS, incident trace, compliance, rollout, RFC, observability, pr-authoring).1617Install both. A consumer who loads only `superpowers` is missing production-risk review depth and the org / multi-team / regulated layer; a consumer who loads only this collection is missing the generic author-craft.1819## Required Loading2021Always load `prompts/inventory.md` — the one-line-per-skill index that names the install command, the trigger, and the superpowers neighbour for every skill in the collection.2223## Combined Install2425```sh26# superpowers (the base layer)27npx skills add obra/superpowers2829# superpower-enterprise (the augment layer — one line per skill)30npx skills add liyown/superpower-enterprise --skill java-code-reviewer31npx skills add liyown/superpower-enterprise --skill react-code-reviewer32npx skills add liyown/superpower-enterprise --skill go-code-reviewer33npx skills add liyown/superpower-enterprise --skill python-code-reviewer34npx skills add liyown/superpower-enterprise --skill node-code-reviewer35npx skills add liyown/superpower-enterprise --skill spec-doc-linter36npx skills add liyown/superpower-enterprise --skill goal-driven-development37npx skills add liyown/superpower-enterprise --skill project-knowledge-capture38npx skills add liyown/superpower-enterprise --skill enterprise-stack39npx skills add liyown/superpower-enterprise --skill data-lineage-trace40npx skills add liyown/superpower-enterprise --skill code-ownership-impact41npx skills add liyown/superpower-enterprise --skill incident-call-trace42npx skills add liyown/superpower-enterprise --skill progressive-rollout-checklist43npx skills add liyown/superpower-enterprise --skill compliance-control-walk44npx skills add liyown/superpower-enterprise --skill observability-coverage-audit45npx skills add liyown/superpower-enterprise --skill cross-team-rfc-draft46npx skills add liyown/superpower-enterprise --skill pr-authoring4748# or install everything in the collection49npx skills add liyown/superpower-enterprise50```5152Install is idempotent — re-running updates existing skills in place.5354## Skills In This Collection (today)5556| Skill | Trigger | Superpowers neighbour |57| --- | --- | --- |58| `java-code-reviewer` | reviewing a Java / Spring / MyBatis / Kafka / Reactor change | — |59| `react-code-reviewer` | reviewing a React / TypeScript / Next.js / Vite change | — |60| `go-code-reviewer` | reviewing a Go / gRPC / sqlx / GORM change | — |61| `python-code-reviewer` | reviewing a Python / asyncio / SQLAlchemy / FastAPI change | — |62| `node-code-reviewer` | reviewing a Node.js / Express / Fastify / Koa / Hono / Prisma / TypeORM / Sequelize / Knex change | — |63| `goal-driven-development` | turning an existing spec into code with verification, review gates, and knowledge capture | `executing-plans` |64| `project-knowledge-capture` | done with a task and want durable post-impl knowledge persisted into `docs/knowledge/` | — |65| `spec-doc-linter` | syncing a module's DevAgent.md or a domain's CONTEXT.md with the code | — |66| `enterprise-stack` | single install point that inventories the whole collection | — |67| `data-lineage-trace` | where does a regulated field come from / who reads it / deletion propagation | (none) |68| `code-ownership-impact` | rename / deprecate / schema change / cross-team / CODEOWNERS | `writing-plans` |69| `incident-call-trace` | incident / outage / postmortem / on-call / SLO breach | `systematic-debugging` |70| `progressive-rollout-checklist` | feature flag / canary / dark launch / rollout / rollback | `finishing-a-development-branch` |71| `compliance-control-walk` | SOX / ISO / SOC 2 / GDPR / HIPAA / PCI / audit / control walkthrough | `verification-before-completion` |72| `observability-coverage-audit` | blind spot / missing alert / coverage audit / gap analysis | `test-driven-development` |73| `cross-team-rfc-draft` | RFC / design doc / cross-team review / dependency request | `brainstorming` → `writing-plans` |74| `pr-authoring` | 写 PR / PR 描述 / 整理 commit / 准备合入 | `requesting-code-review` |7576The collection has 17 skills as of v0.6.1. The 8 planned skills from the v0.5.0 RFC have all shipped.7778## When To Load This Skill7980- An agent is being set up for the first time and the operator wants "everything enterprise".81- A consumer is choosing between two skills that look adjacent and wants a quick answer to "which one?" plus the install command.82- A consumer is writing a new skill in this collection and wants to know which neighbours it must declare cross-references for.83- A consumer wants the up-to-date list of "what is shipped" vs "what is planned" before deciding which release to pin (`#v0.5.0` vs `#v0.6.1`).8485## Examples8687There are no `bad-*` / `good-*` pairs for this meta-skill. The "output" of this skill is the inventory itself; the consumer reads the table to decide which concrete skill to load. See `prompts/inventory.md` for the per-skill one-liner with the install command.8889## See Also9091- The root `README.md` for the combined install + the full Relationship to superpowers table.92- `docs/rfcs/2026-06-10-enterprise-flow-skills.md` for the 8 planned skills and the boundary each draws vs superpowers.93- `docs/knowledge/2026-06-10-v0.6.0-rename.md` for the rename rationale and migration from the pre-v0.6.0 `liyown/skills-registry` repo path.
liyown