openspec-superpower-orchestrationlisted

# OpenSpec Superpower Orchestration ## Overview This skill is the orchestration entrypoint for formal change work that uses `OpenSpec` plus superpower skills. Use it when generic skill defaults are too local or too phase-specific, and you need one workflow that coordinates exploration, formal artifacts, implementation, review, and verification without creating a second source of truth. Its purpose is to improve workflow quality: keep sequencing stable, reduce process loops, and ensure `OpenSpec` artifacts and superpower discipline layers work together instead of competing. ## When to Use - New feature, bugfix, refactor, or behavior change - Formal changes that alter business capability, user-visible flows, API or protocol contracts, state semantics, cross-module architecture, or persisted data shape - The work needs `proposal`, `design`, `spec`, `tasks`, or implementation orchestration - Multiple skills may apply, but they need one ordering discipline - You want `OpenSpec` artifacts to remain the only formal source of truth Do not use for: - Tiny one-off answers with no formal change - Pure explanation work with no artifact or implementation follow-up - Local implementation-only improvements that do not change requirement semantics, such as style tweaks, component splitting, memo/render-boundary optimization, image preloading, computed-value caching, test coverage hardening, or performance bugfixes with no user-visible behavior change ## Dependencies This skill depe