Sequential-first execution with controlled parallelism. WIP limit: 3 agents max. [EXPLICIT] Parallel only when plan has [PARALLEL-OK] tags, zero dependencies, forward-only. [EXPLICIT] Git worktrees, contract-first integration, atomic mergeable units. [EXPLICIT] Trigger: "parallel work", "worktree", "concurrent development", "sequential first", "WIP limit"
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdtemplates/output.docx.mdtemplates/output.htmlSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
"Sequential is safe. Parallel is fast. Smart is knowing when to switch."
Default: sequential. All tasks execute one after another along the critical path. Parallelism is activated ONLY when the approved plan explicitly marks tasks [PARALLEL-OK] with zero pre-dependencies, zero co-dependencies, and WIP <= 3 agents. Forward-only execution — no task waits for another parallel task. When in doubt: sequential. The burden of proof is on parallelism.
[PARALLEL-OK] tags[PARALLEL-OK] tags: STOP — execute sequentially along critical pathRun the 4-point checklist. ALL must pass:
[PARALLEL-OK] on candidate tasksIf ANY check fails → fall back to sequential execution
# Batch 1: max 3 concurrent
git worktree add ../task-auth feat/auth
git worktree add ../task-dashboard feat/dashboard
git worktree add ../task-api feat/api-contracts
# Batch 2: after batch 1 completes
git worktree add ../task-nav feat/navigation
git worktree add ../task-footer feat/footer
// contracts/user-api.ts — agreed interface
export interface UserService {
getUser(id: string): Promise<User>;
updateUser(id: string, data: Partial<User>): Promise<void>;
}
# Merge in dependency order
git checkout main
git merge feat/api-contracts # Contracts first
git merge feat/auth # Independent impl
git merge feat/dashboard # Independent impl
git worktree remove ../task-auth
git worktree remove ../task-dashboard
[PARALLEL-OK] tags for parallelized tasks| Anti-Pattern | Why It's Bad | Do This Instead |
|---|---|---|
| Defaulting to parallel | Merge risk, context fragmentation | Default to sequential; parallel requires plan approval |
| WIP > 3 | Cognitive overload, review bottleneck | Batch: 3 max concurrent, then next batch |
| Parallel with dependencies | Deadlocks, waiting, broken merges | Zero-dependency check BEFORE launching |
| Task waiting for another parallel task | Violates forward-only, creates deadlock | Stop dependent task, return to sequential queue |
| Parallel work without contracts | Integration breaks on merge | Define interfaces BEFORE parallel work |
| Force-pushing to shared branches | Destroys others' work history | Use merge commits, never force-push |
| Worktrees without cleanup | Disk bloat, stale references | Remove worktrees after merge |
discovery-orchestration — Identifies parallel execution opportunities in pipelinesapi-design — Defines API contracts for integration pointscomponent-architecture — Defines component interfaces for UI integrationgithub-actions-ci — CI pipeline that validates merged resultExample invocations:
| Scenario | Handling |
|---|---|
| Empty or minimal input | Request clarification before proceeding |
| Conflicting requirements | Flag conflicts explicitly, propose resolution |
| Out-of-scope request | Redirect to appropriate skill or escalate |