testing-plan

Generate a markdown QA test plan from branch diff versus main.

121|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/AgentSystemLabs/core --skill testing-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-plan
Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/testing-plan
Command: npx skills add https://github.com/AgentSystemLabs/core --skill testing-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents slow, guessy, or incomplete QA by generating a branch-specific manual testing plan with concrete, executable steps and expected results.

Core Features & Use Cases

  • End-to-end human QA checklist: Produces a structured markdown plan that a tester can follow in a browser/desktop app without needing the author.
  • Route- and actor-specific steps: Each step names the exact route/UI surface, which user to log in as, the action to take, and the expected outcome.
  • Change-grounded regression coverage: Includes edge cases and regression checks tied to the diff versus main so refactors don’t silently break neighbors.
  • Use case: Generate a QA handoff for a new feature, bug fix, or refactor so reviewers can verify behavior before merge.

Quick Start

Ask the agent for a testing plan for your current branch so it writes a human-executable testing-plans/<slug>.md file covering golden-path steps, edge cases, and regression checks.

Frequently Asked Questions about testing-plan

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

FAQPage Schema
How do I generate a manual test plan for a feature branch before release?

Generate a manual test plan by analyzing the branch diff versus main to derive test surfaces and actor context, producing a markdown file with executable steps and expected results for human QA verification.

What is the best way to create a QA checklist for regression testing after a refactor?

Regression testing checklists for refactors should be change-grounded by deriving edge cases from the diff versus main, ensuring neighboring functionality doesn't silently break during manual verification.

Can I use this to write automated tests or add verification comments to pull requests?

No, this manual test plan generator specifically avoids automated-test authoring and PR-comment verification use cases, focusing solely on producing human-executable markdown steps for browser or desktop app testing.

How do I ensure my QA testing plan includes route-specific and actor-specific steps?

Route-specific manual test plans derive exact UI surfaces and login actor context from the branch diff, naming the specific route, user role, action, and expected outcome for each unambiguous testing step.

Does this test planning tool require any specific testing frameworks or dependencies?

No dependencies are required; the tool generates a standalone markdown QA test plan file that a human tester can execute against the current branch without needing the author or additional frameworks.

When do I need a manual verification test plan instead of automated tests?

A manual verification test plan is needed when handing off QA for new features, bug fixes, or refactors to reviewers who must verify behavior in a browser or desktop app before merge.