Ask Specsight
In-product chat over your spec. Ask a question in plain language and get an answer drawn from your own features, scenarios and changelog, with sources you can click.
Ask Specsight answers questions about your product in plain language. What changed in the last release? How does the upload limit behave? Which features have the most error scenarios? Every answer is drawn from your own spec: features, scenarios, changelog, digests and release notes. When the spec does not cover the question, Specsight says so rather than guess.
Answers come back as structured cards rather than walls of text: a feature map, a table of scenarios in Context/Action/Outcome form, what changed over a window, a digest, a set of release notes. Each card links into the spec, and every numbered source opens the exact scenario, feature or annotation it drew on. Admins, Developers and Editors can also ask it to draft release notes over a date range, which creates a draft to review and never publishes.
There are two surfaces. Project Ask answers about one project. Specsight Help answers how to use Specsight itself: plans, members, billing, setup. Both open from the dashboard, or with ⌘K from anywhere. Ask is in beta and available to every organisation.
Related terms
- SPEC
Scenario
A single plain-language description of how a product behaves in a specific situation. The atomic unit of a Specsight spec.
- SPEC
Changelog
A chronological record of what changed in a product, feature, or scenario over time. In Specsight, one running changelog covers the whole product, filterable down to a single feature.
- OPERATIONS
MCP (Model Context Protocol)
An open standard from Anthropic for connecting AI assistants to external data and tools. Specsight ships a read-only MCP server so assistants can query a live spec.