[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-82057":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":8,"htmlUrl":8,"language":9,"languages":8,"totalLinesOfCode":8,"stars":10,"forks":11,"watchers":12,"openIssues":13,"contributorsCount":13,"subscribersCount":13,"size":13,"stars1d":14,"stars7d":15,"stars30d":15,"stars90d":13,"forks30d":13,"starsTrendScore":12,"compositeScore":16,"rankGlobal":8,"rankLanguage":8,"license":17,"archived":18,"fork":18,"defaultBranch":19,"hasWiki":20,"hasPages":18,"topics":21,"createdAt":8,"pushedAt":8,"updatedAt":22,"readmeContent":23,"aiSummary":24,"trendingCount":13,"starSnapshotCount":13,"syncStatus":25,"lastSyncTime":26,"discoverSource":27},82057,"openflow","lininn\u002Fopenflow","lininn",null,"HTML",33,6,21,0,7,12,60.74,"MIT License",false,"main",true,[],"2026-06-12 04:01:37","# @lininn\u002Fopenflow\n\n[中文文档](.\u002FREADME.zh-CN.md)\n\nOpenSpec + Superpowers workflow orchestrator — bridging requirements specs and engineering execution, eliminating the format gap.\n\n## Installation\n\n```bash\nnpm install -g @lininn\u002Fopenflow\n```\n\n## Usage\n\n### Initialize a project\n\n```bash\ncd your-project\nopenflow init --tools claude\n```\n\n`init` will automatically:\n1. Detect and guide OpenSpec CLI installation\n2. Detect Superpowers and show install instructions\n3. Check if OpenSpec is initialized in the project\n4. Generate openflow skills to the selected tools' local skill directories, such as `.claude\u002Fskills\u002Fopenflow\u002F`, `.codex\u002Fskills\u002Fopenflow\u002F`, `.cursor\u002Fskills\u002Fopenflow\u002F`, or `.opencode\u002Fcommands\u002Fopenflow\u002F`\n\nSupported tools: `claude`, `codex`, `cursor`, `opencode` (comma-separated, e.g. `--tools claude,codex`)\n\n### Install skills globally\n\n```bash\nopenflow init --tools claude -g\nopenflow init --tools claude,codex,cursor,opencode --global\n```\n\nWith `-g` \u002F `--global`, `openflow` installs skills under the selected tools' home directories:\n\n| Tool | Global skill path |\n|------|-------------------|\n| `claude` | `~\u002F.claude\u002Fskills\u002Fopenflow\u002F` |\n| `codex` | `~\u002F.codex\u002Fskills\u002Fopenflow\u002F` |\n| `cursor` | `~\u002F.cursor\u002Fskills\u002Fopenflow\u002F` |\n| `opencode` | `~\u002F.opencode\u002Fcommands\u002Fopenflow\u002F` |\n\n### Check status\n\n```bash\nopenflow status\n```\n\nShows dependency installation status and active changes in the project.\n\n### Update skills\n\n```bash\nopenflow update\n```\n\nRe-generates project skills after upgrading the npm package.\n\n## Workflow Commands\n\nCanonical usage is `\u002Fopenflow \u003Cphase>`. For Claude Code, Codex, and Cursor,\n`openflow` also generates visible phase aliases such as `\u002Fopenflow-spec` or\n`$openflow-spec` so typing `openflow` in the command\u002Fskill picker surfaces the\navailable phases. OpenCode keeps its native command-tree form under\n`\u002Fopenflow\u002Fspec`, `\u002Fopenflow\u002Fbuild`, and so on.\n\n| Command | Phase | Description |\n|---------|-------|-------------|\n| `\u002Fopenflow proposal` | proposal | Lightweight capture — 3-5 questions to converge on requirements |\n| `\u002Fopenflow brainstorming` | brainstorming | Deep design — multi-round tradeoff exploration |\n| `\u002Fopenflow spec` | spec | Call OpenSpec to generate specs + auto-translate to plan-ready.md |\n| `\u002Fopenflow amend` | amend | Revise requirements\u002Fspecs before close and update plan-ready.md |\n| `\u002Fopenflow build` | build | Call Superpowers to execute implementation |\n| `\u002Fopenflow close` | close | Verify consistency + archive |\n\n## Dependency Strategy\n\n```\nBest with: OpenSpec + Superpowers\nWorks without them: yes, with manual-file fallback\n```\n\n| Dependency | Install | Fallback when missing |\n|------------|---------|----------------------|\n| OpenSpec | `npm install -g @fission-ai\u002Fopenspec@latest` | Manually create `openspec\u002Fchanges\u002F` directories and files |\n| Superpowers | `\u002Fplugin install superpowers@claude-plugins-official` | Manually break down plan-ready.md steps in build phase |\n\n### Dual-layer dependency check\n\n| Layer | Mechanism | When missing |\n|-------|-----------|-------------|\n| **Init time** | Detect OpenSpec CLI from `PATH`; detect project OpenSpec in `.\u002Fopenspec\u002F`; detect Superpowers in the selected tools' local\u002Fglobal skill dirs | Non-blocking, skills still generated |\n| **Runtime** | Dependency check injected into SKILL.md | Build phase falls back to manual step-by-step execution |\n\n## Architecture\n\n```\nUser Requirements\n   │\n   ├── Quick ──→ \u002Fopenflow proposal ──┐\n   │           3-5 questions          │\n   │                                  ├─→ proposal.md\n   └── Deep ───→ \u002Fopenflow brainstorming ─┘ (openspec\u002Fchanges\u002F\u003Cname>\u002F)\n               Multi-round exploration\n                                     │\n                          ┌──────────▼───────────┐\n                          │  \u002Fopenflow spec         │\n                          │  OpenSpec generates     │\n                          └──────────┬───────────┘\n                                     │\n                          ┌──────────▼───────────┐\n                          │   Translation Layer    │\n                          │  Requirements → Eng    │\n                          └──────────┬───────────┘\n                                     │\n                                plan-ready.md\n                                     │\n                          ┌──────────▼───────────┐\n                          │  \u002Fopenflow build       │\n                          │  Superpowers execution │\n                          │  TDD + checkpoint      │\n                          └──────────┬───────────┘\n                                     │\n                          ┌──────────▼───────────┐\n                          │  \u002Fopenflow amend       │\n                          │  Requirement revision  │\n                          │  (only when needed)    │\n                          └──────────┬───────────┘\n                                     │\n                          ┌──────────▼───────────┐\n                          │  \u002Fopenflow close       │\n                          │  Verify + archive      │\n                          └──────────────────────┘\n```\n\n## Acknowledgments\n\nopenflow orchestrates two open-source projects:\n\n| Project | Repository | License | Usage |\n|---------|-----------|---------|-------|\n| [OpenSpec](https:\u002F\u002Fgithub.com\u002FFission-AI\u002FOpenSpec) | `@fission-ai\u002Fopenspec` | MIT | Generates structured spec files (proposal.md, design.md, specs\u002F, tasks.md). openflow calls its CLI and reads its output format. |\n| [Superpowers](https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers) | `superpowers` plugin | MIT | Provides `writing-plans` skill for detailed implementation planning. openflow delegates build-phase execution to its workflow. |\n\nopenflow is a **standalone orchestrator** — it does not bundle, fork, or embed code from either project. Dependencies are detected at init\u002Fruntime, with manual fallback when either is not installed.\n\n## License\n\nMIT\n","@lininn\u002Fopenflow 是一个基于 TypeScript 的工作流编排工具，旨在通过连接需求规范和工程执行来消除格式差距。其核心功能包括初始化项目、安装技能、检查状态及更新技能等，并支持多种开发工具如 Claude, Codex, Cursor 和 OpenCode。它能够自动检测并引导 OpenSpec CLI 的安装，同时为选定的工具生成相应的技能目录。适用于需要将需求文档与实际编码过程紧密结合的软件开发场景中，尤其是那些已经在使用或计划采用 OpenSpec 与 Superpowers 工具链的团队。即使在缺少这些依赖的情况下，也能通过手动创建文件的方式继续运行，保证了项目的灵活性与兼容性。",2,"2026-06-11 04:07:37","CREATED_QUERY"]