playbooks

home / skills / duc01226 / easyplatform / fix-parallel

fix-parallel skill

/.claude/skills/fix-parallel

This skill analyzes and fixes parallel fullstack-developer issues, coordinating diagnostics, planning, and parallel execution to improve reliability and speed.

npx playbooks add skill duc01226/easyplatform --skill fix-parallel

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.5 KB
---
name: fix-parallel
description: "[Fix & Debug] ⚡⚡ Analyze & fix issues with parallel fullstack-developer agents"
argument-hint: [issues]
infer: true
---

**Ultrathink parallel** to fix: <issues>$ARGUMENTS</issues>

**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.

## ⚠️ Anti-Hallucination Reminder

**Before modifying ANY code:** Verify assumptions with actual code evidence. Search for usages, read implementations, trace dependencies. If confidence < 90% on any change, investigate first or ask user. See `.claude/skills/shared/anti-hallucination-protocol.md` for full protocol.

## Workflow

### 1. Issue Analysis
- Use `debugger` subagent to analyze root causes
- Use `/scout-ext` to find related files
- Categorize issues by scope/area (frontend, backend, auth, payments, etc.)
- Identify dependencies between issues

### 2. Parallel Fix Planning
- Trigger `/plan-hard --parallel <detailed-fix-instructions>` for parallel-executable fix plan
- Wait for plan with dependency graph, execution strategy, file ownership matrix
- Group independent fixes for parallel execution
- Sequential fixes for dependent issues

### 3. Parallel Fix Implementation
- Read `plan.md` for dependency graph
- Launch multiple `fullstack-developer` agents in PARALLEL for independent fixes
  - Example: "Fix auth + Fix payments + Fix UI" → launch 3 agents simultaneously
  - Pass phase file path: `{plan-dir}/phase-XX-*.md`
  - Include environment info
- Wait for all parallel fixes complete before dependent fixes
- Sequential fixes: launch one agent at a time

### 4. Testing
- Use `tester` subagent for full test suite
- NO fake data/mocks/cheats
- Verify all issues resolved
- If fail: use `debugger`, fix, repeat

### 5. Code Review
- Use `code-reviewer` for all changes
- Verify fixes don't introduce regressions
- If critical issues: fix, retest

### 6. Project Management & Docs
- If approved: use `project-manager` + `docs-manager` in parallel
- Update plan files, docs, roadmap
- If rejected: fix and repeat

### 7. Final Report
- Summary of all fixes from parallel phases
- Verification status per issue
- Ask to commit (use `git-manager` if yes)

**Example:** Fix 1 (auth) + Fix 2 (payments) + Fix 3 (UI) → Launch 3 fullstack-developer agents → Wait → Fix 4 (integration) sequential

## IMPORTANT Task Planning Notes

- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed

Overview

This skill automates analysis and parallel fixing of fullstack agent issues. It coordinates discovery, parallel planning, simultaneous implementation, testing, and review so teams can resolve multiple independent bugs or features quickly. It emphasizes evidence-based changes and staged execution to avoid regressions.

How this skill works

It inspects the codebase to categorize issues by area (frontend, backend, auth, payments, etc.) and traces actual usages before proposing changes. It generates a dependency-aware plan that groups independent fixes for parallel execution and sequences dependent work. For each parallel phase it launches dedicated fullstack developer agents, runs full test suites, and enforces code review before final sign-off.

When to use it

  • Multiple independent bugs or features need fixing at the same time
  • A release requires parallel workstreams to meet a deadline
  • Complex issues have clear dependency graphs with independent subproblems
  • You must reduce lead time by running safe, concurrent fix workflows
  • When rigorous evidence-first change validation is required

Best practices

  • Always verify assumptions in code before editing; if confidence <90% investigate first
  • Break fixes into many small, testable tasks with a final review todo
  • Use a dependency graph to avoid conflicting parallel edits
  • Run full, real tests (no mocks/cheats) after every parallel phase
  • Require a code-review and re-run tests before merging any parallel branch

Example use cases

  • Fix auth bug, payment processing issue, and UI regression simultaneously by launching three parallel agents and coordinating integration after completion
  • Split a large refactor into independent modules and run parallel implementers for each module, then run integration fixes sequentially
  • Urgent patch: parallel hotfixes for backend endpoints while a separate agent stabilizes frontend behavior
  • Release prep: run parallel security hardening, performance tuning, and documentation updates, then consolidate and test

FAQ

How do you avoid merge conflicts from parallel agents?

Plan a clear file ownership matrix and use the dependency graph to prevent overlapping edits; run integration phases sequentially when overlaps exist.

What if a parallel fix fails tests?

Stop dependent phases, debug with the debugger subagent, fix the root cause, re-run the parallel phase, then continue when tests pass.

Can I use this for small one-off fixes?

Yes—use the same evidence-first protocol and lightweight planning, but avoid unnecessary parallelism for trivial tasks.