AgentStack
SKILL verified MIT Self-run

Parallel Dev

skill-coreline-ai-codex-devflow-plugin-parallel-dev · by coreline-ai

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.

No reviews yet
0 installs
7 views
0.0% view→install

Install

$ agentstack add skill-coreline-ai-codex-devflow-plugin-parallel-dev

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Parallel Dev? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Parallel Dev

Overview

Turn one implementation goal into safe, independently executable workstreams. The priority is maximum concurrency without hidden file conflicts.

Workflow

  1. Confirm goal, non-goals, active local changes, and existing plans.
  2. Map likely touch points with rg --files, rg, and docs.
  3. Put shared contracts/types/interfaces into a small foundation workstream.
  4. Split leaf work by path ownership wherever possible.
  5. For each workstream, define objective, deliverables, owned paths, non-owned paths, dependencies, tests, and done criteria.
  6. Decide whether each slice is safe to run in parallel or must be sequential.
  7. Merge foundation first, then leaf workstreams, then shared wiring/docs.
  8. 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

  1. Parallel workstreams
  2. Ownership boundaries and contracts
  3. Integration/merge order
  4. Tests and smoke checks
  5. Risks and required coordination

Read references/parallel-templates.md when a structured workstream card or sub-agent prompt is useful.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.