Feature
Any spec, structured.
AutoGherk reads product specs in whatever format you have them — Jira tickets, Confluence docs, Figma comment threads — and parses them into a consistent structure it can reason over. The parser understands acceptance criteria written in plain English, not just formal BDD syntax.
Problem
Requirements live in docs, tickets and Figma comments. Nobody turns them into tests consistently.
Workflow
Benefits
- Scenarios in minutes, not days
- Consistent Gherkin style across teams
- Catches ambiguous or incomplete acceptance criteria before a developer picks up the ticket
- Works with Jira, Linear, Notion and plain document uploads
Technical
POST /specs { source: "jira" | "doc" | "url" }Related features
Try it on your suite