{
  "id": "uc_fdc9b82ffd59",
  "slug": "automated-weekly-sprint-changelog-and-stakeholder-memo",
  "asset_type": "use_case",
  "name": "Linear Cycle Close to Executive & Customer Release Notes",
  "tagline": "Summarize every completed issue at the end of a 2-week Linear cycle into internal GTM talking points and public changelog entries.",
  "description_md": "### 1. Problem & Operational Bottleneck\nSummarize every completed issue at the end of a 2-week Linear cycle into internal GTM talking points and public changelog entries. Built and battle-tested in production workflows by **@linear** (Linear Engineering).\n\n### 2. Target Architecture & Required Stack\n- **Linear MCP**\n- **GitHub MCP**\n- **Notion MCP**\n- **Slack MCP**\n\n### 3. Step-by-Step Implementation Blueprint\n1. Configure and authenticate the required MCP connectors (Linear MCP, GitHub MCP, Notion MCP, Slack MCP) in your agent workspace.\n2. Run the initial read-only inspection pass for 'Linear Cycle Close to Executive & Customer Release Notes' to gather baseline telemetry, schemas, and context.\n3. Execute the multi-step analysis and transformation pipeline with strict schema validation and zero fabricated identifiers.\n4. Review the staged diff or approval card and verify completion via automated regression and status checks.\n\n### 4. Copy-Paste Agent Execution Prompt\n```markdown\nRun the 'Linear Cycle Close to Executive & Customer Release Notes' (automated-weekly-sprint-changelog-and-stakeholder-memo) implementation blueprint using Linear MCP, GitHub MCP, Notion MCP, Slack MCP. Objective: Summarize every completed issue at the end of a 2-week Linear cycle into internal GTM talking points and public changelog entries. Step 1: Perform a read-only audit of current state and recent logs. Step 2: Generate a deterministic execution plan with exact diffs, SQL/CLI commands, or drafted payloads. Step 3: Request human confirmation before applying any production writes or external sends.\n```\n\n### 5. Verification & Safety Guardrails\n- **Human-in-the-Loop Gate:** All external communications, production database mutations, and billing actions stage an explicit review diff before execution.\n- **Deterministic Telemetry:** Every run logs structured JSON output, latency metrics, and source citations so operators can audit every decision.\n",
  "primary_category": "operations",
  "categories_json": "[\"operations\", \"use-cases\"]",
  "tags_json": "[\"linear-mcp\", \"github-mcp\", \"notion-mcp\", \"blueprint\", \"operations\"]",
  "compatible_agents_json": "[\"grok-bot\", \"claude-code\", \"cursor\"]",
  "integrations_json": "[\"Linear MCP\", \"GitHub MCP\", \"Notion MCP\"]",
  "includes_json": "[]",
  "safety_level": "Read-Only / Ask-First",
  "safety_summary": "Verified capability blueprint by @linear.",
  "share_url": "",
  "deep_link_uri": "",
  "mcp_endpoint": "",
  "mcp_transport": "http",
  "install_command": "npx lightstate inspect automated-weekly-sprint-changelog-and-stakeholder-memo",
  "skill_markdown": "",
  "starter_prompt": "Run the 'Linear Cycle Close to Executive & Customer Release Notes' (automated-weekly-sprint-changelog-and-stakeholder-memo) implementation blueprint using Linear MCP, GitHub MCP, Notion MCP, Slack MCP. Objective: Summarize every completed issue at the end of a 2-week Linear cycle into internal GTM talking points and public changelog entries. Step 1: Perform a read-only audit of current state and recent logs. Step 2: Generate a deterministic execution plan with exact diffs, SQL/CLI commands, or drafted payloads. Step 3: Request human confirmation before applying any production writes or external sends.",
  "project_url": "https://x.com/linear",
  "repo_url": "",
  "creator_handle": "linear",
  "creator_name": "Linear Engineering",
  "creator_avatar_url": null,
  "creator_url": "https://x.com/linear",
  "creator_platform": "x",
  "creator_cal_url": null,
  "claimed_by_user_id": null,
  "scouted_by_handle": null,
  "source_url": "https://x.com/linear",
  "source_tweet_id": null,
  "source_origin": "certified_builder",
  "source_posted_at": null,
  "x_likes": 399,
  "x_bookmarks": 637,
  "x_retweets": 159,
  "x_views": 5586,
  "human_upvotes": 399,
  "human_installs": 399,
  "bot_pulls": 637,
  "pulse_score": 87,
  "gravity_rank_score": 2769,
  "is_featured": 0,
  "is_verified": 1,
  "is_sponsored": 0,
  "sponsor_tier": "free",
  "sponsor_label": "",
  "sponsor_cta_url": "",
  "sponsor_expires_at": null,
  "commercial_intent_score": 0,
  "status": "active",
  "created_at": "2026-10-24T22:25:00Z",
  "updated_at": "2026-10-24T22:25:00Z",
  "verified_at": null,
  "primitive": "use_case",
  "title": "Linear Cycle Close to Executive & Customer Release Notes",
  "description": "Summarize every completed issue at the end of a 2-week Linear cycle into internal GTM talking points and public changelog entries.",
  "category": "operations",
  "tags": "[\"linear-mcp\", \"github-mcp\", \"notion-mcp\", \"blueprint\", \"operations\"]",
  "agent_compatibility": "[\"grok-bot\", \"claude-code\", \"cursor\"]",
  "author_handle": "linear",
  "author_name": "Linear Engineering",
  "author_avatar": null,
  "source_tweet_url": "https://x.com/linear",
  "github_url": "",
  "external_url": "https://x.com/linear",
  "upvotes_count": 399,
  "installs_count": 399
}