parallel-dev
Skill1 starsChanged 7 months agoMITView on GitHub
Plan and coordinate parallel development workstreams across a codebase. Use when the user asks to parallelize implementation, split work into multiple PRs/agents, define file ownership boundaries, coordinate sub-agents, reduce merge conflicts, manage dependencies, or create a merge/integration plan for concurrent changes.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- BK202503/open-claude-alltheir own version, first seen Nov 8, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- r-ayin/parallel-devtheir own version, first seen Oct 20, 2026
- EthanReedLabs/suldetheir own version, first seen Oct 8, 2026
- leaf76/agent-skillstheir own version, first seen Aug 17, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- EthanReedLabs/sulde★ 99same name
- blamechris/chroxy★ 8same name
- BK202503/open-claude-all★ 7same name
- leaf76/agent-skills★ 0same name
- r-ayin/parallel-dev★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- dev-plan-generatorSkill
- plan-eng-reviewSkill
- readme-styleSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Put shared contracts/types/interfaces into a small foundation workstream.
- Distinctive: line 21
Run targeted tests per workstream and full verification after integration.
- Distinctive: line 30
Prefer bounded implementation tasks over broad exploration.
- Distinctive: line 31
Keep final integration and full verification in the main agent.
- Very specific: line 41
Read references/parallel-templates.md when a structured workstream card or sub-agent prompt is useful.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Parallel Dev
Overview
Turn one implementation goal into safe, independently executable workstreams. The priority is maximum concurrency without hidden file conflicts.
Workflow
- Confirm goal, non-goals, active local changes, and existing plans.
- Map likely touch points with
rg --files,rg, and docs. - Put shared contracts/types/interfaces into a small foundation workstream.
- Split leaf work by path ownership wherever possible.
- For each workstream, define objective, deliverables, owned paths, non-owned paths, dependencies, tests, and done criteria.
- Decide whether each slice is safe to run in parallel or must be sequential.
- Merge foundation first, then leaf workstreams, then shared wiring/docs.
- Run targeted tests per workstream and full verification after integration.
Sub-Agent Assignment Rules
When using sub-agents:
- Give each worker explicit file ownership and non-ownership.
- Tell workers they are not alone in the codebase.
- Tell workers not to revert or overwrite edits made by others.
- Prefer bounded implementation tasks over broad exploration.
- Keep final integration and full verification in the main agent.
Output Shape
- Parallel workstreams
- Ownership boundaries and contracts
- Integration/merge order
- Tests and smoke checks
- Risks and required coordination
Read references/parallel-templates.md when a structured workstream card or sub-agent prompt is useful.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.