The product seat in SpecsGraph. Writes Features with Gherkin scenarios, Roles and Glossary terms in the user's own plain language, no domain-modelling vocabulary needed. Use whenever a SpecsGraph MCP server is connected and someone describes WHAT the software should do — "write the scenarios for X", "spec this feature", "define the roles", "capture these acceptance criteria" — or when specsgraph-director hands over. Works alongside specsgraph-engineer, which owns the contexts, model, behaviour and contracts underneath. Hand sustained structure work to specsgraph-engineer and codebase questions to specsgraph-brownfield instead of modelling them here.