good-morning

Good Morning Briefing

Daily morning briefing that pulls calendar, tasks, pipeline, and outreach data into one view.

Invocation

• /good-morning — Full morning briefing
• /good-morning --quick — Calendar + tasks only
• /good-morning --team — Only team outreach audit

Prerequisites

• Linear MCP installed and connected
• Google Workspace MCP (for calendar) — optional but recommended
• config/config.yaml exists (run /setup first)

Instructions

Parse the argument (if any) from $ARGUMENTS to determine mode:

• If $ARGUMENTS contains --quick → quick mode
• If $ARGUMENTS contains --team → team-outreach-only mode
• Otherwise → full mode

First: Read config/config.yaml (relative to project root) to load all configuration. Extract:

• config.linear.action_team — the team name for action tasks (e.g., "GTM")
• config.linear.pipeline_team — the team name for deal tracking (e.g., "Sales")
• config.linear.default_label — label applied to engine-created tasks
• config.linear.pipeline_stages — list of pipeline stage names
• config.team — list of team members with roles and Linear user IDs
• config.ritual.labels — label names for daily-3, daily-2, parking-lot
• config.ritual.meaningful_count — number of meaningful tasks (default 3)
• config.ritual.light_count — number of light tasks (default 2)
• config.integrations.outreach_sheet — outreach spreadsheet settings
• config.integrations.google_workspace.enabled — whether calendar is available

Identify the default assignee = the team member with is_default_assignee: true.

Resolve Linear team IDs (required): Some Linear MCP servers (e.g., linear-mcp-server) hang indefinitely when issue searches are made without a teamId. Before any issue query:

1. Call mcp__linear__list_teams once
2. Match action_team and pipeline_team names to their UUIDs
3. Store them as {action_team_id} and {pipeline_team_id} for the rest of the session
4. If either name cannot be matched, surface a clear error and stop — do not run unscoped Linear searches