skills.rest
Pythagora-io
Pythagora-ioOFFICIAL
Explore all skills by this author →
GitHub

qa-phase2

Expand QA testing plans by generating bug hypotheses and adding API and browser tests.

9|3|Updated Apr 14, 2026
Search Tags:#qa#test-cases#api-tests#testing-plan#browser-tests#phase2#bug-hypotheses
One-click install
npx skills add https://github.com/Pythagora-io/agent-templates --skill qa-phase2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-phase2
Source: https://github.com/Pythagora-io/agent-templates/tree/main/QA%20Agent/qa-phase2
Command: npx skills add https://github.com/Pythagora-io/agent-templates --skill qa-phase2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 2: Review the existing testing plan with the knowledge gained from Phase 1 (PR diff, code changes, environment state). Generate bug hypotheses and expand the plan if needed. Never make the plan shorter — only add.

Core Features & Use Cases

  • Re-read the Testing Plan: Read both {testFolder}/testing-plan.md and {testFolder}/test-cases.json to understand every test case (API and browser), its priority, and its steps.
  • Load Cross-Cutting Test Strategies: Based on the change type (from Phase 1), load relevant strategies from {KNOWLEDGEBASE_PATH}/test-strategies/:
  • Generate Bug Hypotheses: Think adversarially. Combine PR analysis with knowledge base including patterns in bugs/patterns.md and historical issues from platform docs.
  • Expand the Testing Plan: Add new test cases to {testFolder}/test-cases.json (API tests → add to apiTests; browser tests → add to browserTests). Mark all new tests as "PENDING" and do not modify existing tests.
  • Update Plan Meta & Share: Update the status in test-cases.json to PHASE2 and share the plan with the team for review.

Quick Start

Load the Phase 2 skill, review Phase 1 insights, and begin expanding the testing plan by adding new test cases.

Frequently Asked Questions about qa-phase2

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

FAQPage Schema
How do I expand a QA testing plan with bug hypotheses after reviewing code changes?▼

To expand a QA testing plan, review the existing testing-plan.md and test-cases.json, load cross-cutting test strategies from your knowledge base, generate adversarial bug hypotheses, and append new pending API or browser tests without modifying existing cases.

What are bug hypotheses in QA testing and how do they improve test coverage?▼

Bug hypotheses are adversarial predictions of potential software failures derived by combining PR analysis with historical bug patterns. They improve test coverage by identifying untested risk areas and prompting the addition of targeted API and browser tests to the testing plan.

Can I add both API tests and browser tests to test-cases.json during QA plan expansion?▼

Yes, you can add both API and browser tests during QA plan expansion. New API tests are appended to the apiTests array and browser tests to the browserTests array in test-cases.json, with all new entries marked as PENDING status.

Does expanding a testing plan modify or remove existing test cases?▼

Expanding a testing plan never modifies or removes existing test cases. The process enforces appending only new tests to test-cases.json to augment coverage, while keeping the original testing-plan.md completely intact.

How do I apply cross-cutting test strategies from a knowledge base to a staging environment?▼

To apply cross-cutting test strategies, load relevant strategy files from your KNOWLEDGEBASE_PATH based on the change type identified in Phase 1. These strategies guide the generation of bug hypotheses and new test cases tailored for QA, staging, or production environments.

What is the best way to track the status of newly added test cases in a QA plan?▼

The best way to track newly added test cases is to mark them as PENDING in test-cases.json and update the overall plan status to PHASE2. This ensures the team can review the expanded coverage and distinguish new tests from existing ones.

Related Skills

Explore More Software Engineering Skills→
Pythagora-ioPythagora-io
9

qa-phase3

Run API and browser tests from test-cases.json with real-time status updates.

Official
Advanced
dogkeeper886dogkeeper886

executing-tests

Execute TestLink test cases in a browser and produce pass/fail reports.

Community
Intermediate
Nathanto-aiNathanto-ai

black-box-red-testing

Generate deterministic adversarial red tests targeting distinct bug hypotheses.

Community
Advanced
aibangjuxinaibangjuxin
2

api-tester

Test RESTful APIs with manual and automated scripts.

Community
Intermediate