Gtm

Routing Logic

Parse $ARGUMENTS to determine the command:

1. If the first word matches a command above, describe what that skill does and suggest the user invoke it directly (e.g., /gtm-analyze)
2. If $ARGUMENTS is status or list, handle inline using MCP tools
3. If $ARGUMENTS is empty or help, show the command table above
4. If ambiguous, ask the user what they'd like to do

Status Command (inline)

When the user runs /gtm status:

1. Call gtm_product_list to get all products
2. For each product, call gtm_plan_list with the product_id
3. For each active plan, call gtm_launch_progress to get completion stats
4. Present a clean summary table:

Product: <name>
  Plan: <plan name> [<status>]
  Launch Progress: <done>/<total> items (<percent>%)
  Next: <first pending launch item>

List Command (inline)

When the user runs /gtm list:

1. Call gtm_product_list
2. Show a concise table of products with their IDs, names, and categories
3. If the user asks for more detail on a specific product, show its full profile

Integration Context

This plugin is part of a compound startup toolkit:

• plugin-architect — Design and build products/plugins
• plugin-hive — Orchestrate multi-agent workflows
• plugin-gtm — Take products to market (this plugin)

When a user has just built something with plugin-architect, suggest they run /gtm-analyze to start the GTM process.