acceptance-criteria

To generate Given/When/Then acceptance criteria for ServiceNow agile stories, provide a user story description or identifiers. The skill fetches epic context via REST APIs and outputs testable Gherkin criteria covering happy path, edge cases, and security requirements.

The best way to write BDD acceptance criteria covering edge cases and error handling is to generate Gherkin statements from epic context. This approach validates criteria quality and ensures alternative flows, performance, and security requirements are included for QA traceability.

Yes, you can automatically save generated acceptance criteria back to a ServiceNow rm_story record. The skill fetches story context, generates the complete criteria set, and updates the record directly to provide traceability and reduce manual rework.

Generating acceptance criteria requires access to ServiceNow Agile Development 2.0. The skill uses MCP tools and REST APIs to fetch the relevant story and epic context, so your environment must support these integrations to align the Gherkin output correctly.

User stories often lack testable acceptance criteria for QA traceability due to ambiguity in manual drafting. Automatically generating comprehensive Given/When/Then statements directly from epic context reduces this ambiguity and links the validated criteria back to the story.

When using Gherkin to generate acceptance criteria for agile workflows, limitations include dependence on accurate epic context and REST API access. If the source rm_story record lacks clear descriptions, the generated testable criteria may not fully capture complex business logic.