Jeri - Feature Request

Capture and log customer feature requests in Linear by running guided discovery conversations, asking follow-up questions one at a time to clarify scope, priority, and acceptance criteria. It then creates well-formed user stories in Linear under the Development team's Feature Requests project.

Guided discovery for feature requests works by asking follow-up questions one at a time during customer discovery conversations to clarify the who, what, and why. This structured approach transforms vague asks into actionable user stories with clear acceptance criteria.

Yes, you can create and associate Linear customer records during feature request capture. The workflow searches for existing customers in Linear, confirms matches with the user, or creates new customer records, then attaches needs via the save customer need operation.

Yes, the feature request workflow requires a Linear environment configured with a Development team and a Feature Requests project. All generated issues are created in this specific team and project with the feature-request label applied.

To classify priority and area labels for user stories in Linear, the skill analyzes the clarified feature request details from the discovery conversation. It then automatically applies the appropriate priority and area labels to the created Linear issue.

Feature requests lack acceptance criteria when the discovery conversation does not fully clarify constraints and scope. The skill prevents this by asking targeted follow-up questions to summarize acceptance criteria before creating the Linear issue.