pantheon-ai/issue-tracker-toolkit

Toolkit for writing, refining, and prioritizing tickets on issue-tracking systems (Jira and equivalents). Covers three concerns: writing clear acceptance criteria for user stories; applying MoSCoW prioritization to requirements and backlogs; and readying sparse backlog tickets for refinement by gathering incident context, applying a YAML template, and generating a validated structured document.

Quality

93%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Gherkin Examples for Acceptance Criteria

Name: pantheon-ai/issue-tracker-toolkit
Rating: 93.33333333333331 (1 reviews)
Author: pantheon-ai

Use these examples when the story has ordered interactions or when scenarios will be automated.

Login

Scenario: Successful login with valid credentials
Given the user has a registered account
And the account is not locked
When the user submits valid email and password
Then the user is redirected to the dashboard
And a session is created for 24 hours

Scenario: Login fails with invalid password
Given the user has a registered account
When the user submits a valid email and invalid password
Then an "Incorrect email or password" message is shown
And the user remains on the login page

Password Reset

Scenario: Request reset link
Given the user is on the sign-in page
When the user requests password reset for a registered email
Then a reset email is sent
And the UI shows a confirmation message

Scenario: Expired reset token
Given the user opened a reset link older than 1 hour
When the user submits a new password
Then the reset is rejected
And the UI prompts the user to request a new link

API Create User

Scenario: Create user succeeds
Given a valid auth token with admin scope
When a POST request is sent to /api/v1/users with valid payload
Then the response status is 201
And the response includes id, email, role, and createdAt

Scenario: Create user fails with duplicate email
Given a valid auth token with admin scope
And a user already exists with the requested email
When a POST request is sent to /api/v1/users
Then the response status is 409
And the response includes a duplicate email error