Skip to content

Created scheduled tasks folder #17101

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SaraMiteva wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Created scheduled tasks folder #17101

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
78 changes: 78 additions & 0 deletions .claude/pmm-scheduled-tasks/competitor-changelog-watch.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,78 @@
> **Disclaimer:** This is Sara's scheduled task. Please edit it so it fits your needs.

# Competitor Changelog Watch

**Run a bi-weekly competitive intelligence watch for me (Sara, PMM @ PostHog).** Focus on the four areas where PostHog competes hardest: **error tracking, logs, session replay, and AI-on-replay ("replay vision")**.

## Competitors and sources

**Error tracking**

- Sentry — https://sentry.io/changelog/ and https://blog.sentry.io/
- BugSnag — https://www.bugsnag.com/resources/
- Rollbar — https://rollbar.com/changelog/ and https://rollbar.com/blog/

**Logs / observability**

- Datadog — https://www.datadoghq.com/blog/ (filter to logs/observability)
- New Relic — https://docs.newrelic.com/whats-new/ and https://newrelic.com/blog
- Splunk — https://www.splunk.com/en_us/blog/ (filter to product/observability)
- Elastic — https://www.elastic.co/blog (filter to observability/logs)
- Grafana Loki — https://grafana.com/blog/ and https://github.com/grafana/loki/releases
- Better Stack — https://betterstack.com/changelog and https://betterstack.com/community/

**Session replay**

- Microsoft Clarity — https://learn.microsoft.com/en-us/clarity/mobile-sdk/sdk-changelog and https://clarity.microsoft.com/blog/
- FullStory — https://help.fullstory.com/hc/en-us/articles/4410282600343-Fullstory-Release-Notes
- LogRocket — https://blog.logrocket.com/
- Hotjar — https://www.hotjar.com/blog/

**Replay vision / AI-on-replay** (strategic focus area)

- HumanBehavior — https://www.humanbehavior.co/
- AutoPlay AI — https://www.autoplay.ai/
- Decipher — search "Decipher session replay" on first run, then use the domain
- Contentsquare — https://support.contentsquare.com/hc/en-us/articles/37271835021201-Releases-and-Updates-for-2025
- Amplitude — https://amplitude.com/releases (filter to Session Replay / AI items only)
- Sprig — https://docs.sprig.com/changelog
- Pendo — https://support.pendo.io/hc/en-us/categories/15374632651291-What-s-new
- Glassbox — https://www.glassbox.com/blog/
- UXCam — https://uxcam.com/blog/

## How to run

1. Fetch URLs in parallel. If a page returns a client-rendered shell, retry with Chrome. If it 404s, note it once at the bottom and move on — don't loop.
2. **Only include items dated in the last 14 days.** Use visible date stamps on the page; don't summarize archive content.
3. **Ignore noise** — minor bug fixes, hiring posts, regional/legal updates, generic thought-leadership. **Keep** — new launches, pricing changes, repositioning, AI/agent features (especially multi-session summaries, NL search, MCP, autonomous replay agents), new SDKs/integrations, anything that shifts their story vs PostHog.
4. For each item that survives, write 2–3 lines:
- What they shipped (one sentence)
- Why it matters for PostHog (closes a gap, opens a gap, reframes positioning, validates a direction)
- Source link
5. If a competitor shipped nothing relevant, say **"Nothing notable"** in one line. Don't pad.
6. **Pay extra attention to:**
- **Better Stack** — going hard after our buyer ("30x cheaper than Datadog", AI SRE, contract buyouts)
- **HumanBehavior, AutoPlay AI, Decipher** — AI-native "parasitic VLM" replay startups; directionally where PostHog is heading
- **Amplitude's Session Replay Agent and Contentsquare's Sense Analyst** — autonomous replay agents; track every iteration

## Output (in chat, no file)

```
# Competitor Watch — [date range]

## Headlines
2–3 bullets naming the biggest moves of the cycle. Skip if nothing notable.

## Error tracking
### Sentry
…
[etc.]

## What I'd action this cycle
1–3 concrete suggestions: battlecard update, blog response, sales talking point, gap to flag to product or #team-replay. Skip if nothing.

## Couldn't reach
(only if URLs failed)
```

Keep the whole digest under ~1000 words. I read this once and decide what to do — be ruthless about signal vs noise. Most competitors will be "Nothing notable" most weeks, and that's the right answer.
40 changes: 40 additions & 0 deletions .claude/pmm-scheduled-tasks/customer-quote-harvester.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
> **Disclaimer:** This is Sara's scheduled task. Please edit it so it fits your needs.

# Customer Quote Harvester

Every other Monday at 9am PT, run a customer quote harvest for me.

**What I want:** verbatim customer lines about PostHog's Error Tracking, Logs, Session Replay, and Replay Vision from the last 14 days. Nothing about other products unless it's a comparative jab that makes one of these four look good.

## Where to look

1. **Customer Slack Connect channels** — anything named #posthog-\<customer\> or #\<customer\>-posthog. Skip internal channels (#team-, #ask-, #alerts-, #sales-, etc.). Pull only customer-side messages, never a PostHogger's reply.
2. **PostHog surveys** — NPS – Error Tracking, NPS – Session Replay, Logs Feedback, Session Replay Filters Feedback, and the open-feedback variants. Open-text answers live inside properties.$survey_questions.
3. **BuildBetter** — user interview calls from the last 14 days. Pull the customer's words, not the interviewer's.

