enterprise-stack

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).

Jump to install

Repository: liyown/superpower-enterprise
Last source activity: June 10, 2026 at 06:47
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/liyown/superpower-enterprise --skill enterprise-stack

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

data-lineage-trace

Use when you need to prove where a piece of data (PII, PHI, payment data, customer identifier) originates, where it flows through the system, where it lands, and who reads it. Triggers on: data lineage, PII flow, GDPR right-to-erasure, data residency, schema change, retention policy, 'where does field X come from', 'who reads PII column Y', 'walk this field end to end', deletion propagation, audit trail, data classification. Do NOT use for: static code review (use java-code-reviewer, react-code-reviewer, go-code-reviewer, python-code-reviewer, or node-code-reviewer for that), or for design-time brainstorming (use obra/superpowers brainstorming). Complementary to goal-driven-development, which orchestrates the spec-to-code flow; data-lineage-trace is the regulated-data counterpart that runs after a change lands.

2026-06-10

goal-driven-development

Use this skill to orchestrate an existing goal or spec through the dev flow. Load when the user asks for end-to-end feature execution, a goal-to-PR pipeline, or any task that crosses spec → implementation → review → knowledge capture. The skill is a thin router: it names the 6 phases (spec intake, blast-radius check, implementation, verification, review gate, knowledge capture) and the skill that does the work for each phase. Do NOT use for: a single review (load the matching `*-code-reviewer` directly), or for a generic author-craft task like TDD / debugging / brainstorming (use obra/superpowers). Complementary to the 17 enterprise-flow skills; for the planned v0.6.1+ skills, the orchestrator names which of them does the work for each phase.

2026-06-10

pr-authoring

"Use when preparing a pull request for an enterprise repo: organise the PR description, attach the verification evidence, name the required reviewers per CODEOWNERS, surface linked issues / RFCs / design docs, and emit a 中文 + 企业 CI 兼容的 PR body. Triggers on: 写 PR, PR 描述, 整理 commit, 准备合入, code review 请求, 列出 reviewer, 附 verification 证据, link issue, link RFC, 关联设计文档. Do NOT use for: cross-team blast-radius analysis (use code-ownership-impact), or for the long-form RFC (use cross-team-rfc-draft). Complementary to code-ownership-impact, which is the per-PR packet in English + generic; pr-authoring is the 中文 + 企业 CI 实践 + 多 reviewer 列表 variant, emits a PR body shaped for the consumer's existing PR template, and links RFCs / design docs / issues in the format the org uses."

2026-06-10

View all from this repository

name	enterprise-stack
description	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).
metadata	{"short-description":"Single install point for the superpower-enterprise collection"}

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`

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.

enterprise-stack

Install options

Review the source files

Enterprise Stack

Relationship to superpowers

Required Loading

Combined Install

Skills In This Collection (today)

When To Load This Skill

Examples

See Also

Enterprise Stack

Relationship to superpowers

Required Loading

Combined Install

Skills In This Collection (today)

When To Load This Skill

Examples

See Also

enterprise-stack

Source facts

Install options

Review the source files

More from this repository

Enterprise Stack

Relationship to superpowers

Required Loading

Combined Install

Skills In This Collection (today)

When To Load This Skill

Examples

See Also

Enterprise Stack

Relationship to superpowers

Required Loading

Combined Install

Skills In This Collection (today)

When To Load This Skill

Examples

See Also

More from this repository