Feature discovery
Takes the customer's described problem and points to the documented feature that solves it, citing the relevant docs section.
Use for the substantial fraction of tickets that are 'how do I do X?' when X is already a documented feature.
It only references documentation you pass in. It does not invent features and does not promise unreleased ones.
- intake
- classify
- handoff
Provisioning the MCP URL for Feature discovery 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# feature-discovery.yaml2name: feature-discovery3version: 1.0.04category: product-support5description: Points to existing documented features.6 7inputs:8 - name: question9 type: string10 - name: docs11 type: array12 13constraints:14 ground_in: docs15 invent_features: false16 promise_unreleased: false17 18harness:19 - step: intake20 - step: classify21 match_against: docs22 - step: handoff23 emit:24 doc_section: <slug>25 cite: true26 Need feature discoverytuned 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.
- Structured bug-report intakeWalks the customer through reproducing a bug and produces a clean, engineer-readable report.
- Known-issue lookupConfirms whether a customer's report matches a known open issue and sets expectations on a fix.
- Configuration walkthroughStep-by-step setup guidance grounded in your client's documentation.