skills.rest
ehaimov-dn
ehaimov-dnCOMMUNITY
Explore all skills by this author →
GitHub

Test Plan Generator

Convert Jira tickets into executable test plans using linked project data.

Updated Aug 27, 2026
Search Tags:#github#qa#jira#confluence#network-topology#test-plan
One-click install
npx skills add https://github.com/ehaimov-dn/monitorAPP --skill test-plan-generator-ehaimov-dn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Test Plan Generator
Source: https://github.com/ehaimov-dn/monitorAPP/tree/main/.cursor/skills/test-plan-generator
Command: npx skills add https://github.com/ehaimov-dn/monitorAPP --skill test-plan-generator-ehaimov-dn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert Jira tickets into comprehensive, actionable test plans by aggregating data from Jira issues and epics, Confluence design docs, GitHub PRs, CLI documentation, and live network topology via the DNOS MCP server.

Core Features & Use Cases

  • Ingest Jira tickets (titles, descriptions, acceptance criteria) and summarize them into test objectives.
  • Cross-reference Confluence design docs, GitHub PRs, and CLI docs to build complete test scenarios.
  • Produce a ready-to-execute test plan with test cases, edge cases, prerequisites, and validation steps for QA.

Quick Start

Provide a Jira ticket key to generate a full test plan from all connected sources.

Frequently Asked Questions about Test Plan Generator

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

FAQPage Schema
How do I generate a test plan from a Jira ticket automatically?▼

Generating a test plan from a Jira ticket involves ingesting ticket titles, descriptions, and acceptance criteria, then cross-referencing Confluence docs and GitHub PRs to produce executable test cases, prerequisites, and validation steps.

Can I cross-reference Confluence design docs when creating QA test cases?▼

Cross-referencing Confluence design docs allows you to aggregate embedded links and development metadata with Jira issues, ensuring generated QA test scenarios cover comprehensive edge cases and validation steps.

What data sources are needed to create executable test cases from Jira issues?▼

Required data sources include Jira issues and epics, Confluence design docs, GitHub PRs, CLI documentation, and live network state, all aggregated to produce accurate, actionable test plans with validation steps.

Does generating a test plan from Jira require live network topology data?▼

Live network topology data is required via the network-mapper MCP server to aggregate current network state with Jira issues and GitHub PRs, producing test plans with accurate edge cases and validation steps.

How do I include GitHub PR metadata in my QA test plan generation?▼

Including GitHub PR metadata in QA test plan generation aggregates development metadata from GitHub APIs with Jira issues and Confluence docs, producing structured test cases and edge conditions.

What is the best way to turn Jira acceptance criteria into structured test cases?▼

Turning Jira acceptance criteria into structured test cases requires ingesting Jira issues and cross-referencing Confluence docs and CLI documentation to output executable test cases, edge conditions, and validation steps.

Related Skills

Explore More Software Engineering Skills→
lekmanlekman

atlassian-mcp

Configure and manage Atlassian MCP server integrations for Jira and Confluence.

Community
Advanced
zeropoint-foundationzeropoint-foundation
1

qa-review

Analyzes code changes to generate test plans and assess regression risk.

Community
Advanced
jongiojongio
6

azure-resource-visualizer

Analyze Azure resource groups to generate Mermaid architecture diagrams.

Community
Advanced
jamesrochabrunjamesrochabrun
194

qa-test-planner

Generate QA test plans, manual cases, regression suites, and bug reports.

Community
Advanced