feat: add daily ops layer — pm-standup, pm-interview, pm-weekly-update + Google Calendar and Granola connectors#6
Open
alexhumeau wants to merge 3 commits into
Conversation
…Calendar and Granola connectors New skills: - pm-standup: daily briefing from git, Linear, Google Calendar, and Granola Surfaces yesterday's commits, today's meetings with prep gaps flagged, top priorities inferred from roadmap, blockers, and drift detection - pm-interview: user interview guide + Granola-powered signal extraction Prepares structured interview guides, detects Granola transcripts automatically, extracts findings into FEEDBACK.md (consumed by /pm-audit and /pm-user-feedback) - pm-weekly-update: stakeholder update email adapted to audience Supports manager, CEO/exec, investor, dev team, and cross-functional formats New connectors: - google-calendar: MCP-based (mcp__claude_ai_Google_Calendar__*), fetches today's events - granola: MCP-based (mcp__claude_ai_Granola__*), fetches meeting notes and transcripts pm-standup integrates both connectors: shows today's schedule, flags meetings with no recent commits (prep gap), and surfaces user calls for /pm-interview. pm-interview checks Granola for an existing transcript before asking for manual notes. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…t OS usage When running from a Product OS folder (not inside a codebase), pm-standup now fetches commits from all active GitHub repos instead of reading local git. Commits are grouped by repo: [repo-name] commit message. On first run, caches the list of repos with recent activity to speed up subsequent runs. Falls back to local git if GitHub is not connected. This makes pm-standup useful as a single morning command regardless of which repo you're currently in. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…a, Alvarez, NNG
Complete rewrite of the interview guide generation, grounded in four recognized
frameworks:
- Teresa Torres (Continuous Discovery Habits): one story per interview, temporal
anchoring, excavation of the timeline with neutral prompts, anti-generalization
redirect ("usually" → "last specific time")
- Rob Fitzpatrick (The Mom Test): past behavior only, no hypotheticals, mandatory
workaround/implication/alternative questions, explicit anti-patterns table
- Bob Moesta (JTBD Switch Interview): 6-stage buying timeline for churned/switched
users, four forces mapping (push/pull/anxiety/inertia), contrast probing technique
- Cindy Alvarez (Lean Customer Dev): hypothesis-first ordering (Constable), top 3
questions before the call, forward action at close, post-call review discipline
Session type auto-detection: current user → story-based, churned → JTBD switch,
prospect → lean discovery, buyer → positioning framing.
Signal reliability thresholds now explicit: 3 min, 5 standard, 8-12 for full JTBD map.
Four forces map added to FEEDBACK.md output structure.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
nanopm covers the full strategic pipeline (audit → strategy → roadmap → PRD → tickets).
This PR adds the daily ops layer — the skills a PM uses every day, not once a quarter.
New skills
/pm-standupMorning briefing in under 60 seconds. No questions asked, instant output.
/pm-interview/pm-interviewStructured user interview guide + post-session signal extraction.
/pm-audit— no pipeline changes needed/pm-weekly-updateStakeholder update email drafted from what actually happened.
New connectors
google-calendarmcp__claude_ai_Google_Calendar__*)granolamcp__claude_ai_Granola__*)Both degrade gracefully — if not connected, the relevant section is silently skipped.
Design choices
What I tested