with one click
superpowers-openspec-team-skills
superpowers-openspec-team-skills contains 15 collected skills from SYZ-Coder, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Use when the user explicitly wants this workflow, wants Superpowers exploration before OpenSpec artifacts, or is confirming or continuing tasks that this workflow already generated.
Use when the user explicitly wants this workflow, wants Superpowers exploration before OpenSpec artifacts, or is confirming or continuing tasks that this workflow already generated.
Use when the user explicitly wants this workflow, wants Superpowers exploration before OpenSpec artifacts, or is confirming or continuing tasks that this workflow already generated.
Standalone OpenCode workflow for OpenSpec proposal, design, specs, and tasks.
Standalone OpenCode workflow for OpenSpec-first artifacts, then Superpowers implementation planning, TDD, and verification, including follow-up turns that confirm or revise generated tasks.
Standalone OpenCode workflow for clarification, design, planning, TDD, and verification.
Standalone OpenCode workflow for capturing durable project knowledge, current state, session outcomes, and reusable lessons after meaningful work.
Use when a feature needs an OpenSpec change with proposal, design, specs, and tasks completed before coding. Trigger when the repo policy requires OpenSpec for non-trivial features, when the user asks for proposal/design/tasks first, or when behavior changes need durable change artifacts.
Use when the user explicitly wants an OpenSpec-first path that creates proposal, design, specs, and tasks before handing off to Superpowers execution, verification, and optional archive, or when a follow-up turn is confirming or editing tasks that this workflow already generated.
Use when feature work needs the Superpowers stages before or during implementation: brainstorming, design confirmation, implementation planning, worktree setup, test-driven development, and verification. Trigger when the user asks to brainstorm first, wants a plan before coding, or wants disciplined execution with TDD and verification.
Use when the user explicitly wants to capture lessons from completed work, persist durable project knowledge, or turn repeated patterns into reusable learning notes for future sessions.
Standalone Codex workflow for OpenSpec-first artifacts, then Superpowers implementation planning, TDD, and verification, including follow-up turns that confirm or revise generated tasks.
Standalone Codex workflow for capturing durable project knowledge, current state, session outcomes, and reusable lessons after meaningful work.
Standalone Codex workflow for clarification, design, planning, TDD, and verification.
Standalone Codex workflow for OpenSpec proposal, design, specs, and tasks.