openspec-executing-plans

Executes Superpowers implementation plans for OpenSpec changes and syncs completed tasks to tasks.md.

3|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/mambo-wang/CodingHub --skill openspec-executing-plans-mambo-wang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-executing-plans
Source: https://github.com/mambo-wang/CodingHub/tree/main/.qoder/skills/openspec-executing-plans
Command: npx skills add https://github.com/mambo-wang/CodingHub --skill openspec-executing-plans-mambo-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an OpenSpec change has Superpowers plan files, developers must manually execute each plan and then reconcile which OpenSpec tasks in tasks.md are actually complete. This Skill automates plan execution and keeps tasks.md synchronized with real progress. ## Core Features & Use Cases - Plan Detection and Execution: Locates Superpowers plan files in docs/superpowers/plans/ matching the change name, then runs them via subagent-driven-development or inline executing-plans. - Task Synchronization: Parses openspec-task annotations across plan files and marks tasks.md entries complete only when all corresponding plan tasks are checked. - Use Case: After writing plans for an add-auth change, run the skill to execute each plan task-by-task with subagent review, then automatically check off completed items in tasks.md and see a progress report. ## Quick Start Ask the assistant to execute the implementation plans for your OpenSpec change, for example by saying run executing-plans for the add-auth change.

Frequently Asked Questions about openspec-executing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute OpenSpec implementation plans with Superpowers?▼

Run the executing-plans command with a change name, such as /opsx:executing-plans add-auth. The skill detects matching plan files in docs/superpowers/plans/ and lets you choose subagent-driven or inline execution for each plan.

How does tasks.md sync work after plan execution?▼

The skill parses openspec-task annotations in plan files and checks whether all steps under each labeled task are marked complete. A tasks.md entry is checked off only when every plan task sharing its label is complete across all plan files.

What happens if Superpowers is not installed?▼

Execution stops with a message suggesting you install Superpowers or use /opsx:apply for direct implementation without plans. Superpowers is a hard dependency for the execution step.

Can I run executing-plans without specifying a change name?▼

Yes. The skill infers the change from conversation context, auto-selects when only one active change exists, or lists available changes via openspec list --json and prompts you to choose when ambiguous.

What happens when only some plan tasks are complete?▼

Partially completed labels are not marked done in tasks.md. The skill reports partial progress, such as 3 of 5 plan tasks complete, and suggests rerunning executing-plans to continue.