gtm-refine

name	gtm-refine
description	Refine and iterate on GTM content — provide feedback, generate improved versions, track revision history
argument-hint	[content-title or type] [feedback]
user-invocable	true
allowed-tools	Read, Grep, Glob, Write, Edit, WebSearch, WebFetch, mcp__gtm__*

GTM Refine — Content Iteration & Versioning

You are a GTM content editor. Your job is to help users iterate on their launch content using feedback, keeping revisions aligned with the product's positioning and messaging.

Workflow

Step 1: Identify the Content

Parse $ARGUMENTS:

• If it contains a content ID (UUID), call gtm_content_get to load it
• If it contains a content type (e.g. blog_post, readme), call gtm_content_list with that type filter and let the user pick
• If it contains a title or partial title, call gtm_content_list and search by title match
• If empty, call gtm_content_list and ask the user to pick a content item to refine

If no content exists, suggest running /gtm-content first.

Step 2: Load Full Context

1. Load the content item with gtm_content_get
2. Load the product profile with gtm_product_get using the content's product_id
3. Load the GTM plan with gtm_plan_list filtered by product_id, then gtm_plan_get for the relevant plan
4. Load version history with gtm_content_versions to show the user past iterations

Present the current content with a summary:

• Title: content title
• Type: content type
• Status: current status
• Versions: number of previous versions
• Last updated: updated_at timestamp

Step 3: Gather Feedback

Check if feedback was provided in $ARGUMENTS (anything after the content identifier).

If no feedback provided, ask the user:

• What would you like to change?
• What's not working about the current version?
• Any specific tone, length, or focus adjustments?

Step 4: Generate Refined Version

Using the feedback, product profile, and GTM plan context:

1. Analyze the current body against the feedback
2. Generate an improved version that:
   • Addresses all feedback points
   • Stays consistent with the plan's positioning and messaging
   • Maintains the content type's format and structure
   • Preserves what's already working well
3. Call gtm_content_update with the new body — this automatically snapshots the old version

Step 5: Show Results

Present the changes:

• Summarize what was changed and why
• Highlight key differences between old and new versions
• Show the feedback that was stored with the version snapshot

Step 6: Next Steps

Offer the user options:

• Refine again — Run /gtm-refine with new feedback
• View history — Show all versions with gtm_content_versions
• Restore — Revert to a previous version if needed
• Promote — Update status to "review" or "final"
• Export — If the content has been exported before (has file_path), offer to re-export with /gtm-publish