Help us improve
Share bugs, ideas, or general feedback.
From feature-lifecycle
Creates a Jira ticket from a feature description with BDD acceptance criteria. Use when the user wants to create a ticket, file a bug, add a story, log a task, or write a Jira issue.
npx claudepluginhub gravity9-tech/claude_code_marketplace_demo --plugin feature-lifecycleHow this skill is triggered — by the user, by Claude, or both
Slash command
/feature-lifecycle:create-ticketThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a Jira ticket with BDD-formatted acceptance criteria, duplicate detection, and automatic issue type classification from a natural language feature description.
Interactively writes structured tickets (story, bug, epic, initiative, subtask, issue) with type-specific fields and quality checks. Outputs clean Markdown ready for any tracker.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Create a Jira ticket with BDD-formatted acceptance criteria, duplicate detection, and automatic issue type classification from a natural language feature description.
Call getAccessibleAtlassianResources to retrieve the Atlassian Cloud ID. You need this for all subsequent Jira API calls.
If the user specified a project key (e.g., "PROJ", "TEA"), use that directly.
If not specified, call getVisibleJiraProjects to list available projects, then use AskUserQuestion to ask the user which project to use. Present the project keys and names as options.
Determine the issue type from the user's description:
| Choose | When the description mentions... |
|---|---|
| Bug | Something is broken, not working, error, crash, regression, fix needed |
| Story | New user-facing feature, user flow, "as a user I want..." |
| Task | Technical work, refactoring, setup, configuration, chore, maintenance |
If ambiguous, default to Story for feature descriptions or Task for technical work.
Search for existing tickets that might cover the same work:
searchJiraIssuesUsingJql with a JQL query like:
project = PROJ AND summary ~ "key term" AND status != Done ORDER BY created DESC
search (Rovo Search) with the feature description for broader matchingIf potential duplicates are found:
Structure the ticket description as follows:
## Summary
[1-2 sentence summary of what this feature/fix/task accomplishes]
## Acceptance Criteria
**Scenario 1: [Descriptive scenario name]**
- **Given** [initial context or precondition]
- **When** [action the user or system takes]
- **Then** [expected observable outcome]
**Scenario 2: [Descriptive scenario name]**
- **Given** [initial context or precondition]
- **When** [action the user or system takes]
- **Then** [expected observable outcome]
[Add more scenarios as needed — typically 2-4 per ticket]
## Technical Notes
[Only include this section if there are implementation details, constraints, or dependencies worth noting. Omit if not relevant.]
Guidelines for writing acceptance criteria:
Call createJiraIssue with:
cloudId: from Step 1projectKey: from Step 2issueTypeName: from Step 3 ("Bug", "Story", or "Task")summary: A concise title (under 80 characters, imperative voice)description: The BDD-formatted description from Step 5Display the created ticket to the user:
Ticket created: [KEY-123] — [Summary]
Type: [Bug/Story/Task]
URL: https://[site].atlassian.net/browse/[KEY-123]
User: "Create a ticket for adding a search bar to the homepage that filters products by name"
Assistant actions:
Get Cloud ID from getAccessibleAtlassianResources
Ask user which project to use (shows available projects)
Classify as Story (new user-facing feature)
Search for duplicates: project = PROJ AND summary ~ "search" AND status != Done
No duplicates found — proceed
Create ticket with:
Summary: Add product search bar to homepage
Description:
## Summary
Add a search bar to the homepage that allows users to filter the product grid by name in real time.
## Acceptance Criteria
**Scenario 1: Search filters products by name**
- **Given** the user is on the homepage with all products visible
- **When** the user types "green" into the search bar
- **Then** only products containing "green" in their name are displayed
**Scenario 2: Empty search shows all products**
- **Given** the user has typed a search query with filtered results
- **When** the user clears the search bar
- **Then** all products are displayed again
**Scenario 3: No results found**
- **Given** the user is on the homepage
- **When** the user types a query that matches no products
- **Then** a "No products found" message is displayed
## Technical Notes
- Search should be case-insensitive
- Filter client-side against already-loaded product data for instant results
Return: Ticket created: PROJ-42 — Add product search bar to homepage