goat-flow

Use when evaluating test coverage gaps, planning test strategy, or assessing testing risk for code changes.

Use when reviewing a diff, PR, or set of code changes, or auditing a codebase area for quality issues. Triggers: 'review this', 'code review', 'audit X', 'look at these changes'.

Use when assessing security implications of code changes, architecture decisions, or new features.

Use when starting a non-trivial implementation that needs structured task breakdown with progress tracking.

Use when you describe an outcome and need the right goat-* workflow chosen for you.

Use when a decision or analysis needs multi-lens critique to surface blind spots before shipping.

Use when diagnosing a bug, unexpected behaviour, system failure, or unfamiliar code that needs structured investigation.

Fixture skill used by reference-plumbing tests.