test-plan-generation

Generate IEEE 829 and ISTQB aligned Test Plans and Test Cases with traceability.

5|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/tercel/spec-forge --skill test-plan-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-plan-generation
Source: https://github.com/tercel/spec-forge/tree/main/skills/test-plan-generation
Command: npx skills add https://github.com/tercel/spec-forge --skill test-plan-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generates comprehensive Test Plans and Test Cases aligned with IEEE 829 and ISTQB standards to ensure consistent QA coverage across projects.

Core Features & Use Cases

  • Six-step workflow guiding the end-to-end creation of test artifacts from project scan to RTM generation.
  • Template-driven output that references references/template.md and validates against references/checklist.md to ensure completeness.
  • Built-in traceability with a Requirements Traceability Matrix and inline Mermaid diagrams to illustrate test scope and coverage.

Quick Start

Provide a feature name or project context to generate a complete Test Plan and Test Cases set for that scope.

Frequently Asked Questions about test-plan-generation

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

FAQPage Schema
How do I generate an IEEE 829 test plan from project requirements?

To generate an IEEE 829 test plan, provide a feature name or project context to scan upstream requirements and produce traceable, ready-to-use QA documentation including test cases and a traceability matrix.

What is a Requirements Traceability Matrix and does this workflow include it?

A Requirements Traceability Matrix (RTM) maps upstream requirements to test coverage. This workflow includes built-in RTM generation alongside inline Mermaid diagrams to visually illustrate test scope and coverage.

Can I use ISTQB best practices for test case generation with this approach?

Yes, test case generation follows ISTQB and Google Testing Blog best practices, validating outputs against a formal checklist to ensure completeness and standardized QA documentation.

What is the best way to automate test plan documentation for a new feature?

Automating test plan documentation uses a template-driven six-step workflow that scans the project, identifies requirements, and outputs executable test cases ready to load into a documentation repository.

Do I need a checklist to validate IEEE 829 test plans?

Yes, validating IEEE 829 test plans requires a formal checklist to ensure completeness. The workflow references a built-in checklist file to validate the generated test artifacts before use.