test-plan-gen

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):

1. Output format: ".docx or .pdf?"
2. Project overview: "Brief description of the project and what part you're testing."
3. 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

1. Read the docx skill: Read /sessions/awesome-blissful-hypatia/mnt/.skills/skills/docx/SKILL.md
2. Use scripts/generate_test_plan.js; replace all placeholders with gathered interview content
3. Generate the .docx; if PDF requested: python scripts/office/soffice.py --headless --convert-to pdf <docx_path>
4. Validate: python scripts/office/validate.py <docx_path>
5. 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.js is missing, output structured markdown the user can paste into Word or Notion.

Workflow

1. Quick Setup — Confirm output format, get a project overview, and agree on which sections to include.
2. Guided Interview — Walk through each selected section one at a time; offer defaults at every step.
3. Document Generation — Assemble content, generate the .docx or .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.js is 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 .docx and instruct the user to export to PDF manually via Word or Google Docs

• Expected behavior: User receives a .docx file 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 .docx or .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