openspec-boot

Original：🇺🇸 English
Translated
1 scripts

Use when the user wants to set up spec-driven development (OpenSpec + superpowers-bridge) in a project, or when initializing a new project that needs the SDD workflow. Idempotent. Runs the bundled scripts/run.sh.

10installs
Source9ashwin/openspec-boot
Added on

NPX Install

npx skill4agent add 9ashwin/openspec-boot openspec-boot

Tags

Translated version includes tags in frontmatter
openspec-bootspec-driven-developmentsdd-workflowsuperpowers-bridgecli-tools

SKILL.md Content

View Translation Comparison →

OpenSpec Boot — initialize the SDD workflow in a project

What this skill does

Bootstraps OpenSpec + the 
superpowers-bridge
schema in the current project root, in one call. Concretely:
  1. Runs 
    openspec init
    if no 
    openspec/
    directory exists
  2. Installs the 
    superpowers-bridge
    schema into 
    <project>/openspec/schemas/superpowers-bridge/
    (project-local; user-global is also supported via 
    --user
    but is rarely useful — see WARNING in the script)
  3. Runs 
    openspec schema validate superpowers-bridge
    and 
    openspec schema which superpowers-bridge
  4. Optionally sets 
    superpowers-bridge
    as the project's default schema in 
    openspec/config.yaml
    (so 
    /opsx:new
    no longer needs 
    --schema
    )
  5. Optionally appends the workflow-routing fragment to 
    CLAUDE.md
    or 
    AGENTS.md
  6. Reports 
    obra/superpowers
    plugin / skill availability
The script is idempotent — safe to re-run any time, completed steps are skipped.

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 
    openspec/
    directory and the user is about to do design work
  • The user invokes 
    /opsx:new
    but 
    openspec schemas
    does not list 
    superpowers-bridge
  • The user just cloned a fresh repo and wants the SDD toolchain ready

When NOT to use

  • Inside a subagent dispatched for a specific implementation task
  • Project already has 
    openspec/schemas/superpowers-bridge/
    AND 
    openspec/config.yaml
    with the desired default schema — setup is done, do not re-run unless the user asks
  • The user explicitly wants only 
    spec-driven
    (OpenSpec built-in), not 
    superpowers-bridge
    — in that case just run 
    openspec init
    and stop

How to invoke

The skill bundles a script (
scripts/run.sh
) sitting next to this 
SKILL.md
. Run it from the project root, locating the script via one of its install paths:
bash
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 
openspec-boot
command installed in 
PATH
(via 
install.sh
or manual symlink), prefer the simpler form:
bash
cd <project-root>
openspec-boot "$@"

Common flag combinations

bash
# default: project-local schema, prompts on CLAUDE.md inject + default schema
bash <run.sh>

# automate everything (CI, scripted setup)
bash <run.sh> --inject --default-schema=superpowers-bridge

# skip the CLAUDE.md/AGENTS.md fragment but still set default schema
bash <run.sh> --no-inject

# leave openspec/config.yaml schema field alone
bash <run.sh> --no-default

# explicitly pass --tools to `openspec init` (default: claude when non-interactive)
bash <run.sh> --tools=claude,codex

# preview without doing anything
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.

Preflight (script handles, agent should know)

  • Requires 
    openspec
    CLI on PATH (
    npm i -g @fission-ai/openspec
    if missing — tell the user)
  • Requires 
    git
  • The script runs 
    openspec init
    for the user when 
    openspec/
    is absent

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 run
Otherwise:
bash
/opsx:new my-feature --schema superpowers-bridge

Failure modes

  • openspec CLI not found
    → tell user to 
    npm i -g @fission-ai/openspec
  • Schema validation fails
    → likely OpenSpec CLI version mismatch; suggest CLI upgrade
  • Fragment injection requested but CLAUDE.md / AGENTS.md absent
    → script silently skips; tell user they can re-run with 
    --inject
    after creating one of those files
  • Superpowers not detected
    warning → not blocking; only matters if user plans to use 
    superpowers-bridge
    (Full tier). For 
    spec-driven
    (Lite) no action needed.

Related links