.agents/skills/find-bugs/references/bug-plan.md
Write each decision-ready plan to:
tmp/bugs/<package>-<short-kebab-case-symptom>.md
Use daisyui, docs, or cross-package as <package>. Keep the filename short and descriptive.
Before you create a file, search tmp/bugs/*.md for the same root cause. Update the existing file
instead of creating a duplicate.
Use one file for multiple symptoms only when they have the same proven root cause and the same solution. Otherwise, write a separate file for each bug.
Use only these sections and keep each section concise. Do not add frontmatter, extra sections, implementation code, or a patch.
# Summary
<Describe the issue.>
# Impact
<Explain how the issue affects the product and its users.>
# Current behavior
<Describe what the product does now.>
# Expected behavior
<Describe what the product must do instead.>
# Reason
<Explain the proven root cause. Include repository-relative file and symbol references when they
help identify the cause.>
# Reproduction
<Give the shortest exact steps that reproduce the issue. Include only the minimal commands or
code example needed. State the failure result.>
# Solution
## 1. <Solution name> — Recommended
<Describe the solution.>
- Pros: <Main benefits.>
- Cons: <Main disadvantages.>
- Possible side effects: <Product behavior or areas that can change. Write `None known` when no
side effect is known.>
## 2. <Solution name>
<Describe the solution.>
- Pros: <Main benefits.>
- Cons: <Main disadvantages.>
- Possible side effects: <Product behavior or areas that can change. Write `None known` when no
side effect is known.>
## 3. <Solution name>
<Describe the solution.>
- Pros: <Main benefits.>
- Cons: <Main disadvantages.>
- Possible side effects: <Product behavior or areas that can change. Write `None known` when no
side effect is known.>