Loading...
Loading...
Found 23 Skills
Dispatch independent subagents in parallel for unrelated problems spanning different subsystems. Use when 2+ failures have independent root causes, multiple subsystems are broken independently, or user requests concurrent investigation. Use for "parallel", "multiple failures", "independent bugs", "fix these concurrently". Do NOT use for related failures, shared-state problems, or exploratory debugging where root cause is unknown.
Use when dealing with 2 or more tasks that can be performed independently, with no shared state or sequential dependencies
Use when an approved plan exists and needs execution, or when a hotfix/one-sentence scope needs direct TDD implementation — dispatches subagents per task, validates, reports
Plan a non-trivial code change end-to-end — size triage (XS–XL), slicing strategy, optional parallel subagent dispatch, per-slice Implement → Test → Verify → Commit discipline. Use for any multi-file change, refactor across files, executing a planned task from any planning source, cross-cutting modification (analytics sweep / i18n / library migration), or when about to write more than ~100 lines. 也用于增量实现 / 切片落地 / 推进已规划任务 / 跨切面改动。Skip only for trivial XS edits and pure documentation / configuration changes.
Dispatch background AI worker agents to execute tasks via checklist-based plans.
Concurrent investigation of independent failures. Use when multiple unrelated issues need parallel resolution.
Multi-source research synthesis — aggregate and compare 3+ sources or any source >5KB using sub-agent dispatch and SharedState
Track per-agent token usage and flag waste in parallel dispatch. Use after running parallel agents to evaluate cost vs value.
Mandatory orchestrator protocol - establishes ORCHESTRATOR principle (dispatch agents, don't operate directly) and skill discovery workflow for every conversation.
Concurrent investigation pattern - dispatches multiple AI agents to investigate and fix independent problems simultaneously.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies