Skip to content
Skills Library
Programming · Planning

parallel-task-design

/parallel-task-design

Break a multi-part engineering task into safely parallel work units with clear ownership and integration points. Use when several agents or contributors can work concurrently.

Licence
MIT
Last repository change
30.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Break a multi-part engineering task into safely parallel work units with clear ownership and integration points. Use when several agents or contributors can work concurrently.

Original author description

Break a multi-part engineering task into safely parallel work units with clear ownership and integration points. Use when several agents or contributors can work concurrently.

How it works

  1. Procedure
  2. Deliverable
  3. Boundaries
Original SKILL.md headings · 20 lines, 200 words
SKILL.md preview
---
name: parallel-task-design
description: Break a multi-part engineering task into safely parallel work units with clear ownership and integration points. Use when several agents or contributors can work concurrently.
license: MIT
---

# Parallel Task Design

## Procedure
1. Map the requested outcome, shared files, dependencies, sequence constraints, and final integration tests.
2. Split work by independent deliverable or subsystem rather than by arbitrary file count. Each task needs a clear owner, boundaries, input assumptions, and completion criteria.
3. Identify conflicts: shared manifests, lockfiles, global types, generated code, schemas, snapshots, config, and common abstractions.
4. Establish contracts before parallel implementation. Agree on names, interfaces, types, file ownership, and fixture formats early.
5. Keep dependent tasks sequential. Parallelize independent research/tests/docs only when their results will not be invalidated by upstream decisions.
6. Ask each contributor to report touched files, decisions, commands/tests run, unresolved assumptions, and any edits made outside their scope.
7. Integrate one workstream at a time. Inspect the combined diff, reconcile contradictions, run cross-workstream tests, and remove duplicate or abandoned code.

## Deliverable
Workstream table with owner, input, scope, files/contracts, acceptance criteria, dependencies, and integration test.

## Boundaries
- Do not have multiple agents edit the same file concurrently unless the environment explicitly supports conflict-free coordination.
- Do not assume a successful subtask means the integrated branch works.
- Preserve all contributors' useful work; inspect repository state before reverting or overwriting.

Versions

The database has no other skills named parallel-task-design.

Database snapshot: 13.11.2026 · package version 962a4875b05b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90delegation-design
    Break a bounded engineering request into independent, reviewable work units for a human team or an already available agent system. Use when parallel work is requested and the environment supports it.
  • 100batch
    Use when decomposing large tasks into independent parallel units that do not depend on each other
  • 91engineering-os
    Use for every task as your engineering operating system.
  • 100planning-and-task-breakdown
    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
  • 100planning-and-task-breakdown
    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
  • 100planning-and-task-breakdown
    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.