parallel-task — 병렬 작업 실행 parallel-task, claude-skill-registry, community, 병렬 작업 실행, ide skills, 태스크 종속성 분석, 로그 업데이트, CLI 툴, Python 개발, 태스크 실행 최적화, Claude Code

v1.0.0

이 스킬 정보

효율적인 병렬 작업 실행 및 하위 에이전트 오케스트레이션이 필요한 멀티 태스킹 에이전트에 적합합니다. 병렬 작업 실행기는 태스크 종속성 분석과 로그 업데이트를 통해 태스크를 실행하는 기술입니다

기능

태스크 종속성 분석
로그 업데이트
병렬 작업 실행
CLI 통합
Python 지원

# Core Topics

majiayu000 majiayu000
[0]
[0]
Updated: 2/20/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
65
Canonical Locale
en
Detected Body Locale
en

효율적인 병렬 작업 실행 및 하위 에이전트 오케스트레이션이 필요한 멀티 태스킹 에이전트에 적합합니다. 병렬 작업 실행기는 태스크 종속성 분석과 로그 업데이트를 통해 태스크를 실행하는 기술입니다

이 스킬을 사용하는 이유

에이전트가 계획 파일을 파싱하고, 작업 의존성을 사용하여 병렬 하위 에이전트에게 작업을 위임하고, 올바른 실행 순서를 보장하며, 오케스트레이션 모드를 활용하고, 각 작업 완료 후 작업 루핑 및 의존성 관리와 같은 프로토콜을 사용하여 로그를 업데이트하는 계획 문서를 제공합니다.

최적의 용도

효율적인 병렬 작업 실행 및 하위 에이전트 오케스트레이션이 필요한 멀티 태스킹 에이전트에 적합합니다.

실행 가능한 사용 사례 for parallel-task

복잡한 작업 워크플로우를 위한 하위 에이전트 오케스트레이션
자동 작업 위임을 위한 계획 파일 파싱
의존성 해결을 통한 병렬 작업 실행 관리

! 보안 및 제한 사항

  • 정의된 작업 의존성을 갖는 계획 파일이 필요
  • 하위 에이전트 기반 아키텍처에만 제한
  • 올바른 작업 의존성 구성에 의존

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is parallel-task?

효율적인 병렬 작업 실행 및 하위 에이전트 오케스트레이션이 필요한 멀티 태스킹 에이전트에 적합합니다. 병렬 작업 실행기는 태스크 종속성 분석과 로그 업데이트를 통해 태스크를 실행하는 기술입니다

How do I install parallel-task?

Run the command: npx killer-skills add majiayu000/claude-skill-registry/parallel-task. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for parallel-task?

Key use cases include: 복잡한 작업 워크플로우를 위한 하위 에이전트 오케스트레이션, 자동 작업 위임을 위한 계획 파일 파싱, 의존성 해결을 통한 병렬 작업 실행 관리.

Which IDEs are compatible with parallel-task?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for parallel-task?

정의된 작업 의존성을 갖는 계획 파일이 필요. 하위 에이전트 기반 아키텍처에만 제한. 올바른 작업 의존성 구성에 의존.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add majiayu000/claude-skill-registry/parallel-task. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use parallel-task immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Imported Repository Instructions

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Supporting Evidence

parallel-task

병렬 작업 실행기의 작동 원리와 장점을 살펴보세요. 태스크 종속성 분석과 로그 업데이트 기능을 구현합니다

SKILL.md
Readonly
Imported Repository Instructions
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
Supporting Evidence

Parallel Task Executor

You are an Orchestrator for subagents. Use orchestration mode to parse plan files and delegate tasks to parallel subagents using task dependencies, in a loop, until all tasks are completed. Your role is to ensure that subagents are launched in the correct order (in waves), and that they complete their tasks correctly, as well as ensure the plan docs are updated with logs after each task is completed.

Process

Step 1: Parse Request

