skills.rest
civitas-cerebrum
civitas-cerebrumOFFICIAL
Explore all skills by this author →
GitHub

coverage-expansion

Coordinate journey-level test coverage expansion across a mapped application.

7|7|Updated Mar 9, 2026
Search Tags:#orchestration#coverage#e2e-testing#journeys#regression-tests#bug-discovery
One-click install
npx skills add https://github.com/civitas-cerebrum/element-interactions --skill coverage-expansion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coverage-expansion
Source: https://github.com/civitas-cerebrum/element-interactions/tree/main/skills/coverage-expansion
Command: npx skills add https://github.com/civitas-cerebrum/element-interactions --skill coverage-expansion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Iteratively expand end-to-end test coverage across an entire mapped application by coordinating per-journey planning, execution, and discovery.

Core Features & Use Cases

  • Orchestrates journey-by-journey test growth across a mapped app, coordinating with test-composer and bug-discovery subsystems.
  • Supports depth and breadth modes, enabling either comprehensive adversarial probing or fast coverage sweeps.
  • Reconciles discoveries across journeys, maintains a centralized adversarial findings ledger, and produces regression tests for validated boundaries.

Quick Start

Invoke coverage-expansion in depth mode to start iterative journey-by-journey test growth.

Frequently Asked Questions about coverage-expansion

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

FAQPage Schema
How do I expand end-to-end test coverage across a mapped application?▼

End-to-end test coverage expands by orchestrating journey-by-journey test growth, coordinating planning, execution, and discovery passes across a mapped app to iteratively increase breadth and depth.

What is the difference between depth and breadth modes for e2e testing?▼

Depth mode enables comprehensive adversarial probing of journeys, while breadth mode performs quick coverage sweeps across the application to balance thoroughness and speed.

How are regression tests generated from discovered bugs?▼

Validated boundary findings are reconciled into a centralized adversarial findings ledger, which then produces regression tests to enforce map-driven progression and per-journey isolation.

Can I run coverage sweeps without per-journey isolation?▼

Per-journey isolation is enforced to ensure stable, auditable expansion, meaning coverage sweeps and adversarial probing operate within isolated journey boundaries rather than globally.

When do I need centralized adversarial findings for regression testing?▼

A centralized adversarial findings ledger is needed when reconciling discoveries across multiple journeys to produce regression tests and maintain auditable end-to-end coverage growth.

Does coverage expansion work without a mapped application structure?▼

Coverage expansion requires a mapped application to enforce map-driven progression, coordinating journey-level passes and discoveries against the existing structural map.

Related Skills

Explore More Software Engineering Skills→
civitas-cerebrumcivitas-cerebrum
7

journey-mapping

Generates a prioritized journey map with sub-journeys and test expectations from a web application.

Official
Advanced
Agile-VAgile-V
50

red-team-verifier

Execute independent tests against Build Agent artifacts to validate requirements compliance.

Official
Advanced
civitas-cerebrumcivitas-cerebrum
7

onboarding

Orchestrate autonomous onboarding of new apps to the element-interactions framework.

Official
Advanced
clovernguyen1010-ship-itclovernguyen1010-ship-it

bmad-agent-qa

Generate API and E2E tests for existing features using standard test frameworks.

Community
Intermediate