Agent-Skills.md

Agent Skills: fix-parallel

[Fix & Debug] ⚡⚡ Analyze & fix issues with parallel fullstack-developer agents

UncategorizedID: duc01226/easyplatform/fix-parallel

Repository

duc01226/easyplatform
duc01226License: MIT
31

Install this agent skill to your local

pnpm dlx add-skill https://github.com/duc01226/EasyPlatform/tree/HEAD/.claude/skills/fix-parallel

Skill Files

Browse the full folder contents for fix-parallel.

Download Skill

Loading file tree…

.claude/skills/fix-parallel/SKILL.md

Skill Metadata

Name
fix-parallel
Description
"[Fix & Debug] ⚡⚡ Analyze & fix issues with parallel fullstack-developer agents"

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