drafting-review-email

Name: drafting-review-email
Availability: InStock
Author: dogkeeper886

Draft stakeholder review emails and meeting invites from Jira ticket reviewers.

Updated Sep 16, 2025

Search Tags:#qa #jira #draft #stakeholders #test-artifacts #review-email #meeting-invite

Ready to run

npx skills add https://github.com/dogkeeper886/ai-qa-workflow --skill drafting-review-email

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: drafting-review-email
Source: https://github.com/dogkeeper886/ai-qa-workflow/tree/main/skills/drafting-review-email
Command: npx skills add https://github.com/dogkeeper886/ai-qa-workflow --skill drafting-review-email

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts a stakeholder review email and a meeting invite for a test plan and test cases by deriving reviewers from a Jira ticket.

Core Features & Use Cases

Extract reviewers from Jira tickets
Generate a draft review email
Generate a meeting invite for the review session
Preview and save drafts to the project workspace

Quick Start

Provide a Jira issue key to fetch reviewers, then run the draft email and meeting invite prompts to generate drafts.

Frequently Asked Questions about drafting-review-email

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

FAQPage Schema

How do I draft a stakeholder review email for test artifacts from a Jira ticket?▼

To draft a stakeholder review email, this Skill extracts reviewer information directly from a Jira ticket using the issue key, then generates a ready-to-send review email for your test plan and test cases.

Can I generate a meeting invite for a test plan review using Jira metadata?▼

Yes, you can generate a meeting invite for a test plan review by deriving the required stakeholders from a Jira ticket, producing a ready-to-send meeting invite for the review session.

What is the best way to extract reviewers from a Jira ticket for a QA review cycle?▼

The best way to extract reviewers from a Jira ticket is providing the Jira issue key to fetch stakeholder details automatically, streamlining QA review cycle coordination across project artifacts.

Do I need mcp-atlassian to access Jira for generating review email drafts?▼

Yes, you need mcp-atlassian:jira_get_issue to access Jira, as the Skill requires this connection to fetch issue details and derive reviewers for generating stakeholder review email drafts.

Can I preview a generated review email before saving it to the project workspace?▼

Yes, you can preview the generated review email and meeting invite, as the Skill provides a safe preview step before saving the final drafts to your project workspace.

What limitations exist when deriving stakeholders from Jira for test case reviews?▼

A limitation is that deriving stakeholders relies entirely on the Jira issue key provided, meaning incomplete Jira ticket metadata will result in missing reviewers for your test case review drafts.