Enterprise Delivery

Enterprise Delivery is a standalone plugin that adds repo-first agile delivery governance for agentic software work.

It is designed to run alongside Superpowers. Superpowers handles engineering workflow. Enterprise Delivery handles requirements, backlog, sprint and release tracking, change tracking, traceability, risk and status reporting, and validation gates.

Principles

• Repo-first source of truth.
• External tools are links, not canonical state.
• Every story has a linked CHG-* record from creation.
• Validation gates require evidence before completion claims.
• Brownfield onboarding labels facts as confirmed, inferred, or unknown.
• No third-party runtime dependencies.

Target Project Artifacts

Enterprise Delivery stores project artifacts in:

docs/enterprise/
  project-charter.md
  roadmap.md
  architecture-overview.md
  onboarding-audit.md  # brownfield-only audit artifact
  test-strategy.md
  stakeholder-register.md
  risk-register.md
  decision-log.md
  product-backlog.md
  change-log.md
  project-vision.md
  current-state.md
  task-graph.json
  changes/
  stories/
  sprints/
  releases/

AI-Native State Layer

For spec-driven AI-native projects, Enterprise Delivery also keeps project memory under docs/enterprise/:

• project-vision.md: product goals, non-goals, architecture principles, forbidden patterns, coding philosophy, quality bar, and AI collaboration rules.
• current-state.md: active stories and changes, failing tests, TODOs, coverage, unresolved bugs, recent commits, risks, decisions, and next verification commands.
• task-graph.json: machine-readable task dependencies for humans and agents.

These files are part of the same source of truth as stories, changes, risks, decisions, sprints, and releases. Do not create root-level project state files that drift from docs/enterprise/.

npm and Codex Install

Install the package into the current project's local Codex plugin marketplace:

npx enterprise-delivery install codex

The command copies the Enterprise Delivery plugin payload into:

./.agents/plugins/plugins/enterprise-delivery/

It also creates or updates:

./.agents/plugins/marketplace.json

The command is safe to rerun. It replaces the managed enterprise-delivery plugin copy in the project and preserves unrelated project marketplace entries.

Claude support is reserved for a later adapter:

npx enterprise-delivery install claude

For now this command only reports that the Claude adapter is planned but not implemented.

Validation

Initialize delivery artifacts in a target project repository:

node /path/to/enterprise-delivery/scripts/enterprise-delivery-validate.mjs init

The init command creates missing files under docs/enterprise/ from templates and preserves existing files.

Run validation from a target project repository:

node /path/to/enterprise-delivery/scripts/enterprise-delivery-validate.mjs validate repo
node /path/to/enterprise-delivery/scripts/enterprise-delivery-validate.mjs validate feature --story STORY-0001
node /path/to/enterprise-delivery/scripts/enterprise-delivery-validate.mjs validate sprint --sprint 2026-W20
node /path/to/enterprise-delivery/scripts/enterprise-delivery-validate.mjs validate release --release 2026.05.0

Use --root PATH to initialize or validate a different repository and --json for machine-readable output.

Exit codes:

• 0: validation passed
• 1: validation failed because artifacts are missing or invalid
• 2: command usage was invalid

Skills

• enterprise-kickoff: initialize or audit docs/enterprise/.
• add-requirement: create a linked STORY-* and CHG-* from a new request.
• change-requirement: revise existing requirement artifacts and trace changed scope.
• analyze-requirement: clarify scope, risks, tasks, and planned evidence before coding.
• analyze-tech-stack: document stack facts, tradeoffs, decisions, and risks.
• update-coding-rules: update agent rules, project principles, quality gates, and workflow instructions.
• start-task: begin implementation from a story/change/task graph entry.
• complete-task: run verification, record evidence, and prepare feature completion.
• story-intake: create or update story and mandatory change records.
• delivery-planning: map acceptance criteria to tasks, tests, docs, and risks.
• delivery-lead: guide agents through project start, requirement intake, requirement analysis, tech-stack decisions, coding rules, task start, and completion.
• feature-gate: validate story completion evidence.
• sprint-gate: validate sprint state and reporting.
• release-gate: validate release traceability and readiness.

Brownfield Rule

Do not fabricate enterprise history. Facts discovered from files may be marked inferred. Stakeholders, roadmap, sprint commitments, release state, and approvals require explicit human confirmation before they are marked confirmed.