openspec-write-plan

Generates Superpowers implementation plans from OpenSpec change artifacts with task mapping.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It bridges the gap between OpenSpec change specifications and Superpowers execution by converting proposal, design, and tasks artifacts into a structured implementation plan with verified task-label mapping. ## Core Features & Use Cases - Artifact-Driven Plan Generation: Loads proposal, design, and tasks files via the openspec CLI and feeds them into the superpowers:writing-plans skill. - Automatic Plan Splitting: Splits large task lists into multiple plan files using a configurable --max-tasks threshold with user confirmation. - Mapping Coverage Verification: Scans generated plans for openspec-task annotations to confirm every OpenSpec task label is covered and valid. - Use Case: After finishing an OpenSpec proposal for a new feature, run this skill to produce dated plan files under docs/superpowers/plans/ ready for execution via /opsx:executing-plans. ## Quick Start Ask the AI to create a Superpowers implementation plan for your current OpenSpec change, optionally specifying the change name and a max-tasks limit.

Frequently Asked Questions about openspec-write-plan

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

FAQPage Schema
How do I create an implementation plan from an OpenSpec change?▼

Run this skill with an optional change name; it loads the proposal, design, and tasks artifacts via the openspec CLI and invokes superpowers:writing-plans to generate a dated plan file under docs/superpowers/plans.

How do I split a large OpenSpec task list into multiple plans?▼

Pass the --max-tasks N option (default 10). When the total task count exceeds the limit, tasks are distributed evenly across groups, keeping same top-level labels together, and you confirm the split before generation.

What happens if Superpowers is not installed?▼

The skill stops and reports that the Superpowers writing-plans skill was not detected. Superpowers is a hard dependency, so no plan files are generated and no fallback approach is attempted.

How are OpenSpec tasks mapped to plan tasks?▼

Each generated plan task must include an openspec-task label comment directly above its heading. After generation, the skill verifies every OpenSpec label is covered and every annotation references a valid label from tasks.md.

Can I execute the plan directly after generation?▼

No, the only supported next step is running /opsx:executing-plans with the change name. The skill deliberately skips the Superpowers execution handoff so progress syncs back to OpenSpec tasks.