Bug report tidy-up

Turns a vague complaint into a report someone can act on.

Engineering · produces a Document · built in, ready to run

What you give it

Something like this:

the app is broken again, orders not going through for some customers. bilal called and said it happened yesterday too. i think it started after the update. some stores are fine. it says something about price list. please fix asap this is costing us.

What you get back

This is a real run of the skill on the input above, not a mock-up:

# Bug Report – Orders Not Processing for Some Customers

## What Happens
Orders are failing to process for some customers. The issue may be related to price list functionality and began after a recent update. Some stores are unaffected. Error messaging references "price list."

## What Should Happen
All orders should process successfully for all customers across all stores.

## Steps to Reproduce
**Currently Unknown** – The following information is needed to reproduce this issue:
1. Which specific customers or customer segments are affected?
2. What error message or behavior do affected customers see when attempting to place an order?
3. What is the exact date and time the issue started?
4. What was changed in the recent update that coincides with the start of this issue?
5. Which stores ARE working, and what do they have in common with stores that are NOT working?
6. Can you reproduce this in a test/staging environment, or does it only occur in production?
7. Does the issue affect all orders from affected customers, or only certain product types/price ranges?

## Environment
- **Status**: Production (affecting real customers and revenue)
- **Trigger**: Recent application update
- **Partial scope**: Issue affects some stores but not others

## What Is Still Unknown
- Exact reproduction steps
- Affected customer identifiers or characteristics
- Specific error messages or logs
- Root cause (application code, configuration, data corruption, or external service)
- Whether the issue is deterministic or intermittent
- Full scope of the update that preceded the issue

---

**Recommendation**: Escalate to the engineering team with the questions above. Prioritize obtaining reproduction steps and comparing the recent update against affected vs. unaffected store configurations.

The wording changes a little every run. The shape does not — that is what the procedure below is for.

Tools it uses

None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.

The procedure it follows

This is the skill, in full. Add it to your own skills to change any of it.

Turn the report below into something actionable.

Shape:
- What happens
- What should happen
- Steps to reproduce, numbered
- Environment, if stated
- What is still unknown

Do not invent reproduction steps. If they are missing, list the exact questions that would get them.

How to run it

In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.

New to skills? Start with what a skill is.