test-plan

Generate structured test plans from Linear tickets, GitHub PRs, or feature descriptions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Cottage-Energy/cottage-tests --skill test-plan-cottage-energy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-plan
Source: https://github.com/Cottage-Energy/cottage-tests/tree/main/.claude/skills/test-plan
Command: npx skills add https://github.com/Cottage-Energy/cottage-tests --skill test-plan-cottage-energy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating a comprehensive test plan from scattered inputs (tickets, PRs, feature descriptions) is time-consuming and error-prone; this Skill automates that process, surfacing dependencies, risks, and acceptance criteria to accelerate QA planning.

Core Features & Use Cases

  • Aggregates inputs from Linear, GitHub PRs, Notion tickets, and related references to produce a milestone-aligned test plan.
  • Performs PR analysis when a PR link is present to capture diffs, risk, and impacted tests.
  • Outputs a structured plan with sections for prerequisites, test data, edge cases, and a clear automation plan, ready for handoff to QA.
  • Supports Notion as an input source and can save or link the generated plan back to the ticket for traceability.

Quick Start

Provide a Linear ticket, GitHub PR, or feature description and let this Skill generate a complete test plan in the repository under tests/test_plans.

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 test plan from a GitHub PR and a Linear ticket?

Generate a test plan from a GitHub PR and a Linear ticket by providing both links to aggregate inputs and analyze diffs. The tool routes inputs based on accessibility to surface dependencies and output a structured plan with prerequisites and edge cases.

Can I use Notion tickets as an input source for QA test planning?

Yes, you can use Notion tickets as an input source for QA test planning. The tool aggregates Notion references alongside Linear tickets and PRs to produce milestone-aligned test plans that can be saved or linked back to the original ticket for traceability.

Does automated test planning identify blocking issues and dependencies?

Yes, automated test planning identifies blocking issues and dependencies. It surfaces required context and risks before writing test cases by performing PR analysis and routing inputs based on their accessibility to ensure comprehensive QA coverage.

What is the best way to structure test cases for QA handoff?

The best way to structure test cases for QA handoff is using a standardized template that includes prerequisites, test data, edge cases, and an automation plan. This ensures the generated test plan is ready for immediate QA execution and repository traceability.

Where are generated test plans saved in the repository?

Generated test plans are saved in the repository under the tests/test_plans directory. This ensures the structured output with acceptance criteria and automation plans remains version-controlled and directly traceable to the original feature inputs.