planning-tests

Detect ticket types and generate test plans for Confluence publication.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/dogkeeper886/ai-qa-workflow --skill planning-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-tests
Source: https://github.com/dogkeeper886/ai-qa-workflow/tree/main/skills/planning-tests
Command: npx skills add https://github.com/dogkeeper886/ai-qa-workflow --skill planning-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a complete test plan from a project folder by detecting the ticket type, writing test plan sections, reviewing coverage, and publishing to Confluence. Use when a QA engineer wants to plan tests, create a test plan, write a test plan, or start test planning for a project.

Core Features & Use Cases

  • Detect ticket type and route to the appropriate planning command.
  • Write test plan sections to test_plan/ and review coverage with matrices and diagrams.
  • Publish test plans to Confluence pages using MCP tools for collaborative review.

Quick Start

Run the planning-tests workflow on a project folder to generate and publish the test plan to Confluence.

Frequently Asked Questions about planning-tests

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

FAQPage Schema
How do I generate a QA test plan from existing Jira tickets?

To generate a QA test plan from Jira tickets, apply this workflow to your project folder to automatically detect ticket types, write structured test plan sections, and review coverage matrices for features, bugs, and enhancements.

What is the best way to publish a test plan to Confluence for team review?

The best way to publish a test plan to Confluence is using MCP tools that automatically create collaborative review pages directly from your generated test_plan/ directory sections.

How does test coverage review work when planning tests for multiple ticket types?

Test coverage review works by generating matrices and diagrams that map detected ticket types—features, bugs, and enhancements—against written test plan sections to identify gaps in your project folder.

Can I use this test planning workflow for both new features and bug fixes?

Yes, you can use this test planning workflow for both new features and bug fixes; it detects the specific ticket type in your project folder and routes to the appropriate planning command.

Do I need any dependencies installed to write test plan sections to my project?

No dependencies are required to write test plan sections; the workflow operates directly on your project folder to detect ticket types and outputs structured files to the test_plan/ directory.

What limitations exist when automating test plan creation from project folders?

A limitation of automating test plan creation is that it requires properly structured input prerequisites in your project folder to accurately detect ticket types and satisfy the conditions needed to write valid test plan sections.