openspec-executing-plans
Use when an OpenSpec change already has one or more Superpowers plan files and implementation should proceed while syncing completed work back to tasks.md.
- License 许可
- MIT
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- openspec-executing-plans
- license
- MIT
- metadata
- { "author": "dyx", "version": "1.0.1" }
- description
- Use when an OpenSpec change already has one or more Superpowers plan files and implementation should proceed while syncing completed work back to tasks.md.
- compatibility
- Requires openspec CLI and Superpowers skills (subagent-driven-development or executing-plans).
03 SKILL.md 正文
Execute Superpowers implementation plans for an OpenSpec change, then sync completed tasks back to tasks.md.
Input: Optionally specify a change name (e.g., /opsx:executing-plans add-auth). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
Steps
-
Select the change
If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a change
- Auto-select if only one active change exists
- If ambiguous, run
openspec list --jsonto get available changes and prompt the user to select
Always announce: "Using change: <name>" and how to override.
-
Check status and load artifacts
openspec status --change '<name>' --jsonRead the change status and locate the tasks file.
-
Detect plan files
Look for Superpowers plan files in
docs/superpowers/plans/. Match files where the change name appears as an exact segment in the filename:*-<change-name>.mdor*-<change-name>-tasks-*.md. Do not match partial prefixes (e.g., changeauthmust not matchauth-v2). -
Decision tree
Plan exists? ├─ YES + Superpowers available → Step 5 (execute) ├─ YES + Superpowers unavailable → STOP: suggest installing Superpowers, or use /opsx:apply for direct implementation ├─ NO + Superpowers available → Ask user: create plan first? │ ├─ Yes → Run /opsx:write-plan logic, then return to Step 3 │ └─ No → STOP: suggest running /opsx:write-plan └─ NO + Superpowers unavailable → STOP: suggest installing Superpowers, or use /opsx:apply for direct implementationSuperpowers detection: Attempt to invoke the Superpowers skill. If the call fails with "skill not found" or similar, treat as unavailable. For other errors (network, timeout, parameter errors), report the actual error to the user instead of silently treating as unavailable.
-
Execute plans via Superpowers
For each plan file (in order if multiple):
- Offer execution choice to user (ask once if multiple plans, with an "apply to all" option):
Plan: <filename> Tasks: N Execution options: 1. Subagent-Driven (recommended) — fresh subagent per task, review between tasks 2. Inline Execution — batch execution with checkpoints Which approach? (applies to all remaining plans if multiple) - Subagent-Driven: invoke
superpowers:subagent-driven-developmentwith the plan file - Inline Execution: invoke
superpowers:executing-planswith the plan file
If the skill call fails (Superpowers not installed): stop and display:
"Superpowers skill not available. Please install Superpowers, or use
/opsx:applyfor direct implementation without plans." - Offer execution choice to user (ask once if multiple plans, with an "apply to all" option):
-
Sync OpenSpec tasks.md
After execution completes (or partially completes):
a. Parse all plan files for this change. For each
<!-- openspec-task: LABEL -->annotation followed by a### Task N:section, record:- The OpenSpec task label (LABEL)
- Whether all steps in that plan task are checked (
[x])
b. Aggregate across files: Group plan tasks by OpenSpec label. A label is "fully complete" only when all plan tasks with that label are checked
[x]across all plan files.c. Update tasks.md: For each fully complete label, find the matching line in tasks.md by exact label match (e.g.,
- [ ] 1.1— label followed by a space, not prefix matching, so1.1does not match1.10) and change- [ ]to- [x].d. Report sync results:
## Task Sync Results Synced to tasks.md: - [x] 1.1 Create index.html - [x] 1.2 Write CSS Still in progress: - [ ] 2.1 Implement data model (3/5 plan tasks complete) Overall: 2/3 OpenSpec tasks completePartial completion: If only some plan tasks under a label are complete, do NOT mark the OpenSpec task as done. Report the partial progress.
-
Show final status
Display:
- Tasks synced this session
- Overall OpenSpec progress
- If all done: suggest
/opsx:verifythen/opsx:archive - If partially done: suggest continuing with
/opsx:executing-plans
Guardrails
- Change names must match
[A-Za-z0-9_-]+— reject any name with spaces, quotes, or special characters before substituting into shell commands - Superpowers is a hard dependency for execution — offer
/opsx:applyas the non-Superpowers alternative - Always sync tasks.md after execution, even if execution was partial
- Never mark an OpenSpec task complete unless ALL corresponding plan tasks are complete
- Do not modify any existing OpenSpec command files or Superpowers files
- Defer to Superpowers skills for git workflow conventions (worktree management, branch lifecycle)
04 同仓库更多 Skills
humanizer-zh
编辑中文文章、评论和文档中的空话、重复及模板化表达,让文字更自然,同时保留事实、确定程度和作者声音。适用于润色已有文本,不用于判断作者身份或保证通过 AI 检测器。
diagram-design
Create branded architecture, architecture delta, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, exploded axonometric, axonometric plan, Venn, pyramid/funnel, treemap and marimekko, heatmap, bar and dumbbell, waterfall, line (slopegraph, ridgeline, streamgraph, bump), Gantt and scatter charts (bubble, beeswarm), high-level, process, medallion, data flow, DP integration, DP security matrix, Sankey, fishbone, Wardley map, kanban, user journey, service blueprint, deployment, dependency graph, UML class, story map, or database schema diagrams as HTML/SVG/PNG, with .drawio, Mermaid, and .excalidraw import, plus lifecycle phase maps, block decomposition trees, and onboarding guidance.
ponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
openspec-write-plan
Use when an OpenSpec change has proposal, design, and tasks artifacts ready and a Superpowers implementation plan needs to be created before execution.
openspec-verify-change
Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".
openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Also use when the user says "openspec update change" or "opsx update". If the user means the openspec update CLI command, which refreshes generated files, run that command instead. Never edits code.