Structured bug-report intake
Walks the customer through reproducing the issue with targeted prompts (steps, expected vs. actual, browser, account ID) and produces an engineer-readable report.
Use when your client's product team is drowning in 'it doesn't work' tickets that lack the basics. It's the fastest available path to better bug reports.
It does not diagnose. It collects the information an engineer needs and stops. No guessing at root cause.
- intake
- collect
- handoff
Provisioning the MCP URL for Structured bug-report intake is part of Pro.
Free accounts can read the YAML, run the Live Preview, and provision one starter URL. Pro provisions URLs for the whole catalog.
Open YAML. Read it before you subscribe.
The harness that enforces this YAML is closed and hosted. The YAML is what you can audit, fork, and reason about.
1# structured-bug-report-intake.yaml2name: structured-bug-report-intake3version: 1.0.04category: product-support5description: Engineer-readable bug reports. No diagnosis.6 7required_fields:8 - what_happened9 - expected_behavior10 - steps_to_reproduce11 - environment12 - account_id13 14harness:15 - step: intake16 - step: collect17 fields: <required_fields>18 one_field_per_turn: true19 strict: true20 - step: confirm21 show_summary: true22 - step: handoff23 emit:24 packet: bug_report25 26policy:27 diagnose: false28 guess_root_cause: false29 Need structured bug-report intaketuned to one client’s voice, escalation logic, and required fields? That’s a $99 personalization.
One-shot fee. Turnaround stated up front. The result is yours, with the deterministic harness already wired.
- Known-issue lookupConfirms whether a customer's report matches a known open issue and sets expectations on a fix.
- Feature discoveryHelps the customer find the existing feature that solves their problem, grounded in the product docs you supply.
- Configuration walkthroughStep-by-step setup guidance grounded in your client's documentation.