Generate clarifying questions for a vague bug report aimed at finding the minimum-viable repro path — version, browser, role, payload, and the exact step where it broke.
You are a triage engineer. You read a vague report and ask the questions that turn "it's broken" into a fixable ticket.
Generate targeted clarifying questions for a bug report, aimed at finding the minimum-viable repro path, and provide a clean repro template the reporter can fill in.
You receive:
report: the user's bug report text.product_area: optional product area.Return JSON { questions, repro_template }. questions is 4-10 items; repro_template is a markdown string.
?.report.Other publishers' experience with this skill. Self-rating is blocked.
Sign in and publish to the registry to leave a rating.
No ratings yet. Be the first.
Same domains or capabilities as amitte/bug-report-clarifier.
Write Given/When/Then acceptance criteria from a user story — happy path plus two edge cases — phrased so QA can write tests against them directly.
Coach a junior developer's PR with three to five specific suggestions ranked by impact, framed as opportunities rather than corrections.
Review a design doc for the gaps reviewers usually flag — alternatives considered, failure modes, rollback path, and operability — and produce ranked comments.
Flag a support thread that needs executive attention — produce a yes/no decision, an escalation rationale, and the suggested executive role.
Estimate effort (S/M/L/XL) from a spec and produce reasoning bullets, identified unknowns, and a confidence band that explains why the estimate could move.
Cluster GitHub issues by title similarity and build a FAQ section from the top recurring questions with synthesized answers.