Skip to content
Back to skills

Aetox Parallel

ASecurity

ตอนมีปัญหาอิสระตั้งแต่สองเรื่องขึ้นไป เช่น เทสต์หลายไฟล์พังคนละสาเหตุ หรือระบบย่อยหลายตัวเสียโดยไม่เกี่ยวกัน

  • 46 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
ai-agentsgogitdatabase

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add Mikedev115/Aetox --skill aetox-parallel --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Aetox Parallel?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Aetox Parallel
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mikedev115-aetox-parallel/badge)](https://www.skillsdirectory.com/skills/mikedev115-aetox-parallel)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: aetox-parallel
before: handing two or more independent problems to subagents at the same time, such as several failing test files with different causes
description: ตอนมีปัญหาอิสระตั้งแต่สองเรื่องขึ้นไป เช่น เทสต์หลายไฟล์พังคนละสาเหตุ หรือระบบย่อยหลายตัวเสียโดยไม่เกี่ยวกัน
source: https://github.com/obra/superpowers (dispatching-parallel-agents), adapted
license: MIT
copyright: Copyright (c) 2026 Aetox Skills
---

# Aetox Parallel

One subagent per independent problem, all at once. Investigating three
unrelated failures in sequence spends three times the wall clock and drags
the first problem's context into the third.

## Is it independent

Parallel only when every one of these holds:

- Each problem can be understood without the others. A fix in one cannot
  change the outcome of another.
- No shared state: not the same files, not the same database, not the same
  running process.
- The whole system's state does not need to be held in one head to solve
  any of them.

Related failures, where fixing one might fix the rest, are one problem for
one agent. Two agents that would edit the same file are one agent.

## The brief each one gets

Focused, self-contained, specific about the return:

- Scope: one test file, one subsystem, one bug. Named.
- Goal: what "done" is, as the command that proves it.
- Constraints: do not change code outside the scope; do not touch the
  others' files; report, do not commit, unless told to.
- Return: what was found, what was changed, what the verification said.

All the context the agent needs is in the brief. It has no conversation to
read.

## Dispatch and integrate

Dispatch every one in the same turn; one per turn is sequential, whatever
it was called. When they return: read each report, check that the changes
do not conflict, run the full suite once on the combined result, and only
then call any of it fixed. A report that says "should work" is a report
without evidence; run it.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…