test-plan

Generate formal test plans from implementation and design documents.

Updated Jan 31, 2026

Search Tags:#planning #testing #documentation #QA #software-development #test-case #test-plan

Ready to run

npx skills add https://github.com/tacogips/git-xnotes --skill test-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-plan
Source: https://github.com/tacogips/git-xnotes/tree/main/.claude/skills/test-plan
Command: npx skills add https://github.com/tacogips/git-xnotes --skill test-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Test Plan Skill helps teams create structured test plans from implementation and design documents, ensuring traceability, coverage, and progress tracking across features and releases.

Core Features & Use Cases

Guided test-plan creation: Provides a consistent template for unit, integration, and e2e plans aligned to project standards.
Divided planning and tracking: Enables granular test cases and progress monitoring across sessions.
Implementation reference integration: Links to impl-plans and source files to maintain alignment between code and tests.

Quick Start

Create a new plan under test-plans/<feature>-unit.md and begin by filling in header metadata, implementation reference, and test-cases sections.

Frequently Asked Questions about test-plan

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

FAQPage Schema

How do I generate a structured test plan from implementation and design documents?▼

To generate a structured test plan from implementation and design documents, use a divide-and-conquer workflow that imposes plan structure with headers, environment details, test cases, status, and progress tracking, storing outputs under test-plans/.

What is the best way to break down features into testable units for QA coverage?▼

Breaking down features into testable units for QA coverage requires applying a divided planning approach that generates granular test cases and enforces consistent templates aligned to project standards for unit, integration, and e2e plans.

Can I track test plan progress across multiple QA sessions?▼

Yes, you can track test plan progress across multiple QA sessions by storing plans under test-plans/<feature>-unit.md and maintaining status and progress sections within the plan structure for continuous monitoring.

Does test planning work with existing impl-plans and source files?▼

Test planning works with existing impl-plans and source files by integrating implementation references directly into the test plan, which maintains alignment between code and tests while ensuring traceability and coverage.

How do I create a new test plan with proper header metadata and test cases?▼

To create a new test plan with proper header metadata and test cases, start by creating a file under test-plans/<feature>-unit.md and fill in the header metadata, implementation reference, and test-cases sections to establish a structured baseline.