Skip to content

lininn/openflow

Repository files navigation

@lininn/openflow

中文文档

OpenSpec + Superpowers workflow orchestrator — bridging requirements specs and engineering execution, eliminating the format gap.

Installation

npm install -g @lininn/openflow

Usage

Initialize a project

cd your-project
openflow init --tools claude

init will automatically:

  1. Detect and guide OpenSpec CLI installation
  2. Detect Superpowers and show install instructions
  3. Check if OpenSpec is initialized in the project
  4. Generate openflow skills to the selected tools' local skill directories, such as .claude/skills/openflow/, .codex/skills/openflow/, or .cursor/skills/openflow/

Supported tools: claude, codex, cursor (comma-separated, e.g. --tools claude,codex)

Install skills globally

openflow init --tools claude -g
openflow init --tools claude,codex,cursor --global

With -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/

Check status

openflow status

Shows dependency installation status and active changes in the project.

Update skills

openflow update

Re-generates project skills after upgrading the npm package.

Workflow Commands

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 spec spec Call OpenSpec to generate specs + auto-translate to plan-ready.md
/openflow build build Call Superpowers to execute implementation
/openflow close close Verify consistency + archive

Dependency Strategy

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

Dual-layer dependency check

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

Architecture

User Requirements
   │
   ├── Quick ──→ /openflow proposal ──┐
   │           3-5 questions          │
   │                                  ├─→ proposal.md
   └── Deep ───→ /openflow brainstorming ─┘ (openspec/changes/<name>/)
               Multi-round exploration
                                     │
                          ┌──────────▼───────────┐
                          │  /openflow spec         │
                          │  OpenSpec generates     │
                          └──────────┬───────────┘
                                     │
                          ┌──────────▼───────────┐
                          │   Translation Layer    │
                          │  Requirements → Eng    │
                          └──────────┬───────────┘
                                     │
                                plan-ready.md
                                     │
                          ┌──────────▼───────────┐
                          │  /openflow build       │
                          │  Superpowers execution │
                          │  TDD + checkpoint      │
                          └──────────┬───────────┘
                                     │
                          ┌──────────▼───────────┐
                          │  /openflow close       │
                          │  Verify + archive      │
                          └──────────────────────┘

Acknowledgments

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.

License

MIT

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors