Interactive post-onboarding tour that adapts to whatever data exists (calendar, Granola, or none). Use right after onboarding, or when the user says 'show me around', 'how do I start'. Also use proactively when the vault is < 7 days old. Not for the initial setup itself; use setup.
Define time-horizoned assumptions about your industry (today / 6mo / 12mo) that ground strategic thinking. Use when the user is making roadmap, positioning or investment calls, or says 'what am I assuming about the market'. Also use proactively before a big strategic recommendation. Not for capturing a single…
Turn synced meetings into updated person pages, extracted tasks and organized notes. Use when the user says 'process my meetings', 'catch up my notes', or after Granola/Otter syncs. Also use proactively when unprocessed meetings exist. Not for prepping an upcoming meeting; use meeting-prep.
Use when reviewing customer accounts for evidence-backed expansion hypotheses based on current usage, product fit, and expressed needs. Not for renewal strategy or negotiation; use renewal-prep.
Use when reviewing customer-account health with a configured scoring rubric and dated inputs, or when reporting why a portfolio cannot yet be scored. Not for finding expansion opportunities; use expansion-opportunities.
Use when preparing an evidence-backed brief for an upcoming customer renewal from contract, ARR, dated outcomes, usage, and risk evidence. Not for health scoring; use health-score.
Use when assessing use of named design-system components or tokens across a defined sample of product artifacts, including adoption and deviation questions.
Use when a system or design choice needs an evidence-backed ADR, explicit alternatives and trade-offs, or review of proposed, accepted, or superseded decision history.
Use when a service or operational incident needs a cited, timezone-aware timeline, blameless learning review, or prevention actions with accountable follow-up.
Use when technical debt needs linked code or operational evidence, deduplication, first-seen provenance, or impact, effort, confidence, and cost-of-delay prioritization.
Use when preparing a finance draft for a board or leadership review from dated actuals, budgets, forecasts, cash data, and decision context. Not for detailed line-item variance analysis; use variance-analysis.
Use when reporting the evidence-backed status of a named month-end or quarter-end close, its blockers, counted completion, and dependency path. Not for explaining budget variances; use variance-analysis.
Use when explaining a dated actual-versus-budget or actual-versus-forecast variance for a comparable finance period. Not for tracking close checklist completion; use close-status.
Use when synthesizing dated customer conversations, feedback, or behavior evidence into audience or persona insight, especially when sources are numerous, repeated, time-bounded, or disagree.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: