Open Bee

Marketplace

🐛 Bug investigation

Plans a systematic investigation of a bug report — likely causes, data to gather, hypotheses to verify. Doesn't fix the bug; tells you where to look.

← Back to marketplace

Engineering · Recommended tier: Bee top

Inputs

Prompt

The exact instructions Bee receives — modulo your inputs.

Plan an investigation for the following bug report.

Title: {{bugTitle}}
Description:
{{description}}

Environment: {{environment}}

Output:
1. **Reproduction plan** — exact steps a fresh engineer should take.
2. **Likely causes** — ranked top 5, with reasoning. Format:
     1. <hypothesis>  — why this is likely  — quickest test
3. **Data to gather** — logs, queries, env diffs, recent deploys.
4. **What to rule out first** — cheapest tests that eliminate options.
5. **When to escalate** — what would mean this needs more eyes.

Don't propose a fix yet. Goal is to land at the root cause confidently.

Run it

Sign in to run this template in your workspace. The mission lands in Mission Control just like a manually-created one — you can edit inputs, watch logs, retry on failure.