test

Plan and scope testing work with coverage maps and prioritized task lists.

9|9|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill test-nullmastermind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/test
Command: npx skills add https://github.com/nullmastermind/viber-router --skill test-nullmastermind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers and teams scope, plan, and implement testing work by exploring coverage, strategy, and edge cases, turning ambiguous testing needs into prioritized, actionable test plans and optional spec artifacts.

Core Features & Use Cases

  • Exploration & Clarification: Use Feynman echo, targeted questions, and the Zero-Fog checklist to restate requirements and confirm scope before design.
  • Codebase Investigation: Map existing test structure and coverage, locate untested paths, surface flaky tests, and identify hidden complexity that needs testing.
  • Strategy Comparison & Recommendations: Compare unit vs integration vs E2E approaches, recommend mocking and test data strategies, and sketch tradeoffs between coverage and maintenance cost.
  • Deliverables: Produce coverage maps, edge-case matrices, mocking strategies, prioritized task lists, test implementation steps, and optional spec files for immediate handoff.
  • Use Case: For a new backend service, run discovery to generate a prioritized plan covering unit and integration tests, identify E2E spikes, and produce a checklist for CI integration.

Quick Start

Explore testing needs for the new auth service by mapping current coverage, identifying missing edge cases, and recommending a prioritized implementation plan.

Frequently Asked Questions about test

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

FAQPage Schema
How do I identify coverage gaps and plan a test strategy for a new codebase?

To identify coverage gaps and plan a test strategy, map the existing test structure, locate untested paths, and surface hidden complexity. This produces a prioritized test plan, coverage maps, and edge-case matrices for immediate implementation.

What is the best way to compare unit, integration, and E2E testing approaches?

Comparing unit, integration, and E2E testing approaches involves evaluating tradeoffs between coverage and maintenance cost. This analysis yields recommendations for mocking strategies and highlights edge cases across services and CI pipelines.

How do I generate a prioritized task list for test implementation?

Generating a prioritized task list for test implementation requires scoping testing work through codebase investigation and edge-case identification. The process outputs prioritized implementation steps and optional spec artifacts to guide the testing work.

Can I scope testing work for backend services and CI pipelines without existing specs?

Yes, you can scope testing work for backend services and CI pipelines without existing specs by using targeted questions to clarify requirements. This discovery process maps current coverage and generates a checklist for CI integration.

Why does my test planning miss critical edge cases across services?

Test planning misses critical edge cases across services when hidden complexity goes untested. Performing codebase investigation and generating an edge-case matrix surfaces these gaps, ensuring robust mocking strategies and comprehensive E2E coverage.