qa

Generate risk-based test scenarios, seam tests, and coverage matrices aligned with architecture plans.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/djwmobley/pipeline --skill qa-djwmobley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/djwmobley/pipeline/tree/main/skills/qa
Command: npx skills add https://github.com/djwmobley/pipeline --skill qa-djwmobley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lead QA professionals plan and verify tests that uncover risks at component boundaries, ensuring changes are safe and valuable.

Core Features & Use Cases

  • Inline QA planning inside the implementation plan (MEDIUM)
  • Standalone QA planning for LARGE/MILESTONE initiatives (full test plans)
  • Verify mode with targeted checks and seam tests to protect critical boundaries
  • Seam tests and work-package decomposition to enable scalable, parallel QA work

Quick Start

Run the QA planner to generate the test plan inline during /pipeline:plan, then review the resulting QA section and adjust as needed.

Frequently Asked Questions about qa

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

FAQPage Schema
What is seam testing and how does it identify risks at component boundaries?▼

Seam testing is a verification strategy that isolates component boundaries to uncover integration risks. It ensures test coverage specifically targets critical interaction points, preventing unsafe changes from propagating through the system architecture.

How do I plan a test strategy for a large software milestone?▼

To plan a test strategy for large milestones, generate a standalone QA plan that decomposes work into parallel packages. This creates risk-based test scenarios and coverage matrices aligned with your architecture to ensure safe, scalable verification.

Can I generate inline QA plans during feature implementation?▼

Yes, you can generate inline QA plans during feature implementation. This integrates risk-based test scenarios directly into the implementation pipeline, allowing you to review and adjust coverage for medium-sized tasks efficiently.

What is the best way to decompose test plans for parallel QA work?▼

The best way to decompose test plans is using work-package decomposition. This breaks down large test strategies into isolated, scalable units, enabling parallel QA execution while maintaining rigorous boundary verification.

When should I use standalone QA planning instead of inline mode?▼

Use standalone QA planning for large or milestone initiatives requiring comprehensive test plans and coverage matrices. Inline mode is better suited for medium-sized feature implementations where risk assessment integrates directly into the pipeline.