What is OpenFlow?
OpenFlow is an OpenSpec + Superpowers workflow orchestrator that connects requirement specifications with engineering execution, making the entire AI-assisted programming process seamlessly cohesive.
Simply put, it acts as a 'requirements translator,' converting product thinking into engineering-executable steps and then handing them over to AI for execution.
Core Features: Complete the Entire Process with One Set of Commands
| Command | Phase | Capability |
|---|---|---|
/openflow proposal |
proposal | Lightweight questioning, 3-5 questions to quickly converge requirements |
/openflow brainstorming |
brainstorming | Deep design, multi-round solution exploration |
/openflow spec |
spec | Invoke OpenSpec to generate specifications + automatic translation |
/openflow build |
build | Invoke Superpowers to execute implementation |
/openflow close |
close | Verify consistency + archive |
This process covers the complete chain from 'I want to implement a feature' to 'code completion and verification passed'.
Installation and Usage: Get Started with One Command
# Global installation
npm install -g @lininn/openflow
# Initialize project
cd your-project
openflow init --tools claude
The init command will help you:
- Detect and guide installation of OpenSpec CLI
- Detect Superpowers and prompt installation method
- Automatically generate the skills directory within the project
Supports three major AI programming tools: Claude Code, Codex, and Cursor, catering to different team technology stacks.
How Does the Workflow Operate?
User Requirements
|
├── Lightweight ──→ /openflow proposal ──┐
│ 3-5 questions fast convergence |
│ ├─→ proposal.md
└── Deep ──→ /openflow brainstorming ─┘
Multi-round solution exploration
|
┌──────────▼───────────┐
│ /openflow spec │
│ OpenSpec generates specifications │
│ + automatic translation │
└──────────┬───────────┘
|
plan-ready.md
|
┌──────────▼───────────┐
│ /openflow build │
│ Superpowers execution │
│ TDD discipline + checkpoint recovery │
└──────────┬───────────┘
|
┌──────────▼───────────┐
│ /openflow close │
│ Verify consistency + archive │
└──────────────────────┘
The key lies in the translation layer: translating the requirements perspective (features and user experience that product managers care about) into the engineering perspective (tasks, steps, dependencies that developers care about).
Dual-Layer Dependency Assurance: Graceful Degradation
OpenFlow's design philosophy is "Best with, works without":
| Dependency | Best Practice | Fallback When Missing |
|---|---|---|
| OpenSpec | npm install -g @fission-ai/openspec@latest |
Manually create openspec/changes/ directory |
| Superpowers | /plugin install superpowers@claude-plugins-official |
During build phase, manually break down steps from plan-ready.md and execute |
The init command will detect the environment, and runtime will automatically degrade, ensuring the project does not get stuck due to missing dependencies.
Why Do You Need OpenFlow?
- No requirements left behind: Thoroughly discuss requirements via proposal/brainstorming before taking action
- Specifications as code: The specifications generated in the spec phase are directly translated into executable plans
- Execution with guarantee: The build phase follows TDD discipline and can resume if interrupted
- Traceable delivery: The close phase verifies and archives, making every step traceable
Final Thoughts
OpenFlow's positioning is not to replace OpenSpec or Superpowers, but to make them collaborate more closely.
If you are already using Claude Code / Codex / Cursor for AI-assisted programming, why not give OpenFlow a try to make the transition from requirements to code smoother.
GitHub URL: https://github.com/lininn/openflow
This article was collaboratively generated by Claude + OpenFlow
暂无评论。