Defect Intake and Triage
Turns "it's broken" into something an engineer can act on, or says exactly what is still missing.
🔴 This does not reproduce anything. Reproduction needs a terminal, a staging environment and
arbitrary browser control, none of which Cowork has. The portable half of a bug-reproduction
pattern is the intake and handoff, and that is all this does. The card says so to the reader.
Inputs
- The report itself, from Email or Teams
- Enterprise Search for prior reports of the same thing, and for the owning team
references/config.md for the required intake fields and the severity vocabulary
Procedure
- Extract the report into the required fields from config: what was expected, what happened,
when, who, which system, which environment, how often, and what evidence is attached.
- Mark every field that is absent MISSING and generate the one question that would fill it.
A triage whose output is three precise questions is more useful than one that guesses.
- Search for duplicates: prior reports with the same system and symptom. Link them. Say
"possible duplicate" and never "duplicate", because that call belongs to the owning team.
- Identify the owning team from evidence: who owns the system in documents or who answered
prior reports. Mark UNKNOWN rather than guessing.
- Assign a severity only if the config vocabulary has an evidenced rule for it. Otherwise
leave it unset and say why.
- Produce an Adaptive Card with the full intake, the missing fields, the possible duplicates
and the proposed owner, for the user to approve before anything is filed.
Output
Adaptive Card carrying: the structured intake, MISSING fields with the question for each, possible
duplicates with links, proposed owning team, and the proposed ticket title and body.
Definition of done
Every required field is filled or MISSING-with-a-question, duplicates are linked, and nothing was
filed.
A triage that concludes "not enough information, here are the three questions" is a success.
It is better than a ticket an engineer closes as unreproducible.
When there is no data
- The report is one sentence: produce the questions. Do not pad the intake with assumptions.
- No owning team found: UNKNOWN, and say what you searched.
- Evidence referenced but not attached: list it as evidence to request.
Boundaries
- Never file, create, assign or comment on a ticket without approval. Filing requires a work
tracker plugin and the user's explicit go.
- Never attempt reproduction. No terminal, no staging, no browser steps.
- Never declare a duplicate, a root cause or a severity the config does not support.
- Never include customer identifiers in a ticket body unless the user approves.
Self-check
- Is every missing field paired with the question that would fill it?
- Did I say "possible duplicate" rather than "duplicate"?
- Did I avoid claiming any reproduction?
1---2name: defect-intake-triage3description: Turns a reported problem in mail or Teams into a structured, ticket-ready intake with the evidence attached and the gaps named, then an Adaptive Card for approval before anything is filed. Use when the user asks to triage a bug report, turn a complaint into a ticket, prepare a defect for filing, or says a user reported a problem.4metadata:5 source: https://skillmd.com/skills/kesslernity/defect-intake-triage6---78# Defect Intake and Triage910Turns "it's broken" into something an engineer can act on, or says exactly what is still missing.1112🔴 **This does not reproduce anything.** Reproduction needs a terminal, a staging environment and13arbitrary browser control, none of which Cowork has. The portable half of a bug-reproduction14pattern is the **intake and handoff**, and that is all this does. The card says so to the reader.1516## Inputs17- The report itself, from **Email** or Teams18- **Enterprise Search** for prior reports of the same thing, and for the owning team19- `references/config.md` for the required intake fields and the severity vocabulary2021## Procedure221. **Extract the report** into the required fields from config: what was expected, what happened,23 when, who, which system, which environment, how often, and what evidence is attached.242. **Mark every field that is absent MISSING** and generate the one question that would fill it.25 A triage whose output is three precise questions is more useful than one that guesses.263. **Search for duplicates**: prior reports with the same system and symptom. Link them. Say27 "possible duplicate" and never "duplicate", because that call belongs to the owning team.284. **Identify the owning team** from evidence: who owns the system in documents or who answered29 prior reports. Mark UNKNOWN rather than guessing.305. **Assign a severity** only if the config vocabulary has an evidenced rule for it. Otherwise31 leave it unset and say why.326. **Produce an Adaptive Card** with the full intake, the missing fields, the possible duplicates33 and the proposed owner, for the user to approve before anything is filed.3435## Output36Adaptive Card carrying: the structured intake, MISSING fields with the question for each, possible37duplicates with links, proposed owning team, and the proposed ticket title and body.3839## Definition of done40Every required field is filled or MISSING-with-a-question, duplicates are linked, and nothing was41filed.4243**A triage that concludes "not enough information, here are the three questions" is a success.**44It is better than a ticket an engineer closes as unreproducible.4546## When there is no data47- The report is one sentence: produce the questions. Do not pad the intake with assumptions.48- No owning team found: UNKNOWN, and say what you searched.49- Evidence referenced but not attached: list it as evidence to request.5051## Boundaries52- **Never file, create, assign or comment on a ticket without approval.** Filing requires a work53 tracker plugin and the user's explicit go.54- **Never attempt reproduction.** No terminal, no staging, no browser steps.55- Never declare a duplicate, a root cause or a severity the config does not support.56- Never include customer identifiers in a ticket body unless the user approves.5758## Self-check59- Is every missing field paired with the question that would fill it?60- Did I say "possible duplicate" rather than "duplicate"?61- Did I avoid claiming any reproduction?