As a dynamic language, Perl doesn't require you to define subroutines until
run-time. Although this is a powerful feature, it can also be a major
source of bugs. For example, you might mistype the name of a subroutine, or
call a subroutine from another module without including that module or
importing that subroutine. And unless you have very good test coverage, you
might not know about these bugs until you have already launched your code.

The the Perl::Critic::Policy manpage modules in this distribution are aimed
at reducing errors caused by invoking subroutines that are not defined.
Each Policy can be used separately. But when applied together, they enforce
a specific and deliberate coding style that minimizes the chance of writing
code that makes calls to undefined subroutines.

This coding style will not appeal to everyone. Some folks will surely find
this coding style to be too verbose or too restrictive. In particular,
importing via the Exporter manpage tags and pattern matching is purposely
not supported. But hopefully, these Policies will encourage you to
consciously consider the inherent trade-offs of your current coding style.