notque/vexjoy-agent / skills/process/workflow
workflow
VerifiedStructured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.
references/project-coordinator/parallel-execution-patterns.md
View on GitHub# 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
```markdown
STREAM A: go-worker (programming/golang-general.md) → src/api/ (RUNNING)
STREAM B: frontend-worker (frontend/typescript-frontend.md) → src/ui/ (RUNNING)
STREAM C: db-worker (data/database.md) → migrations/ (RUNNING)
Fan-in: wait for A+B+C before integration.
```
---
## File Domain Declaration (Pre-Dispatch)
```markdown
Task: Refactor authentication middleware
Agent: api-worker (programming/nodejs-api.md)
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
```markdown
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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks 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. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |