How this command is triggered — by the user, by Claude, or both
Slash command
/follow-up-tracker:setupThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Follow-Up Tracker Setup Walk the user through first-time setup. Complete each step in order. ## Step 1: Verify Gmail connection Call `gmail_list_labels` to confirm the Gmail MCP is connected. If it fails, tell the user they need to connect their Gmail MCP server before using this plugin. ## Step 2: Check for follow-up labels Search the label list for these three labels: - "Follow Up" (default 7-day window) - "Follow Up 3d" (3-day window) - "Follow Up 14d" (14-day window) If any are missing, tell the user which labels need to be created and provide instructions: 1. Open Gmail → Setti...
Walk the user through first-time setup. Complete each step in order.
Call gmail_list_labels to confirm the Gmail MCP is connected. If it fails, tell the user they need to connect their Gmail MCP server before using this plugin.
Search the label list for these three labels:
If any are missing, tell the user which labels need to be created and provide instructions:
Call gcal_list_calendars to confirm Google Calendar MCP is connected. If it fails, tell the user they need to connect their Google Calendar MCP server.
Ask the user to confirm their Gmail address. This is used to distinguish sent messages from replies.
Ask the user:
Create or verify the tracking.json file exists with an empty array [] if this is a fresh setup.
Summarize the configuration:
Follow-Up Tracker — Setup Complete
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Email: {user email}
Labels: Follow Up ✓ | Follow Up 3d ✓ | Follow Up 14d ✓
Calendar: Connected ✓
Reminder time: {time} {timezone}
Tracking file: Initialized ✓
Tell the user they can now:
/scan-now to manually check for due follow-upsnpx claudepluginhub stevegustafson32/follow-up-tracker-plugin/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.
/setupChecks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.
/setupInteractive setup wizard that detects installed AI providers, configures authentication, and optimizes token usage. Auto-runs on first install and surfaces a status dashboard on manual invocation.