How do I install the Drafting Review Email skill?

Run npx skillmds@latest add majiayu000/drafting-review-email in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Drafting Review Email safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Drafting Review Email?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Drafting Review Email free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Drafting Review Email?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Drafting Review Email by majiayu000

Name: Drafting Review Email
Rating: 4.5 (4 reviews)
Author: majiayu000

Drafting Review Email

Drafts a stakeholder review email and a meeting invite for a test plan and test cases, using reviewers identified from the Jira ticket. Use when a QA engineer wants to draft a review email, create a meeting invite, send a review request, or notify stakeholders about test artifacts.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

drafting-review-email

Drafts a stakeholder review email and meeting invite for test plan and test cases.

Progress Checklist

Copy and track your progress:

- [ ] Step 1: Read project context
- [ ] Step 2: Extract reviewers from Jira ticket
- [ ] Step 3: Draft review email
- [ ] Step 4: Draft meeting invite
- [ ] Validate: Preview both drafts and confirm before saving

Steps

Step 1: Read Project Context

Read these files from the project folder:

README.md — project overview and ticket ID
test_plan/README.md — test plan type, scenario count
test_cases/README.md — test case count
confluence/confluence_links.md — Confluence page URLs

Step 2: Extract Reviewers

Fetch the Jira ticket using mcp-atlassian:jira_get_issue to identify:

Assignee (primary reviewer)
Reporter (stakeholder)
Watchers (additional reviewers)
Any reviewer names mentioned in comments

Step 3: Draft Review Email

Run /pm-demo-email to create the review email from project context and reviewer list.

Step 4: Draft Meeting Invite

Run /pm-meeting-invite to create the meeting invite for the review session.

Use reference-style links (URLs at bottom) to keep the body scannable.

Validate

Show both full drafts to the user. Ask: "Do these look good? Should I save them to files?"

Do NOT save to disk until the user confirms.

After confirmation, save:

demo/Demo_Showcase_Email.md — email draft
Meeting_Invite_[Type]_Review.md — meeting invite

Expected Input

Path to project folder containing README.md, test_plan/, test_cases/, and confluence/ files.

---name: drafting-review-emaildescription: Drafts a stakeholder review email and a meeting invite for a test plan and test cases, using reviewers identified from the Jira ticket. Use when a QA engineer wants to draft a review email, create a meeting invite, send a review request, or notify stakeholders about test artifacts.--- # drafting-review-email Drafts a stakeholder review email and meeting invite for test plan and test cases. ## Progress Checklist Copy and track your progress: ``` - [ ] Step 1: Read project context - [ ] Step 2: Extract reviewers from Jira ticket - [ ] Step 3: Draft review email - [ ] Step 4: Draft meeting invite - [ ] Validate: Preview both drafts and confirm before saving ``` ## Steps ### Step 1: Read Project Context Read these files from the project folder: - `README.md` — project overview and ticket ID - `test_plan/README.md` — test plan type, scenario count - `test_cases/README.md` — test case count - `confluence/confluence_links.md` — Confluence page URLs ### Step 2: Extract Reviewers Fetch the Jira ticket using `mcp-atlassian:jira_get_issue` to identify: - Assignee (primary reviewer) - Reporter (stakeholder) - Watchers (additional reviewers) - Any reviewer names mentioned in comments ### Step 3: Draft Review Email Run `/pm-demo-email` to create the review email from project context and reviewer list. ### Step 4: Draft Meeting Invite Run `/pm-meeting-invite` to create the meeting invite for the review session. Use reference-style links (URLs at bottom) to keep the body scannable. ### Validate Show both full drafts to the user. Ask: "Do these look good? Should I save them to files?" **Do NOT save to disk until the user confirms.** After confirmation, save: - `demo/Demo_Showcase_Email.md` — email draft - `Meeting_Invite_[Type]_Review.md` — meeting invite ## Expected Input Path to project folder containing README.md, test_plan/, test_cases/, and confluence/ files.

Frequently asked questions