OpenSpec + Superpowers workflow orchestrator — bridging requirements specs and engineering execution, eliminating the format gap.
npm install -g @lininn/openflowcd your-project
openflow init --tools claudeinit will automatically:
- Detect and guide OpenSpec CLI installation
- Detect Superpowers and show install instructions
- Check if OpenSpec is initialized in the project
- Generate openflow skills to the selected tools' local skill directories, such as
.claude/skills/openflow/,.codex/skills/openflow/,.cursor/skills/openflow/, or.opencode/commands/openflow/
Supported tools: claude, codex, cursor, opencode (comma-separated, e.g. --tools claude,codex)
openflow init --tools claude -g
openflow init --tools claude,codex,cursor,opencode --globalWith -g / --global, openflow installs skills under the selected tools' home directories:
| Tool | Global skill path |
|---|---|
claude |
~/.claude/skills/openflow/ |
codex |
~/.codex/skills/openflow/ |
cursor |
~/.cursor/skills/openflow/ |
opencode |
~/.opencode/commands/openflow/ |
openflow statusShows dependency installation status and active changes in the project.
openflow updateRe-generates project skills after upgrading the npm package.
Canonical usage is /openflow <phase>. For Claude Code, Codex, and Cursor,
openflow also generates visible phase aliases such as /openflow-spec or
$openflow-spec so typing openflow in the command/skill picker surfaces the
available phases. OpenCode keeps its native command-tree form under
/openflow/spec, /openflow/build, and so on.
| Command | Phase | Description |
|---|---|---|
/openflow proposal |
proposal | Lightweight capture — 3-5 questions to converge on requirements |
/openflow brainstorming |
brainstorming | Deep design — multi-round tradeoff exploration |
/openflow grill |
grill | Optional stress-test — challenge proposal assumptions before spec |
/openflow spec |
spec | Call OpenSpec to generate specs + auto-translate to plan-ready.md |
/openflow amend |
amend | Revise requirements/specs before close and update plan-ready.md |
/openflow build |
build | Call Superpowers to execute implementation |
/openflow close |
close | Verify consistency + archive |
/openflow grill is optional: skip it when the proposal is already clear, or use it to challenge hidden assumptions before committing to specs. The spec phase now treats plan-ready.md as a detailed Superpowers handoff, not a task summary: it must preserve source coverage, file responsibilities, implementation slices, TDD expectations, validation commands, and blockers.
Best with: OpenSpec + Superpowers
Works without them: yes, with manual-file fallback
| Dependency | Install | Fallback when missing |
|---|---|---|
| OpenSpec | npm install -g @fission-ai/openspec@latest |
Manually create openspec/changes/ directories and files |
| Superpowers | /plugin install superpowers@claude-plugins-official |
Manually break down plan-ready.md steps in build phase |
| Layer | Mechanism | When missing |
|---|---|---|
| Init time | Detect OpenSpec CLI from PATH; detect project OpenSpec in ./openspec/; detect Superpowers in the selected tools' local/global skill dirs |
Non-blocking, skills still generated |
| Runtime | Dependency check injected into SKILL.md | Build phase falls back to manual step-by-step execution |
Detailed diagrams: Architecture (SVG) | Architecture (PNG) | Workflow (SVG) | Workflow (PNG)
User Requirements
│
├── Quick ──→ /openflow proposal ──┐
│ 3-5 questions │
│ ├─→ proposal.md
└── Deep ───→ /openflow brainstorming ─┘ (openspec/changes/<name>/)
Multi-round exploration
│
┌──────────▼───────────┐
│ /openflow grill │
│ Optional stress-test │
└──────────┬───────────┘
│
┌──────────▼───────────┐
│ /openflow spec │
│ OpenSpec generates │
└──────────┬───────────┘
│
┌──────────▼───────────┐
│ Translation Layer │
│ Requirements → Eng │
└──────────┬───────────┘
│
plan-ready.md
│
┌──────────▼───────────┐
│ /openflow build │
│ Superpowers execution │
│ TDD + checkpoint │
└──────────┬───────────┘
│
┌──────────▼───────────┐
│ /openflow amend │
│ Requirement revision │
│ (only when needed) │
└──────────┬───────────┘
│
┌──────────▼───────────┐
│ /openflow close │
│ Verify + archive │
└──────────────────────┘
openflow orchestrates two open-source projects:
| Project | Repository | License | Usage |
|---|---|---|---|
| OpenSpec | @fission-ai/openspec |
MIT | Generates structured spec files (proposal.md, design.md, specs/, tasks.md). openflow calls its CLI and reads its output format. |
| Superpowers | superpowers plugin |
MIT | Provides writing-plans skill for detailed implementation planning. openflow delegates build-phase execution to its workflow. |
openflow is a standalone orchestrator — it does not bundle, fork, or embed code from either project. Dependencies are detected at init/runtime, with manual fallback when either is not installed.
MIT