菜单
Use when the user runs "/ultrapowers <plan-path>", asks to "execute this plan", "go ultra", or wants an approved plan built autonomously in parallel waves — on the exe.dev fleet, never on this machine.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/popmechanic/ultrapowers --skill ultrapowers命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when writing ANY implementation plan — this plugin's owned authoring skill. Elicits the operator's claim, shapes the decomposition into signed contracts, runs the proof gate, and emits a claims-v1 plan that /ultrapowers compiles into waves. Replaces the marker-layering skill and the external writing-plans dependency for plan bodies.
Use when the operator has a backlog rather than a single idea — triage open issues into a ranked docket, sweep the accepted queue into engine-tagged plans, and drain that queue through an autonomous build. Optional; the single-feature superpowers flow is unchanged when not summoned.
Use when the operator wants to learn from real ultrapowers runs — harvest runs across projects, read them through five lenses, accumulate a redaction-guarded observation ledger, and distill human-gated improvement proposals. Two verbs - "ultralearn" (sense) and "ultralearn distill" (propose).
正在显示 SKILL.md
| name | ultrapowers |
| description | Use when the user runs "/ultrapowers <plan-path>", asks to "execute this plan", "go ultra", or wants an approved plan built autonomously in parallel waves — on the exe.dev fleet, never on this machine. |
| argument-hint | <plan-path> |
| allowed-tools | Skill Read Grep Glob Bash |
This skill is the CLIENT only. Since 0.3.0 there is no LLM engine session:
on the sandbox, the shim spawns the deterministic driver
(node fleet/run-main.mjs → fleet/run-engine.mjs), which runs preflight,
compiles the plan, dispatches judgment agents, folds each wave with the
kernel, gates, and approves — code, not prose. Nothing in this skill runs a
plan locally, and ultra_run.py refuses to (its fleet-run stage).
Selecting ultrapowers at the planning handoff, or invoking /ultrapowers on an
approved plan, is the authorization to execute — no further approval pause.
Commit the plan and push it. Bring the orchestrator's clone to that ref
(fleet/RUNBOOK.md §Live W1 run): drive-one pushes the run's base from
that checkout, and the fitness preflight reads the plan at that ref — never
from your working tree.
Launch on the orchestrator with a fresh run-<N> (run IDs are never
reused):
ssh -n fleet-orchestrator.exe.xyz 'cd /home/exedev/repo && setsid -f node fleet/drive-one.mjs <plan-path> run-<N> </dev/null >/tmp/drive-run-<N>.out 2>&1'
Watch live as a sync peer (fleet/watch.mjs — RUNBOOK §Watch), or tail
the drive log (ssh fleet-orchestrator.exe.xyz 'tail -f /tmp/drive-run-<N>.out').
Read the receipt in the PR the orchestrator opens. Gate-green → a ready PR. Parked → a draft PR carrying the gate receipt: acknowledge by marking it ready, or re-drive a narrower plan. The laptop never fetches a run branch.
Nothing runs here and there is no local fallback: without the fleet, say so and stop.
fleet/run-engine.mjs — the engine (waves, judgments, fold, gate) as code;
fleet/roles/*.md — the judgment prompts, one file per role.references/design-rationale.md — why each surviving guard exists.references/dependency-analysis.md, references/plan-markers.md — plan → waves.references/report-format.md, references/finishing-notes.md — report schema; finishing checks.kernel/FOLD_LOG.md — the fold-log schema (contended-wave state a parked run's evidence carries).scripts/ultra_run.py, scripts/ultra_gate.py, scripts/finalize_report.py,
scripts/gate_check.py, scripts/run_acceptance.sh, scripts/compile_plan.py.