portable-agent-workflows

Portable Agent Workflows

Portable Agent Workflows is a harness-agnostic workflow layer for coding agents. It defines a shared vocabulary, portable skills, adapter mappings, persistent artifacts, and generated native entrypoints so Codex, OpenCode, Claude Code, Cursor, and similar harnesses can follow the same workflow model without sharing tool names or hidden chat state.

Origins

This model combines the strongest ideas from obra/superpowers and DasDigitaleMomentum/opencode-processing-skills: explicit skill workflows, durable planning artifacts, review gates, handovers, and harness-specific adapters. It does not copy either system directly; it defines a clean agent-work-v1 domain model that can be used across Codex, OpenCode, Claude Code, Cursor, and future harnesses.

What This Repository Is

• A portable workflow and artifact model for coding agents.
• A set of harness-agnostic skills under .agent-work/skills/.
• A generated integration layer for Codex, Claude Code, and Cursor.
• A governance-backed reference repository for agent-work-v1.

What This Repository Is Not

• It is not a runtime library or global installer.
• It is not tied to one agent harness.
• It does not mutate GitHub repository settings automatically.

Public Project Status

Portable Agent Workflows is a public, MIT-licensed, open-source reference model. It is ready for evaluation, issues, and focused pull requests that improve the agent-work-v1 model, documentation, validation, or generated harness entrypoints. The GitHub Community Profile is complete: README, license, contributing guide, Code of Conduct, issue template, pull request template, and contributor content reporting are in place.

The main reader path is this README, then docs/overview.md, then the .agent-work/ source artifacts. docs/superpowers/ records design and planning history; it is kept for transparency, not as the primary product documentation path.

Enterprise Readiness

• PR-first governance is documented in [CONTRIBUTING.md][contributing].
• Security reporting is documented in [SECURITY.md][security].
• Community standards are documented in [CODE_OF_CONDUCT.md][code-of-conduct].
• License terms are published in [LICENSE][license].
• Releases follow the [release policy][release-policy].
• Release history is tracked in [CHANGELOG.md][changelog].
• Compatibility is governed by the [compatibility policy][compatibility-policy].
• Deprecations follow the [deprecation policy][deprecation-policy].
• Recommended repository settings are documented in [GitHub settings][github-settings].
• Supported harnesses are tracked in the [compatibility matrix][compatibility-matrix].