「follow-ups」の検索結果

Prepare for and run a product requirements review (需求评审 / PRD 评审会) the way Chinese internet teams do it: a pre-read the engineers, testers and designers can challenge, the questions each role will ask, the meeting run sheet and a written conclusion (通过 / 有条件通过 / 不通过). Use when asked 帮我准备需求评审, PRD 评审会怎么开, 评审前检查一下我的 PRD, 研发会问什么问题, or prepare my requirements review in Chinese. Produces a readiness check of the PRD, a role-by-role question bank with answer points, a 60-minute run sheet, and the review minutes template with the conclusion and follow-ups.

日本語の概要は準備中です。原文の説明を表示しています。

Turn a list of goals, tasks, deadlines, and working constraints into a practical schedule with next actions and follow-ups.

日本語の概要は準備中です。原文の説明を表示しています。

Send cold email and run outbound email campaigns from an agent with Sendsets. Connect or check sending mailboxes, turn a lead list (CSV or inline) into a multi-step email sequence with follow-ups, validate merge fields, send a test, launch, and read and answer replies. Use when the user asks to send cold emails, email a list of prospects or leads, run an outreach or outbound sequence, or follow up with contacts by email.

日本語の概要は準備中です。原文の説明を表示しています。

Use when building the robustness section for a 《会计研究》 (Accounting Research) manuscript — replacing accounting measures with alternatives, adding governance / institutional controls, placebo tests, and endogeneity follow-ups — so the main result survives an accounting referee's scrutiny. Use after mechanism is settled.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate Project Osmos for long-running Fabric and OneLake data-engineering outcomes, including task status, messages, follow-ups, cancellation, and deletion. Osmos tasks are remote service tasks, not local background agents. In Fabric portal Copilot, direct interaction is unsupported; point users to GitHub Copilot CLI. Use spark-cli for direct non-Osmos Spark work. Triggers: "Project Osmos", "Project Osmos task status", "check my Osmos task".

日本語の概要は準備中です。原文の説明を表示しています。

End-to-end LinkedIn outreach campaign builder. Takes leads from Supabase, upstream skills, or CSV. Aligns on campaign goal and tone, writes personalized LinkedIn message sequences (connection request + follow-ups + optional InMail), presents for review, and exports for the user's outreach tool (Dripify, Botdog, Expandi, or manual CSV). Logs to Supabase outreach_log.

日本語の概要は準備中です。原文の説明を表示しています。

Use when wrapping up a session before ending. 4 parallel subagents detect doc updates, repeated patterns, learning points, and follow-ups, then a verifier deduplicates and presents choices. Triggers on /session-wrap, session wrap, session cleanup, end of session.

日本語の概要は準備中です。原文の説明を表示しています。

Always-on spam and deliverability guardrails for cold email copy. Apply these rules whenever writing, reviewing, or QA-ing subject lines, openers, follow-ups, CTAs, or any cold outreach copy. Trigger on phrases like "check this for spam", "spam word check", "deliverability review", "QA this copy", "flag banned words", "check subject line", "is this safe to send", "scan for spam triggers", or any time cold email copy is being generated or reviewed. Also trigger automatically as a background rule whenever the campaign-copywriting or cold-email-copywriting skill is active -- these guardrails apply to EVERY piece of outbound copy generated, even if the user does not explicitly ask for a check.

日本語の概要は準備中です。原文の説明を表示しています。

Build personalized cold outreach sequences for LinkedIn and email. Use when someone needs to reach prospects, warm up cold leads, or build a systematic outreach engine. Covers research, connection requests, follow-ups, and conversion.

日本語の概要は準備中です。原文の説明を表示しています。

Use when implementing delays that must survive process restarts (e.g., 24-hour cart abandonment, scheduled follow-ups), waiting for human approval or external events with timeouts (review gates, webhook callbacks, async API completion), polling external services without losing state on crashes, calling other functions and awaiting their results, memoizing expensive operations so they don't re-run on retry, or running async work in parallel inside a workflow. Covers Inngest step methods: step.run, step.sleep, step.waitForEvent, step.waitForSignal, step.sendEvent, step.invoke, step.ai, plus patterns for loops and parallel execution.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare a sourced site-visit record separating direct observations, participant reports, interpretations, limitations and proposed follow-ups.

