spark-workflow

Orchestrate OpenSpec workflows with Superpowers gates and artifact-based progress.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Miss-PinkElf/Multi-Agent --skill spark-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spark-workflow
Source: https://github.com/Miss-PinkElf/Multi-Agent/tree/main/.claude/skills/spark-workflow
Command: npx skills add https://github.com/Miss-PinkElf/Multi-Agent --skill spark-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured OpenSpec workflow orchestration with integrated Superpowers gates to ensure deliberate planning, alignment, and verification before delivering changes.

Core Features & Use Cases

  • Orchestrates the OpenSpec lifecycle for frontend or product-facing work across small tweaks to whole new modules, ensuring alignment, gate checks, and artifact-driven progress.
  • Acts as a single orchestrator for planning, alignment, proposal, apply, review, and archiving while guiding through light and standard path routing.
  • Integrates with brain storming, OpenSpec proposals, systematic debugging, code-review gates, and verification to ensure robust delivery.

Quick Start

Begin with Classify to decide path, then proceed through Align, Propose, Apply, Review/Verify, and Archive as appropriate.

Frequently Asked Questions about spark-workflow

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

FAQPage Schema
How do I enforce verification and alignment gates during an OpenSpec workflow?

An OpenSpec workflow with quality gates ensures deliberate planning by enforcing artifact-based progress through proposal.md, design.md, and tasks.md, routing changes through alignment, proposal, and verification stages before completion.

How do I plan and route product-facing changes using a structured workflow?

You plan and route product-facing changes by classifying the work to select a light or standard path, then advancing through align, propose, apply, review, and archive stages to ensure robust delivery.

How do I link artifacts like proposal.md and tasks.md to track workflow progress?

To link artifacts like proposal.md, design.md, and tasks.md to track workflow progress, you enforce artifact-based progress checks that route changes through systematic debugging and code review before deployment.

What is the best way to integrate systematic debugging and code review into a planning workflow?

Integrating systematic debugging and code review into a planning workflow requires a single orchestrator that enforces these tasks as quality gates, ensuring alignment and verification before deploying changes.

Can I use this workflow orchestration for small tweaks or is it only for whole new modules?

This workflow orchestration supports both small tweaks and whole new modules by classifying the work scale upfront and routing the process through appropriate light or standard paths with defined gates.