원클릭으로 Manus에서 모든 스킬 실행

multitask

스타205

포크38

업데이트2026년 6월 24일 20:03

Run several tickets to draft PRs at the same time, one isolated worker per ticket. Use when the user passes multiple tickets and wants them worked in parallel. Composes task-to-pr per ticket; never writes code itself.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

owainlewis

owainlewis/blueprint

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

SKILL.md

readonly

name	multitask
description	Run several tickets to draft PRs at the same time, one isolated worker per ticket. Use when the user passes multiple tickets and wants them worked in parallel. Composes task-to-pr per ticket; never writes code itself.
user-invocable	true
argument-hint	<ticket list> e.g. LIN-101, LIN-102, LIN-103

Multitask

Turn a ticket list into draft PRs in parallel. Partition the work, run one worker per lane, report the fleet. Do not edit code directly.

Workflow

Classify independence first. Read each ticket and touched code. Tickets sharing files, schema, or behavioral assumptions go in one sequential lane. Independent tickets get separate lanes. If most overlap, run sequentially and report why.
Isolate each lane: its own worktree, its own branch, one full-session worker. Use the harness's mechanism for parallel workers (subagents, worker threads); when none exists, run the lanes one after another and say so.
Each worker runs task-to-pr for its ticket, end to end.
Monitor. When a lane fails or its outcome changes shared assumptions, stop the lanes that depend on it and report; don't let workers build on a broken premise. Report failures, don't silently retry them.
Report the fleet: every ticket with its branch, PR URL, and status, including stopped and blocked lanes. Clean up worktrees whose PRs are open.

Rules

Cap parallel lanes around five.
Never merge, rebase, or cherry-pick between lanes. One ticket, one branch, one PR.
The coordinator never edits code. Fixes happen inside the lane's worker.
A failed lane is reported, not quietly absorbed into another lane.

이 저장소의 다른 Skills

같은 저장소

plan

owainlewis/blueprint

Break a spec, brief, issue tracker item, or user request into agent-sized tasks, using phases and milestones only when they clarify larger work, delivered to exactly one destination.

2026-06-29205

bootstrap-project

owainlewis/blueprint

Bootstrap a new or empty project repository with a local skeleton: README, license, .gitignore, AGENTS.md, docs, and optional commit or push only when explicit. Interview the repo creator when file-changing decisions are unclear.

2026-06-24205

branch

owainlewis/blueprint

Create a traceable Git branch for the current task.

2026-06-24205

browser-verify

owainlewis/blueprint

Verify browser-rendered work in a real browser. Use for HTML, UI, visual docs, presentations, local apps, and browser-facing changes.

2026-06-24205

commit

owainlewis/blueprint

Stage intended changes and create one Conventional Commit.

2026-06-24205

debug

owainlewis/blueprint

Find and fix the root cause when something breaks: a failing test, a broken build, a bug report, or behavior that doesn't match expectations. Use when the user says 'debug', 'why is this failing', 'fix this bug', or when a failure interrupts other work.

2026-06-24205

name	multitask
description	Run several tickets to draft PRs at the same time, one isolated worker per ticket. Use when the user passes multiple tickets and wants them worked in parallel. Composes task-to-pr per ticket; never writes code itself.
user-invocable	true
argument-hint	<ticket list> e.g. LIN-101, LIN-102, LIN-103

Multitask

Turn a ticket list into draft PRs in parallel. Partition the work, run one worker per lane, report the fleet. Do not edit code directly.

Workflow

Classify independence first. Read each ticket and touched code. Tickets sharing files, schema, or behavioral assumptions go in one sequential lane. Independent tickets get separate lanes. If most overlap, run sequentially and report why.
Isolate each lane: its own worktree, its own branch, one full-session worker. Use the harness's mechanism for parallel workers (subagents, worker threads); when none exists, run the lanes one after another and say so.
Each worker runs task-to-pr for its ticket, end to end.
Monitor. When a lane fails or its outcome changes shared assumptions, stop the lanes that depend on it and report; don't let workers build on a broken premise. Report failures, don't silently retry them.
Report the fleet: every ticket with its branch, PR URL, and status, including stopped and blocked lanes. Clean up worktrees whose PRs are open.

Rules

Cap parallel lanes around five.
Never merge, rebase, or cherry-pick between lanes. One ticket, one branch, one PR.
The coordinator never edits code. Fixes happen inside the lane's worker.
A failed lane is reported, not quietly absorbed into another lane.