parallel-execution-patterns
**Scope**: Safe parallel agent streams, file domain conflict detection, concurrent workloads.
$ npx -y skills add notque/vexjoy-agent --agent claude-codeHow it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
**Scope**: Safe parallel agent streams, file domain conflict detection, concurrent workloads.
Agent definition
parallel-execution-patterns.mdParallel Execution Patterns Reference
> **Scope**: Safe parallel agent streams, file domain conflict detection, concurrent workloads.
---
Task Parallelism Categories
| Task Type | Safe? | Constraint | |-----------|-------|------------| | Different file domains | Yes | No shared files | | Same file, different sections | No | Serialize via handoff | | Read-only analysis/audit/review | Always | No write conflicts | | Test-only agents | Yes | Read-only against source | | Schema migration + app code | No | Migration first | | Lint + format on same file | No | Sequential post-compile | | Documentation updates | Usually | Check shared index files |
---
Fan-Out Parallel Dispatch
STREAM A: golang-general-engineer → src/api/ (RUNNING)
STREAM B: typescript-frontend-engineer → src/ui/ (RUNNING)
STREAM C: database-engineer → migrations/ (RUNNING)
Fan-in: wait for A+B+C before integration.
---
File Domain Declaration (Pre-Dispatch)
Task: Refactor authentication middleware
Agent: nodejs-api-engineer
Domain: src/middleware/auth.ts, src/middleware/session.ts
Excludes: src/routes/ (owned by STREAM B)
Success: `npm test -- auth` passes
Explicit declaration makes conflicts visible at planning time.
---
Fan-In Gate
Wait conditions:
- [ ] STREAM A complete
- [ ] STREAM B complete
- [ ] STREAM C complete
BLOCKED: Do not dispatch integration until all checked.
Partial integration creates inconsistent state.
---
Pattern Catalog
Verify Domain Isolation Before Dispatch
**Signal**: Dispatching 3 agents without checking shared files. **Detection**: `grep -r "config/config" src/ | cut -d: -f1 | sort | uniq -d` **Fix**: Run domain conflict check before every parallel wave. Serialize agents sharing any file.
Treat Code Generation as Sequential Gate
**Signal**: Running `go generate` while another stream reads generated files. **Fix**: Generation completes fully, fan-in confirms output exists, then downstream starts.
Enforce Compile-Test-Lint-Format Sequence
**Signal**: Lint and compile agents dispatched simultaneously. **Fix**: Within any domain: Compile → Test → Lint → Format. Only proceed after previous exits 0.
---
Parallel Capacity Heuristics
| Scenario | Max Parallel | |----------|-------------| | Clean domain boundaries | 5-8 | | Shared config layer | 3-4 (config agent first) | | Monorepo cross-cutting | 2-3 | | Active schema migration | 1 + blocked | | Context at 70%+ | 1 only |
---
Parallelism Decision Checklist
1. `[ ]` Domain overlap check — no shared files 2. `[ ]` Dependencies resolved — prerequisites complete 3. `[ ]` Generated files stabilized 4. `[ ]` Context budget allows N agents 5. `[ ]` Fan-in gate documented in STATUS.md
Read more
Parallel Execution Patterns Reference
> **Scope**: Safe parallel agent streams, file domain conflict detection, concurrent workloads.
---
Task Parallelism Categories
| Task Type | Safe? | Constraint | |-----------|-------|------------| | Different file domains | Yes | No shared files | | Same file, different sections | No | Serialize via handoff | | Read-only analysis/audit/review | Always | No write conflicts | | Test-only agents | Yes | Read-only against source | | Schema migration + app code | No | Migration first | | Lint + format on same file | No | Sequential post-compile | | Documentation updates | Usually | Check shared index files |
---
Fan-Out Parallel Dispatch
STREAM A: golang-general-engineer → src/api/ (RUNNING) STREAM B: typescript-frontend-engineer → src/ui/ (RUNNING) STREAM C: database-engineer → migrations/ (RUNNING) Fan-in: wait for A+B+C before integration.
---
File Domain Declaration (Pre-Dispatch)
Task: Refactor authentication middleware Agent: nodejs-api-engineer Domain: src/middleware/auth.ts, src/middleware/session.ts Excludes: src/routes/ (owned by STREAM B) Success: `npm test -- auth` passes
Explicit declaration makes conflicts visible at planning time.
---
Fan-In Gate
Wait conditions: - [ ] STREAM A complete - [ ] STREAM B complete - [ ] STREAM C complete BLOCKED: Do not dispatch integration until all checked.
Partial integration creates inconsistent state.
---
Pattern Catalog
Verify Domain Isolation Before Dispatch
**Signal**: Dispatching 3 agents without checking shared files. **Detection**: `grep -r "config/config" src/ | cut -d: -f1 | sort | uniq -d` **Fix**: Run domain conflict check before every parallel wave. Serialize agents sharing any file.
Treat Code Generation as Sequential Gate
**Signal**: Running `go generate` while another stream reads generated files. **Fix**: Generation completes fully, fan-in confirms output exists, then downstream starts.
Enforce Compile-Test-Lint-Format Sequence
**Signal**: Lint and compile agents dispatched simultaneously. **Fix**: Within any domain: Compile → Test → Lint → Format. Only proceed after previous exits 0.
---
Parallel Capacity Heuristics
| Scenario | Max Parallel | |----------|-------------| | Clean domain boundaries | 5-8 | | Shared config layer | 3-4 (config agent first) | | Monorepo cross-cutting | 2-3 | | Active schema migration | 1 + blocked | | Context at 70%+ | 1 only |
---
Parallelism Decision Checklist
1. `[ ]` Domain overlap check — no shared files 2. `[ ]` Dependencies resolved — prerequisites complete 3. `[ ]` Generated files stabilized 4. `[ ]` Context budget allows N agents 5. `[ ]` Fan-in gate documented in STATUS.md
Essays and writing behind this toolkit live at vexjoy.com. AI agents skip steps. "Looks correct" replaces running tests. "Trivial change" replaces verification.
Repo: notque/vexjoy-agent
Other agents on vexjoy-agent.
- ansible-automation-engineer
Ansible automation: playbooks, roles, collections, Molecule testing, Vault security.
Open agent - modules
**Scope**: Module selection patterns, builtin vs command/shell decisions, collection modules, and version-specific module changes **Version range**: ansible-core 2.14+ / Ansible Collections (community.general 7.0+) **Generated**: 2026-04-04 — verify against current Ansible
Open agent - testing
**Scope**: Molecule test scenarios, ansible-lint rules, idempotency validation, and check-mode patterns **Version range**: Molecule 6.0+ / ansible-lint 6.0+ / ansible-core 2.14+ **Generated**: 2026-04-04 — verify against current Molecule and ansible-lint documentation
Open agent - base-instructions
Universal operational rules injected by /do at agent dispatch. Domain-specific rules live in each agent's .md file.
Open agent - communication-patterns
**Scope**: Failure modes in agent output style — over-reporting, self-congratulation, verbose narration, and hedging. Covers what to detect and how to fix each. **Version range**: all versions **Generated**: 2026-05-11
Open agent - combat-effects-upgrade
Zero-dependency combat visual upgrades: CSS particle replacement, Framer Motion combat juice, CSS 3D card transforms.
Open agent

