scoped-superpowers

Routes project tasks to scoped workflow references based on size and risk.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/kangjuhyup/study --skill scoped-superpowers-kangjuhyup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scoped-superpowers
Source: https://github.com/kangjuhyup/study/tree/main/scoped-superpowers-ab/fixture/workflow
Command: npx skills add https://github.com/kangjuhyup/study --skill scoped-superpowers-kangjuhyup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Loading an entire workflow framework for every task wastes context and adds process overhead, while skipping structure entirely on large or risky work leads to missed verification steps. This Skill classifies each task by scope and risk, then loads at most one relevant workflow reference for the current phase. ## Core Features & Use Cases - Scope-Based Routing: Classifies work as small, medium, large, or high-risk using uncertainty, blast radius, reversibility, and operational risk, then selects only the workflow reference that phase requires. - Parallelism Gate: Detects two or more independent workstreams with no shared state or dependencies and dispatches focused parallel agents with defined goals, scopes, and handoff formats. - Phase-Appropriate Verification: Routes completion claims through a verification-before-completion reference that demands fresh, scope-appropriate evidence for medium, large, or high-risk changes. - Use Case: When asked to fix a flaky test and refactor an authentication module, the router treats the auth change as high-risk, loads the systematic debugging reference for the flaky test, and dispatches parallel agents only if the workstreams are truly independent. ## Quick Start Ask the assistant to handle a medium or large development task using scoped workflow routing so only the relevant phase guidance is loaded.

Frequently Asked Questions about scoped-superpowers

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

FAQPage Schema
How do I choose the right workflow for a coding task?

Classify the task by uncertainty, blast radius, reversibility, and operational risk rather than file count alone. Small obvious changes need no workflow reference, medium tasks load at most one phase reference, and large or high-risk work starts with planning before selecting phase-specific guidance.

When should I dispatch parallel agents for a development task?

Dispatch parallel agents only when at least two concrete workstreams have distinct goals, no shared files or mutable state, no dependency on each other's unfinished results, and enough substance to outweigh coordination overhead. Never split a small task into microtasks just to create parallel work.

Does this workflow router require a Superpowers plugin installation?

No, the skill is self-contained and bundles its own adapted workflow references derived from Superpowers 6.3.0. It does not require a separately installed Superpowers plugin to function.

When should I skip loading a workflow reference entirely?

Skip workflow references for simple questions, status checks, file lookups, localized routine edits, obvious typos, and routine commits. Selecting no workflow is a valid outcome, and small changes only need the smallest meaningful direct verification.

What evidence is required before claiming a task is complete?

Identify the command or inspection that proves each completion claim, run it fresh after the last relevant change, and confirm exit status and failure counts. Prior runs, code review, or another agent's success report do not substitute for fresh verification.