Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vaycentsun/sw-parallel-debugging
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Passed 20 of 21 test cases with the skill, and 15 of 21 without it.
and 4 more in the full report
6 fixed15 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have failing tasks while working on a feature. There is an active plan located at docs/sw-agiledevelopment/plans/feature-auth.md. Should we manually draft parallel sub-agent prompts using custom debugging prompts or route through the plan execution workflow?
| Checked | Without skill | With skill |
|---|---|---|
| Delegates execution to sw-execute-plan rather than manually constructing parallel debugging tasks. | Missed | Passed |
| Explains that structured agile plan files require automated plan-driven dispatch instead of prompt-based parallel debugging. | Passed | Passed |
The instructions your model reads when the skill loads.
你将任务委派给具有隔离上下文的专业 Agent。通过精确设计他们的指令和上下文，确保他们保持专注并成功完成任务。他们不应继承你的会话上下文或历史——你构建他们需要的精确内容。这也为你保留了协调工作的上下文。
当你有多个不相关的失败（不同的测试文件、不同的子系统、不同的 Bug）时，顺序调查会浪费时间。每个调查都是独立的，可以并行发生。
核心原则： 每个独立问题域分派一个 Agent。让他们并发工作。
flowchart TD
A{多个失败？} -->|是| B{它们是独立的吗？}
B -->|否 - 相关| C[sw-systematic-debugging<br/>单个 Agent 调查所有]
B -->|是| D{能并行工作吗？}
D -->|是| E[sw-parallel-debugging<br/>并行分派]
D -->|否 - 共享状态| F[sw-systematic-debugging<br/>顺序调查]
使用时机：
不要使用：
两者都涉及并行分派 Agent，但使用场景完全不同：
| 维度 | sw-parallel-debugging（本技能） | sw-subagent-development |
|---|---|---|
| 触发方式 | 用户直接触发，面对突发问题 | 被 sw-execute-plan 内部调用，有计划 |
| 是否有计划 | 无结构化计划，问题刚暴露 | 有书面实施计划，任务已定义 |
test cases passed, vs 15 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.