Indeed Moose Roles can do this kind of thing easily.

First we start with your basic "TextClass" class:

package TextClass;
use Moose;

has 'text' => (
    is  => 'rw',
    isa => 'Str',
);

with 'PrettyPrint';

no Moose;
__PACKAGE__->meta->make_immutable;
1;
[download]

Note the with 'PrettyPrint'; That is the module which contains the role we will add.

We make another module to implement the "prettyprint" role:

package PrettyPrint;
use Moose::Role;

requires 'text';

sub prettyprint {
    my $self = shift;
    print "So handsome:\n\t", $self->text, "\nYeah, sure!\n";
    $self;
}
1;
[download]

The prettyprint sub from this module will now become a method in your 'TextClass' class or any other class that provides a text method. That is what the requires 'text' takes care of. Use this role in another class that doesn't provide the text method and it will complain and end the compilation of your script.

As you see, the methods in your Role-module have access to all the public methods of your object, even those which are provided auto-magically by Moose itself, such as the getters and setters, in this case the text method.

Using all this now is standard:

use Modern::Perl qw/2014/;
use lib 'D:/Perl/scripts';    # or wherever you have saved the modules

use TextClass;

my $person = TextClass->new( text => q/I'm CountZero/ );

$person->prettyprint;
[download]

Output:

So handsome:
    I'm CountZero
Yeah, sure!
[download]

Note, that a Role isn't a class: it cannot be instantiated on its own, it will not provide its own objects. Rather it is a bunch of subroutines that get directly included in your basic class without any intermediary object. So you do not do $text->PrettyPrint::prettyprint or $text->PrettyPrintObject->prettyprint

Update: clarified about adding a Role module.