qa

Generate step-by-step test plans for newly implemented features.

562|80|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/kdlbs/kandev --skill qa-kdlbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/kdlbs/kandev/tree/main/.agents/skills/qa
Command: npx skills add https://github.com/kdlbs/kandev --skill qa-kdlbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that a feature works as intended after implementation. Assume bugs exist and hunt for them.

Core Features & Use Cases

  • Understand intent and verify coverage
  • Trace wiring: ensure exports, routes, and data flows are hooked end-to-end
  • Test the happy path and break edge cases, including concurrency and authorization

Quick Start

Describe a feature and ask the QA skill to generate a step-by-step test plan.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I generate a test plan for newly implemented features?

To generate a test plan for newly implemented features, describe the feature intent and the system will produce step-by-step validation steps, covering happy paths, edge cases, and error paths.

What is bug hunting through edge-case validation in software testing?

Bug hunting through edge-case validation is the process of actively attempting to break features by testing boundary inputs, concurrency, and error paths to assume bugs exist and find them before release.

Can I use this approach to verify both backend and frontend changes?

Yes, you can use this approach to verify both backend and frontend changes, as it applies across workflows, APIs, integrations, and edge-case scenarios to ensure data flows are hooked end-to-end.

How do I trace data flow wiring to ensure exports and routes are hooked correctly?

To trace data flow wiring, verify that exports, routes, and data flows are hooked end-to-end by testing the integration points and ensuring the feature works as intended after implementation.

Does this validation method cover concurrency and authorization edge cases?

Yes, this validation method covers concurrency and authorization edge cases by actively attempting to break features through boundary inputs and error paths beyond the happy path.