Prisoner is correct, but there are some implementation details that will trip you up if you are not careful.
If you wanted to [pig]gyback on play a game you would add this to your manifest, inside the intent for your main activity or service (if using a live card):
<meta-data
android:name="com.google.android.glass.VoiceTrigger"
android:resource="@xml/voice_trigger_start" />
And in voice_trigger_start.xml put this:
<?xml version="1.0" encoding="utf-8"?>
<trigger command="PLAY_A_GAME" />
If you use keyword instead of command as you are supposed to do when launching from custom triggers in development mode, this technique will not work!
Also note that PLAY_A_GAME is not what will show, it will actually be "play a game with ...". This speaks to what Prisoner said about Glass having a different metaphor for how a user is supposed to think about interacting with Glass. See my post script for an interesting twist on this.
Finally make sure your app name is a good one. Generally this is stored in strings.xml as follows. Whatever your app name is will show in the launcher process.
<string name="app_name">Very Angry Birds</string>
At the Glass home screeen the user will say "ok glass, play a game, Very Angry Birds".
I tested this, and this is the result:
One last thing, if you are the only "game" in town, in other words if you are the only app installed with the PLAY_A_GAME command, then the way to launch very angry birds is now "play a game", there is no more "with...", it is hidden when there is only one app for the command. So make sure you have a title screen in case you are the only game in town so the user knows what he just launched.