testing-plan

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.