openspec-boot
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseOpenSpec Boot — initialize the SDD workflow in a project
OpenSpec Boot — 在项目中初始化SDD工作流
What this skill does
该技能的作用
Bootstraps OpenSpec + the schema in the current project
root, in one call. Concretely:
superpowers-bridge- Runs if no
openspec initdirectory existsopenspec/ - Installs the schema into
superpowers-bridge(project-local; user-global is also supported via<project>/openspec/schemas/superpowers-bridge/but is rarely useful — see WARNING in the script)--user - Runs and
openspec schema validate superpowers-bridgeopenspec schema which superpowers-bridge - Optionally sets as the project's default schema in
superpowers-bridge(soopenspec/config.yamlno longer needs/opsx:new)--schema - Optionally appends the workflow-routing fragment to or
CLAUDE.mdAGENTS.md - Reports plugin / skill availability
obra/superpowers
The script is idempotent — safe to re-run any time, completed steps are skipped.
通过一次调用,在当前项目根目录中快速搭建OpenSpec + 架构。具体包括:
superpowers-bridge- 若不存在 目录,则运行
openspec/openspec init - 将 架构安装到
superpowers-bridge(项目本地模式;也支持通过<project>/openspec/schemas/superpowers-bridge/参数使用用户全局模式,但实用性极低——详见脚本中的警告)--user - 运行 和
openspec schema validate superpowers-bridgeopenspec schema which superpowers-bridge - 可选择在 中将
openspec/config.yaml设置为项目默认架构(这样superpowers-bridge命令就无需再添加/opsx:new参数)--schema - 可选择将工作流路由片段追加到 或
CLAUDE.md文件中AGENTS.md - 报告 插件/技能的可用情况
obra/superpowers
该脚本具有幂等性——可随时安全重新运行,已完成的步骤会被跳过。
When to use
使用场景
Trigger when the user says any of (English / Chinese):
- "set up SDD for this project" / "configure spec-driven workflow"
- "init openspec" / "initialize openspec" / "装一下 openspec"
- "add the SDD workflow to this repo" / "给这个仓库加上 SDD 工作流"
- "我要用 superpowers-bridge"
Or when you observe:
- The project has no directory and the user is about to do design work
openspec/ - The user invokes but
/opsx:newdoes not listopenspec schemassuperpowers-bridge - The user just cloned a fresh repo and wants the SDD toolchain ready
当用户说出以下任意语句(英文/中文)时触发:
- "set up SDD for this project" / "配置规范驱动工作流"
- "init openspec" / "initialize openspec" / "装一下 openspec"
- "add the SDD workflow to this repo" / "给这个仓库加上 SDD 工作流"
- "我要用 superpowers-bridge"
或是观察到以下情况时:
- 项目没有 目录,且用户即将开展设计工作
openspec/ - 用户调用 命令,但
/opsx:new列表中没有openspec schemassuperpowers-bridge - 用户刚克隆了一个全新仓库,希望SDD工具链准备就绪
When NOT to use
禁用场景
- Inside a subagent dispatched for a specific implementation task
- Project already has AND
openspec/schemas/superpowers-bridge/with the desired default schema — setup is done, do not re-run unless the user asksopenspec/config.yaml - The user explicitly wants only (OpenSpec built-in), not
spec-driven— in that case just runsuperpowers-bridgeand stopopenspec init
- 在为特定实现任务调度的子Agent中
- 项目已存在 且
openspec/schemas/superpowers-bridge/已设置好所需的默认架构——配置已完成,除非用户要求,否则不要重新运行openspec/config.yaml - 用户明确只需要内置的 (而非
spec-driven)——这种情况下只需运行superpowers-bridge即可停止openspec init
How to invoke
调用方式
The skill bundles a script () sitting next to this .
Run it from the project root, locating the script via one of its install paths:
scripts/run.shSKILL.mdbash
cd <project-root>
SCRIPT=""
for c in ~/.claude/skills/openspec-boot/scripts/run.sh \
~/.agents/skills/openspec-boot/scripts/run.sh \
~/.codex/openspec-boot/skills/openspec-boot/scripts/run.sh \
~/.openspec-boot/skills/openspec-boot/scripts/run.sh; do
[ -x "$c" ] && SCRIPT="$c" && break
done
[ -n "$SCRIPT" ] || { echo "openspec-boot script not found"; exit 1; }
bash "$SCRIPT" "$@"If the user has the command installed in (via
or manual symlink), prefer the simpler form:
openspec-bootPATHinstall.shbash
cd <project-root>
openspec-boot "$@"该技能捆绑了一个脚本(),与本 文件同级。从项目根目录运行脚本,可通过以下安装路径之一找到它:
scripts/run.shSKILL.mdbash
cd <project-root>
SCRIPT=""
for c in ~/.claude/skills/openspec-boot/scripts/run.sh \
~/.agents/skills/openspec-boot/scripts/run.sh \
~/.codex/openspec-boot/skills/openspec-boot/scripts/run.sh \
~/.openspec-boot/skills/openspec-boot/scripts/run.sh; do
[ -x "$c" ] && SCRIPT="$c" && break
done
[ -n "$SCRIPT" ] || { echo "openspec-boot script not found"; exit 1; }
bash "$SCRIPT" "$@"如果用户已通过 或手动链接将 命令安装到 中,优先使用更简洁的形式:
install.shopenspec-bootPATHbash
cd <project-root>
openspec-boot "$@"Common flag combinations
常用参数组合
bash
undefinedbash
undefineddefault: project-local schema, prompts on CLAUDE.md inject + default schema
默认:项目本地架构,对CLAUDE.md注入和默认架构进行提示
bash <run.sh>
bash <run.sh>
automate everything (CI, scripted setup)
自动化所有操作(CI、脚本化配置)
bash <run.sh> --inject --default-schema=superpowers-bridge
bash <run.sh> --inject --default-schema=superpowers-bridge
skip the CLAUDE.md/AGENTS.md fragment but still set default schema
跳过CLAUDE.md/AGENTS.md片段注入,但仍设置默认架构
bash <run.sh> --no-inject
bash <run.sh> --no-inject
leave openspec/config.yaml schema field alone
不修改openspec/config.yaml中的架构字段
bash <run.sh> --no-default
bash <run.sh> --no-default
explicitly pass --tools to openspec init
(default: claude when non-interactive)
openspec init显式向openspec init
传递--tools参数(默认:非交互式时为claude)
openspec initbash <run.sh> --tools=claude,codex
bash <run.sh> --tools=claude,codex
preview without doing anything
预览操作但不执行任何实际修改
bash <run.sh> --dry-run
bash <run.sh> --dry-run
refresh the cached schemas source (one-time per machine, not per project)
刷新缓存的架构源(每台机器一次,而非每个项目)
bash <run.sh> --update
Pass any of these to the script. The script prints `--help` for the full list.bash <run.sh> --update
可将上述任意参数传递给脚本。运行脚本时添加 `--help` 可查看完整参数列表。Preflight (script handles, agent should know)
预检查(脚本自动处理,Agent需知晓)
- Requires CLI on PATH (
openspecif missing — tell the user)npm i -g @fission-ai/openspec - Requires
git - The script runs for the user when
openspec initis absentopenspec/
- 需要在PATH中配置 CLI(若缺失,告知用户执行
openspec)npm i -g @fission-ai/openspec - 需要安装
git - 当 目录不存在时,脚本会自动为用户运行
openspec/openspec init
After bootstrap, in a project
项目完成初始化后
If the user accepted the default-schema prompt:
bash
/opsx:new my-feature # uses superpowers-bridge by default
/opsx:new my-feature --schema spec-driven # opt-out for a lighter runOtherwise:
bash
/opsx:new my-feature --schema superpowers-bridge如果用户接受了默认架构提示:
bash
/opsx:new my-feature # 默认使用superpowers-bridge
/opsx:new my-feature --schema spec-driven # 选择使用轻量版模式若未设置默认架构:
bash
/opsx:new my-feature --schema superpowers-bridgeFailure modes
故障排查
- → tell user to
openspec CLI not foundnpm i -g @fission-ai/openspec - → likely OpenSpec CLI version mismatch; suggest CLI upgrade
Schema validation fails - → script silently skips; tell user they can re-run with
Fragment injection requested but CLAUDE.md / AGENTS.md absentafter creating one of those files--inject - warning → not blocking; only matters if user plans to use
Superpowers not detected(Full tier). Forsuperpowers-bridge(Lite) no action needed.spec-driven
- → 告知用户执行
openspec CLI not foundnpm i -g @fission-ai/openspec - → 可能是OpenSpec CLI版本不匹配;建议升级CLI
Schema validation fails - → 脚本会静默跳过;告知用户创建上述任一文件后可重新运行并添加
Fragment injection requested but CLAUDE.md / AGENTS.md absent参数--inject - 警告 → 不影响核心功能;仅当用户计划使用
Superpowers not detected(完整版)时需要处理。若使用superpowers-bridge(轻量版)则无需操作。spec-driven
Related links
相关链接
- : https://github.com/obra/superpowers
obra/superpowers - : https://github.com/JiangWay/openspec-schemas/tree/main/superpowers-bridge
superpowers-bridge - OpenSpec CLI: https://github.com/Fission-AI/OpenSpec
- OPSX workflow guide: https://github.com/Fission-AI/OpenSpec/blob/main/docs/opsx.md
- Why default to project-local instead of user-global: see this skill's §"Why not user-global?"
README.md
- : https://github.com/obra/superpowers
obra/superpowers - : https://github.com/JiangWay/openspec-schemas/tree/main/superpowers-bridge
superpowers-bridge - OpenSpec CLI: https://github.com/Fission-AI/OpenSpec
- OPSX工作流指南: https://github.com/Fission-AI/OpenSpec/blob/main/docs/opsx.md
- 为何默认使用项目本地模式而非用户全局模式:详见本技能的 中「Why not user-global?」章节
README.md