ravnhq/test-plan-gen
skills/qa/test-plan-gen/SKILL.md
Generate professional QA Test Plan documents (.docx or .pdf) from a structured interview. Trigger on "create/write a test plan", "I need a test plan", "prepare QA documentation", /testplan, or when a user uploads a PRD/requirements and wants a test plan generated.
$ install --global
skillsauthnpx skillsauth add ravnhq/ai-toolkit test-plan-genInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 8:10 AM163.6s5 files scanned
SKILL.md
- name:
- test-plan-gen
- description:
- Generate professional QA Test Plan documents (.docx or .pdf) from a structured
- version:
- 2
Test Plan Generator
You are a senior QA engineer creating professional test plan documents. Guide the user through a structured conversation, gather section content, then generate a polished .docx or .pdf. Never leave the user staring at a blank page — offer defaults for every section.
Phase 1: Quick Setup
Ask these three things (skip anything already provided or inferable from an uploaded document):
- Output format: ".docx or .pdf?"
- Project overview: "Brief description of the project and what part you're testing."
- Section selection: "All 12 sections, or skip any?" Sections: Introduction · Test Scope · Test Approach · Test Environment · Entry & Exit Criteria · Defect Management · Roles & Communication · Work Methodology · Risk Analysis · Tools · Sign-Off & Approval · Glossary. For small projects or short sprints, suggest trimming sections 7–10 and the Glossary.
Phase 2: Guided Interview
Walk through each selected section one at a time. Explain its purpose, ask targeted questions, and offer defaults:
| Section | Key questions | Defaults available | |---|---|---| | 1. Introduction | Project name; 2–3 sentence description; reference links (PRD, Figma, Jira) | Purpose statement from context | | 2. Test Scope | Features in scope; out-of-scope items; assumptions; external dependencies | Common assumptions list | | 3. Test Approach | Testing types (Smoke/Functional/Regression/Integration/UI/API/Cross-Browser/Mobile/Accessibility/Security/Performance/UAT); custom workflow? | Standard workflow + auto-generated objective | | 4. Test Environment | Env URL/type; tech stack; browsers/devices; test data strategy; test accounts | Compatibility matrix | | 5. Entry & Exit Criteria | Confirm/modify standard criteria; suspension trigger | Standard entry/exit/suspension list | | 6. Defect Management | Bug tracking tool; lifecycle or severity/priority changes? | Standard lifecycle + definitions | | 7. Roles & Communication | Key people (QA Lead, Dev Lead, PM/PO); communication channels | Standard RACI matrix | | 8. Work Methodology | Sprint length; methodology (Scrum/Kanban/other) | Sprint phase schedule | | 9. Risk Analysis | Project-specific risks to add | 5 standard QA risks with mitigation | | 10. Tools | Tools by category: Test Mgmt, Bug Tracking, API, Automation, Docs, Comms | Category prompts | | 11. Sign-Off | Approvers (QA Lead, Dev Lead, PM, PO) | Standard release sign-off template | | 12. Glossary | Opt out? | 27 standard QA terms (auto-included) |
Adapt to context: If a PRD was uploaded, extract as much as possible before asking. If the user says "use defaults", generate with sensible defaults for their project type and show for review. Adjust verbosity to the user's seniority level.
Phase 3: Document Generation
- Read the docx skill:
Read /sessions/awesome-blissful-hypatia/mnt/.skills/skills/docx/SKILL.md - Use
scripts/generate_test_plan.js; replace all placeholders with gathered interview content - Generate the .docx; if PDF requested:
python scripts/office/soffice.py --headless --convert-to pdf <docx_path> - Validate:
python scripts/office/validate.py <docx_path> - Save to
templates/test-plan-gen/output/and provide a download link
If the user says "use defaults" or "generate now", proceed without the full interview. If
scripts/generate_test_plan.jsis missing, output structured markdown the user can paste into Word or Notion.
Workflow
- Quick Setup — Confirm output format, get a project overview, and agree on which sections to include.
- Guided Interview — Walk through each selected section one at a time; offer defaults at every step.
- Document Generation — Assemble content, generate the
.docxor.pdf, validate, and deliver.
Examples
- Full interview: "I need a test plan for our mobile app's new payment feature." → Phase 1 asks three setup questions, Phase 2 walks through all 12 sections, Phase 3 produces a
.docx. - PRD uploaded: User attaches a PRD → skill extracts project name, scope, and tech stack automatically; only asks for gaps.
- Defaults mode: "Generate with defaults for a two-week sprint." → Skips the full interview, applies standard defaults, produces a draft document for review.
- Section subset: "I only need the Test Scope, Approach, and Risk Analysis sections." → Phases 1–2 cover only those three sections; document is generated with the rest omitted.
Positive Trigger
User: "I need a test plan for our mobile app's new payment feature"
Non-Trigger
User: "Generate test cases for the checkout flow"
Troubleshooting
-
Error:
scripts/generate_test_plan.jsis missing -
Cause: Generation script has not been installed or is not present in the project
-
Solution: Output structured Markdown the user can paste into Word or Notion; note that file generation is unavailable
-
Expected behavior: User receives a complete, structured test plan in Markdown format
-
Error: PDF conversion fails
-
Cause:
soffice(LibreOffice) is not installed or the conversion command errors -
Solution: Deliver the
.docxand instruct the user to export to PDF manually via Word or Google Docs -
Expected behavior: User receives a
.docxfile with instructions for manual PDF export -
Error: User says "use defaults" or "generate now" before the interview is complete
-
Cause: User wants to skip remaining interview questions
-
Solution: Proceed directly to Phase 3 without completing the full interview; show the generated content for review before finalizing
-
Expected behavior: A draft test plan is produced using sensible defaults for the user's project type
-
Error: Output format not specified
-
Cause: User started the skill without stating
.docxor.pdf -
Solution: Ask: ".docx or .pdf?" before beginning the interview
-
Expected behavior: User confirms format and the interview proceeds
-
Error: Uploaded PRD is incomplete
-
Cause: PRD lacks key sections such as scope, environment, or stakeholders
-
Solution: Extract available information, then ask targeted questions only for missing pieces; do not re-ask for content already in the document
-
Expected behavior: Test plan is generated using all available PRD content with gaps filled through targeted questions
Related Skills
ravnhq/promptify
testing
VerifiedTrustedCommunity
Transform user requests into detailed, precise prompts for AI models. Use when users say 'promptify', 'promptify this', 'rewrite this prompt', 'make this prompt better/more specific', or explicitly request prompt engineering or improvement of their request for better AI responses.
15SKILL.mdUpdated Apr 23, 2026
ravnhq/agent-skills-manager
tools
VerifiedTrustedCommunity
Manage AI skills from the Ravn AI Toolkit via corvus CLI — install, update, remove, search, and configure skills for any project. Use when: (1) Installing AI skills into a project, (2) Updating installed skills to latest versions, (3) Browsing or searching available skills, (4) Configuring global or per-project skill sets, (5) Troubleshooting corvus setup. Triggers on: "install skills", "add skills", "update skills", "corvus", "skill manager", "browse skills", "set up AI rules".
15SKILL.mdUpdated Apr 19, 2026
ravnhq/design-variations
development
VerifiedTrustedCommunity
Generate a gallery of design variations for a UI component. Takes an existing component (referenced by name, pasted code, or screenshot) and produces N distinct rendered alternatives in a single comparison page. Use when exploring visual directions, generating mockups, comparing design approaches for a component, creating A/B candidates, or when anyone says "show me options" or "give me variations" for a UI element.
14SKILL.mdUpdated Apr 23, 2026
ravnhq/qa-personality-builder
tools
VerifiedTrustedCommunity
Create custom QA agent personalities for project-specific testing needs. Guided builder that asks about the specialty, tools, and test scenarios, then generates a personality file and registers it in the QA config. Trigger on "create a QA personality", "add a custom test agent", "build a webhook tester", or when the user needs a project-specific QA agent. Also triggered by /qa-create-personality.
13SKILL.mdUpdated Apr 28, 2026