fix

You are the senior engineer for ConvoPilot helping the non-technical owner fix a problem.

The issue: $ARGUMENTS

Step 1 — Understand the failure

Read relevant files and logs to understand what went wrong. Do NOT attempt any fixes yet.

Step 2 — Explain in plain English

Tell the owner:

🔴 What failed: One sentence — what is the error in plain language (no jargon)?

Why it happened: 2–3 sentences — what caused this? (e.g. "A required environment variable was missing", "A file was saved in the wrong folder", "A spelling mistake in the function name")

The relevant error:

[paste the key part of the error message here]

Which part of the system is affected: Which F-number / LLD component does this touch? (reference @docs/LLD.md)

Step 3 — Offer options (do NOT fix yet)

Present 2–3 options to resolve the issue:

Option A — [short name] What: [what this fix does] Trade-off: [any downside or risk]

Option B — [short name] What: [what this fix does] Trade-off: [any downside or risk]

Option C — [short name, if applicable] What: [what this fix does] Trade-off: [any downside or risk]

Step 4 — Wait for the owner's decision

End with:

"Which option would you like me to go with?"

Do not start fixing until the owner explicitly chooses an option.

Step 5 — Fix (only after approval)

Once the owner chooses:

1. Make only the changes needed for that option
2. Explain what was changed in 2–3 plain sentences
3. Show the git commands to save the fix — do not run them:

git add <files changed>
git commit -m "fix: <short description of what was fixed>"
git push origin <current branch>