사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/pwguler/skills --skill parallel시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Run parallel work only when the user asks for it. Otherwise, run the tasks one at a time in this session. The independence of the tasks is the guarantee. Parallel runs are only the cheap way to get it.
- Choose the mode. Partition is the default: independent tasks that share no files or state, with one subagent for each task. Race is several full attempts at one task, as race.md says. Coverage is many parts of one job with a done check, as coverage.md says. Related failures fit no mode. Investigate them together first.
- For a race or a coverage run, state the cost first: how many subagents, and how many full attempts. Launch only after the user agrees.
- For partition, give each worker a brief with its scope, context, constraints, and expected return. The scope is one file, one subsystem, or one problem. "Fix all the tests" is too wide for an agent. Paste the context into the brief: error messages, test names, and relevant paths. Agents get nothing from the session. The constraints say what must not change, such as "tests only" or "do not touch production code". The expected return is a summary of the root cause and the changes, so that you can review the integration.
- Launch all the subagents at the same time. Run each worker that edits files in its own git worktree, so that no two workers share a checkout. A new worktree holds only committed files, so start the workers from a clean checkout.
- Integrate the results when they return. A worker in a worktree gives its changes back as a patch or a branch, not in this checkout. Read each summary. Apply each patch with
git apply --3way, or merge each branch. Resolve any conflict by intent. Then run theverifyskill before you say that the batch is done. Its full gate covers the suite.
Rules:
- Partition does not fit in three cases. The failures are related, so a fix for one can fix the others. The cause of the problem is still unknown. Or the agents would touch the same files.
- A race never averages different designs. When the attempts differ in shape, the brief was too loose. Rewrite it. A coverage run never starts without a done check.
- The worktree and branch of a worker stay after the run, so that the worker can continue. When the batch passes
verify, offer to remove them. Remove them only after the user agrees.
