wa:jira

Create, retrieve, and search WA JIRA issues with enforced labels and titles.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-jira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:jira
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/jira
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-jira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

wa:jira removes the guesswork of how to create, label, and structure WA JIRA issues by enforcing a consistent title, tags, assignee assignment, and acceptance-criteria formatting.

Core Features & Use Cases

  • Create issues for new backend, frontend, documentation, infrastructure, security, QA, or bot work with the correct WA label and domain prefix in the title.
  • Fetch issue details to quickly review the current state, assignee, and metadata for an existing WA issue key.
  • Search issues to locate work using queries such as sprint filters (e.g., active sprints) while keeping results aligned to WA conventions.
  • Use case: create a task like “BE: Add auth endpoint” and then retrieve it later to confirm tags, assignee, and checklist-based acceptance criteria.

Quick Start

Create a WA task by running: /wa:jira create "BE: Add auth endpoint" --type task

Frequently Asked Questions about wa:jira

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Jira tasks with consistent naming conventions and labels?

To create Jira tasks with consistent conventions, use a structured issue creation process that automatically enforces domain-prefixed plain-text titles, applies the correct WA label, and assigns the proper assignee_id for the project.

What is required when creating a bug ticket in Jira for this project?

Creating a bug ticket in this project requires linking the issue to a parent epic and defining checklist-based acceptance criteria to ensure the bug is properly scoped and trackable within the ongoing sprint.

How can I search for active Jira sprint issues for ongoing project execution?

You can search for active Jira sprint issues by running a filtered query, such as sprint = active, to quickly locate and review ongoing project execution tasks while keeping search results aligned to project conventions.

How do I retrieve Jira issue details to review assignee and metadata?

You can retrieve Jira issue details by looking up the specific issue key, which fetches the current state, assignee, tags, and metadata to quickly review the task's progress and formatting.

Can I use this workflow to manage backend, frontend, and QA Jira tickets?

Yes, this workflow supports creating and managing Jira issues for backend, frontend, documentation, infrastructure, security, QA, and bot work, enforcing the correct domain prefix in the title for each specific type.

What format should acceptance criteria follow when structuring Jira issues?

Acceptance criteria should follow a checklist-based formatting structure to remove guesswork, ensuring that task requirements are clearly defined and verifiable before the issue is assigned and moved into a sprint.