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
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

149.6k
0
AI

flags

Logo of vercel
vercel

React フレームワーク

138.4k
0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク(強力なGPUアクセラレーション)

98.6k
0
開発者