[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.

Prerequisites: MUST READ .claude/skills/shared/understand-code-first-protocol.md AND .claude/skills/shared/evidence-based-reasoning-protocol.md before executing.

• docs/project-reference/domain-entities-reference.md — Domain entity catalog, relationships, cross-service sync (read when task involves business entities/models)

Skill Variant: Variant of /fix — deep investigation with subagents for complex issues.

Quick Summary

Goal: Systematically diagnose and fix complex bugs using parallel subagent investigation.

Workflow:

• Scout — Use scout/researcher subagents to explore the issue in parallel

• Diagnose — Trace root cause through code paths with evidence

• Plan — Create fix plan with impact analysis

• Fix — Implement and verify the fix

Key Rules:

• Debug Mindset: every claim needs file:line evidence

• Use subagents for parallel investigation of multiple hypotheses

• Always create a plan before implementing complex fixes

Debug Mindset (NON-NEGOTIABLE)

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

• Do NOT assume the first hypothesis is correct — verify with actual code traces

• Every root cause claim must include file:line evidence

• If you cannot prove a root cause with a code trace, state "hypothesis, not confirmed"

• Question assumptions: "Is this really the cause?" → trace the actual execution path

• Challenge completeness: "Are there other contributing factors?" → check related code paths

• No "should fix it" without proof — verify the fix addresses the traced root cause

⚠️ MANDATORY: Confidence & Evidence Gate

MANDATORY IMPORTANT MUST declare Confidence: X% with evidence list + file:line proof for EVERY claim. 95%+ recommend freely | 80-94% with caveats | 60-79% list unknowns | <60% STOP — gather more evidence.

Ultrathink to plan & start fixing these issues follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: $ARGUMENTS

Workflow:

If the user provides a screenshots or videos, use ai-multimodal skill to describe as detailed as possible the issue, make sure developers can predict the root causes easily based on the description.

Fullfill the request

Question Everything: Use AskUserQuestion tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.

• If you have any questions, use AskUserQuestion tool to ask the user to clarify them.

• Ask 1 question at a time, wait for the user to answer before moving to the next question.

• If you don't have any questions, start the next step.

Fix the issue

Use sequential-thinking skill to break complex problems into sequential thought steps. Use problem-solving skills to tackle the issues. Analyze the skills catalog and activate other skills that are needed for the task during the process.

• Use debugger subagent to find the root cause of the issues and report back to main agent. 1.5. Write investigation results to .ai/workspace/analysis/{issue-name}.analysis.md . Re-read ENTIRE file before planning fix.

• Use researcher subagent to research quickly about the root causes on the internet (if needed) and report back to main agent.

• Use planner subagent to create an implementation plan based on the reports, then report back to main agent.

• Then use /code SlashCommand to implement the plan step by step.

• Final Report:

• Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.

• Ask the user if they want to commit and push to git repository, if yes, use git-manager subagent to commit and push to git repository.

• IMPORTANT: Sacrifice grammar for the sake of concision when writing reports.

• IMPORTANT: In reports, list any unresolved questions at the end, if any.

REMEMBER:

• You can always generate images with ai-multimodal skills on the fly for visual assets.

• You always read and analyze the generated assets with ai-multimodal skills to verify they meet requirements.

• For image editing (removing background, adjusting, cropping), use media-processing skill as needed.

IMPORTANT Task Planning Notes (MUST FOLLOW)

• Always plan and break work into many small todo tasks

• Always add a final review todo task to verify work quality and identify fixes/enhancements

• After fixing, MUST run /prove-fix — build code proof traces per change with confidence scores. Never skip.