# Coordinate Software Test Coverage

Teams often miss test gaps when unit, integration, end-to-end, and performance work are planned separately. This skill helps Claude, Codex, and Claude Code organize testing priorities, coverage targets, quality gates, and reporting.

## Install

```bash
npx skillstore add brownbull/test-orchestrator
```

## Metadata

- - Slug: brownbull-test-orchestrator
- - Version: 1.0.0
- - Author: Brownbull
- - GitHub username: Brownbull
- - License: MIT
- - Repository: https://github.com/Brownbull/ayni\_core/tree/main/.claude/skills/test-orchestrator
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Quality score: 77
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/brownbull-test-orchestrator
- - Manifest: https://skillstore.pages.dev/api/skills/brownbull-test-orchestrator/manifest

## Capabilities

- Creates test plans across unit, integration, end-to-end, performance, and security categories.
- Defines coverage goals, acceptance criteria, and quality gate expectations.
- Coordinates testing tasks across specialized test skills or testing roles.
- Reviews test failures, coverage metrics, and flaky test indicators.
- Documents test plans, result summaries, and quality metrics for project handoff.

## Use Cases

- Plan Release Testing: Create a structured test plan before a release, including scope, risk areas, coverage goals, and acceptance criteria.
- Coordinate Test Implementation: Break testing work into unit, integration, end-to-end, performance, and security tasks for a feature team.
- Review Quality Gates: Evaluate failures, coverage gaps, flaky tests, and build-blocking conditions before merging a change.

## Prompt Templates

### Create a Basic Test Plan

```
Create a test plan for this feature. Include unit, integration, end-to-end, performance, and security checks. Define acceptance criteria and coverage goals.
```

### Find Coverage Gaps

```
Review the current tests and identify coverage gaps. Group findings by test type, risk level, and recommended next action.
```

### Coordinate Test Work

```
Convert this feature scope into testing tasks. Assign each task to the right testing category and include expected inputs, outputs, and completion criteria.
```

### Design a Quality Gate

```
Design a quality gate for this release. Include required test suites, coverage thresholds, failure handling, flaky test policy, and release-blocking conditions.
```

## Limitations

- It provides testing guidance and coordination, not a runnable test framework.
- It does not include scripts, fixtures, or project-specific test commands.
- It relies on the user or agent to inspect the target codebase before implementation.
- It does not verify real coverage unless test results are provided.

## Best Practices

- Provide feature scope, risk areas, existing test results, and coverage targets before asking for a plan.
- Keep quality gates measurable with clear pass or fail criteria.
- Review flaky tests separately from product failures so release risk is visible.

## Anti Patterns

- Do not ask for broad test coverage without naming the component or user flow.
- Do not treat coverage percentage as proof that critical behavior is tested.
- Do not ignore failing or flaky tests when defining release readiness.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T17:50:47.988\+00:00
- - Summary: The static analyzer flagged Markdown backticks, ordinary documentation text, and example code as risky patterns. Manual review found no executable skill code, no command execution instruction, no weak cryptographic implementation, and no prompt injection attempt.

## Stats

- - Views: 224
- - Downloads: 4
- - Favorites: 0
- - Popularity score: 0