owainlewis/multitask
skills/multitask/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add owainlewis/blueprint multitaskInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 12, 2026, 7:27 AM113.2s1 file scanned
SKILL.md
- 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 list of tickets into draft PRs in parallel. You are the coordinator: partition the work, run one worker per lane, report the fleet. You never write code yourself.
Workflow
- Classify independence first. Read each ticket and the code it touches. Tickets that share files, schema, or behavioral assumptions overlap: group them into one sequential lane. Truly independent tickets get their own lanes. If most of the tickets overlap, say so and run them sequentially; parallelism is not worth the coordination cost.
- 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-prfor 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. The bottleneck is human review of the resulting PRs, not the workers.
- 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.
Related Skills
owainlewis/pr
tools
VerifiedTrustedCommunity
Commit, push, and open a pull request with a clear description. Use when finished work on the current branch needs to become a PR.
143SKILL.mdUpdated Jun 12, 2026
owainlewis/task-to-pr
development
VerifiedTrustedCommunity
Turn one ticket into a draft PR. Use when the user passes a ticket reference (JIRA-123, LIN-123, github#456, an issue URL) and expects code, tests, review, and a PR. Use implement when no PR is expected; use multitask for several tickets at once.
143SKILL.mdUpdated Jun 11, 2026
owainlewis/implement
development
VerifiedTrustedCommunity
Turn one scoped task into a verified diff: code, tests, verification, report. The inner build step of the delivery flow. Use directly when the workspace is prepared and no PR is expected; use task-to-pr when a ticket should become a PR.
143SKILL.mdUpdated May 10, 2026
owainlewis/branch
tools
VerifiedTrustedCommunity
Create a traceable Git branch for the current task.
143SKILL.mdUpdated May 10, 2026