## What counts as a quote

Mentions of: error tracking, exceptions, Sentry, Bugsnag, session replay, replay AI/vision, FullStory, LogRocket, Hotjar, logs, observability, Datadog, New Relic, Splunk. Verbatim only — use … for trimmed middles. Drop duplicates. **5 strong quotes beat 20 mediocre ones.**

## Permission tagging

Tag every quote with a permission flag:
- 🟢 public (HN, Reddit, X, G2)
- 🟡 needs permission (Slack Connect, NPS, interview)
- 🔴 internal only (PostHogger paraphrase)

Default to 🟡 in doubt — never 🟢.

## Case study candidates

Pick 1–3 case study candidates. A good one has at least 2 of: a clear switch story, strong positive sentiment, concrete impact (cost / time / tools dropped), multiple positive touchpoints, recognizable brand, or active engagement. Be picky — say "no candidates this cycle" rather than reach.

## Delivery

Deliver as a Google Drive doc titled **Customer Quote Bank — \<date range\>** with:
- Sections per product
- Case study candidates
- Highlights (which quote suits landing page vs. sales deck vs. social)
- Coverage notes (channels scanned, surveys reviewed, BuildBetter calls reviewed, what came back empty)

Under 1500 words. Drop the doc link in Slack DM to me when it's ready.
32 changes: 32 additions & 0 deletions .claude/pmm-scheduled-tasks/monday-focus-briefing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
> **Disclaimer:** This is Sara's scheduled task. Please edit it so it fits your needs.

# Monday Focus Briefing

**Every Monday at 8am, generate my weekly focus briefing.**

Scan everywhere I made commitments, was tagged, or was assigned work in the **last 7 days**, and send me a single prioritized chat message.

**Sources to check:**

- **Granola** — meetings I attended; pull action items, things I committed to, follow-ups I promised.
- **Google Drive** — recent docs I own, was mentioned in, or commented on; surface unresolved comments and review requests.
- **GitHub** — PRs awaiting my review, PRs of mine awaiting changes, issues assigned to me, @-mentions needing a reply.
- **Slack** — direct asks to me, threads where I owe a response, @-mentions, things I said I'd follow up on.

**Order strictly by urgency**, not by source:

1. Hard deadlines this week
2. Direct asks awaiting my response (questions, review requests, anyone blocked on me)
3. Commitments I made
4. Tagged for awareness
5. Background activity worth knowing

**Format:**

- Open with a 1–2 sentence summary and the top 1–3 things that matter most.
- Then a **Top priorities this week** section (3–6 bullets across all sources).
- Then one section per source, only if it has content. If a source is quiet, say "Nothing pending" — don't pad.
- One line per bullet, ≤25 words, with a clickable link to the source (Slack permalink, GitHub URL, Drive URL, Granola link).
- End with a short **Heads up** section for anything time-sensitive next week.

If a connector errors out, note it briefly and continue with the rest. Run autonomously — don't ask me clarifying questions. Use today's date as the anchor.
23 changes: 23 additions & 0 deletions .claude/pmm-scheduled-tasks/weekly-product-digest.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
> **Disclaimer:** This is Sara's scheduled task. Please edit it so it fits your needs.

# Weekly Product Digest

Every Monday at 9 AM, build me a **Weekly Product Digest** from my three product Slack channels — #team-logs, #team-replay, and #team-error-tracking — covering the previous 7 days.

Save it as a live Cowork artifact called *Weekly Product Digest* that I can re-open from the sidebar all week, and refresh it each Monday with the new week's data.

Pull three things, in this order:

1. **Action items & @mentions of me.** Anything I'm tagged in or asked to do. Resolve my Slack user ID once at the start (my email is sara@posthog.com) and look for that ID in messages. For each item, show the channel, author, snippet (~200 chars), timestamp, and a "View in Slack" link.

2. **Decisions & announcements.** Product decisions, launch updates, scope or policy changes — anything that signals "this changed." Skip routine status pings.

3. **Team progress updates.** What the team is working on, milestones hit, blockers cleared. Group items by project/topic with a one-line synthesis under each heading. Skip lunch chatter, gif reactions, and off-topic threads.

If a section is genuinely empty, show *"Nothing this week"* in italic — don't hide it. I want to see that you actually checked.

**Layout:** light mode, clean and scannable. Header has the date range covered, the timestamp of the last update, and the three channels as monospace chips. Each item renders as a small card — channel + author + timestamp on top, snippet below, "View in Slack" link bottom-right opening in a new tab.

**After updating the artifact,** post a short chat summary (under 80 words) flagging the 1–3 things I should look at first — anything blocking a launch, anything I'm tagged on, or any decision that affects my plans. End with a reminder that the full digest is in the sidebar.

**If something breaks:** if a channel can't be reached, note it in the footer rather than failing the whole run. If Slack auth is broken, update the artifact with a banner saying Slack needs to be reconnected — don't invent data. Never produce a silently empty dashboard.
Loading