日本語の概要は準備中です。原文の説明を表示しています。

Summarizes recent git changes for context recovery after session breaks. Use when resuming work after a gap or handing off to another session.

日本語の概要は準備中です。原文の説明を表示しています。

Daily inbox triage using Cowork's email write tools (Microsoft 365 or Gmail) -- classifies unread mail, drafts replies in your voice, flags what needs a decision, and schedules follow-ups. Built to run as a recurring Cowork scheduled task.

日本語の概要は準備中です。原文の説明を表示しています。

Generate professional email templates for various business scenarios including sales outreach, customer support, internal communications, follow-ups, and apologies. Creates personalized, tone-appropriate templates with subject lines and formatting. Use when users need to write business emails, cold outreach, or professional communications.

日本語の概要は準備中です。原文の説明を表示しています。

Generate professional email templates for various business scenarios including sales outreach, customer support, internal communications, follow-ups, and apologies. Creates personalized, tone-appropriate templates with subject lines and formatting. Use when users need to write business emails, cold outreach, or professional communications.

日本語の概要は準備中です。原文の説明を表示しています。

Use when preparing for, running, or closing a live meeting with an AI assistant dashboard. Triggers on "meeting copilot", "live copilot", "prepare for a call", "update copilot", "close the session", or requests to turn transcript chunks into meeting questions, topic maps, decisions, and follow-ups.

日本語の概要は準備中です。原文の説明を表示しています。

Transcribe meeting audio with speaker diarization, generate structured summaries with action items, decisions, and follow-ups, and support multiple audio formats and languages. Use when the user requests meeting transcription or provides relevant inputs for this workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Draft professional emails for business and marketing contexts — outreach, client communication, proposals, follow-ups, and internal updates. Includes tone calibration, subject line formulas, and follow-up cadence recommendations.

日本語の概要は準備中です。原文の説明を表示しています。

Read-only context for issues, pull requests, and backlogs. Use to trace related work, check PR counts, prioritize follow-ups, filter saved captures, open exact dashboard views, replay triage queries, or compare snapshots.

日本語の概要は準備中です。原文の説明を表示しています。

Draft cold emails, warm intro blurbs, follow-ups, and investor communications. Use when the user needs to write to angels, VCs, or accelerators.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze a warehouse for stale, unused, or redundant tables via the analyze_storage_costs MCP tool. Classifies waste patterns and table categories, computes safety tiers, and handles category drill-downs and lineage follow-ups.

日本語の概要は準備中です。原文の説明を表示しています。

AI Overview (AI Mode) scraping via Google Search. Returns AI-summarized key points for a single keyword, ideal for deep research, technical Q&A, long-tail product selection, and cross-border consumer preference analysis using the latest web information. Single-round only; follow-ups require the agent to summarize context and issue a new request. Triggered by: Google AI, AI Overview, AI Mode, Google AI search, AI search, deep research, consumer preference analysis, web summary, long-tail product research, cross-border market insights.

日本語の概要は準備中です。原文の説明を表示しています。

Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.

日本語の概要は準備中です。原文の説明を表示しています。

Write the postmortem for an incident, in its incident channel, once it is mitigated or resolved. Use on "write up this incident", "postmortem", "incident summary", "what happened here for people who weren't around", "draft the retro", or when the oncall memory says incidents of this severity get one. Reads the incident channel (and the alert thread it came from), the investigation findings and the data behind them, and writes a one-screen, zero-context write-up: what happened, impact with numbers, detection, timeline with durations, why it happened, what fixed it, follow-ups with proposed owners, and one before/during/after chart. Posted and pinned in the incident channel as its final pinned post, with edit requests updating that one pinned post in place — unless the person or the team's conventions say write-ups live elsewhere, in which case it is written there and only a link is posted, nothing pinned. A person edits and publishes it; never assigns blame.

日本語の概要は準備中です。原文の説明を表示しています。