Extract from user request:

  1. Plan file: The markdown plan to read
  2. Task subset (optional): Specific task IDs to run

If no subset provided, run the full plan.

Step 2: Read & Parse Plan

  1. Find task subsections (e.g., ### T1: or ### Task 1.1:)
  2. For each task, extract:
    • Task ID and name
    • depends_on list (from - **depends_on**: [...])
    • Full content (description, location, acceptance criteria, validation)
  3. Build task list
  4. If a task subset was requested, filter the task list to only those IDs and their required dependencies.

Step 3: Launch Subagents

For each unblocked task, launch subagent with:

  • description: "Implement task [ID]: [name]"
  • prompt: Use template below

Launch all unblocked tasks in parallel. A task is unblocked if all IDs in its depends_on list are complete.

Task Prompt Template

You are implementing a specific task from a development plan.

## Context
- Plan: [filename]
- Goals: [relevant overview from plan]
- Dependencies: [prerequisites for this task]
- Related tasks: [tasks that depend on or are depended on by this task]
- Constraints: [risks from plan]

## Your Task
**Task [ID]: [Name]**

Location: [File paths]
Description: [Full description]

Acceptance Criteria:
[List from plan]

Validation:
[Tests or verification from plan]

## Instructions
1. Examine working plan and any relevant or dependent files
2. Implement changes for all acceptance criteria
3. Keep work **atomic and committable**
4. For each file: read first, edit carefully, preserve formatting
5. Run validation if feasible
6. **ALWAYS mark completed tasks IN THE *-plan.md file AS SOON AS YOU COMPLETE IT!** and update with:
    - Concise work log
    - Files modified/created
    - Errors or gotchas encountered
7. Commit your work
   - Note: There are other agents working in parallel to you, so only stage and commit the files you worked on. NEVER PUSH. ONLY COMMIT.
8. Double Check that you updated the *-plan.md file and committed your work before yielding
9. Return summary of:
   - Files modified/created
   - Changes made
   - How criteria are satisfied
   - Validation performed or deferred

## Important
- Be careful with paths
- Stop and describe blockers if encountered
- Focus on this specific task

Ensure that the agent marked its task complete before moving on to the next task or set of tasks.

Step 4: Check and Validate.

After a wave of subagents complete their work:

  1. Inspect their outputs for correctness and completeness.
  2. Validate the results against the expected outcomes.
  3. If the task is truly completed correctly, ENSURE THAT TASK WAS MARKED COMPLETE WITH LOGS.
  4. If a task was not successful, have the agent retry or escalate the issue.
  5. Ensure that that wave of work has been committed to github before moving on to the next wave of tasks.

Step 5: Repeat

  1. Review the plan again to see what new set of unblocked tasks are available.
  2. Continue launching unblocked tasks in parallel until plan is done.
  3. Repeat the process until all* tasks are both complete, validated, and working without errors.

Error Handling

  • Task subset not found: List available task IDs
  • Parse failure: Show what was tried, ask for clarification

Example Usage

/parallel-task plan.md
/parallel-task ./plans/auth-plan.md T1 T2 T4
/parallel-task user-profile-plan.md --tasks T3 T7

Execution Summary Template

markdown
1# Execution Summary 2 3## Tasks Assigned: [N] 4 5### Completed 6- Task [ID]: [Name] - [Brief summary] 7 8### Issues 9- Task [ID]: [Name] 10 - Issue: [What went wrong] 11 - Resolution: [How resolved or what's needed] 12 13### Blocked 14- Task [ID]: [Name] 15 - Blocker: [What's preventing completion] 16 - Next Steps: [What needs to happen] 17 18## Overall Status 19[Completion summary] 20 21## Files Modified 22[List of changed files] 23 24## Next Steps 25[Recommendations]

관련 스킬

Looking for an alternative to parallel-task or another community skill for your workflow? Explore these related open-source skills.

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

149.6k
0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

138.4k
0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

98.6k
0
개발자