ChatGPT Work 実践ガイド
6部門ワークフロー、Prompt テンプレートと自動化レシピ

Create a scheduled task that runs every weekday at 4 PM.

1. Check my tomorrow's @Google Calendar client meetings (exclude internal meetings)
2. For each client meeting:
   - Pull account notes and interaction records from the past 30 days via @SharePoint / @Salesforce
   - Search for public news and executive updates about the company in the past 30 days
   - Write a 2–3 sentence background summary for each external attendee
3. Generate a 2–3 page Brief for each meeting, save as @Google Drive documents
4. Send me a summary email via @Gmail with links to each Brief

Output format: Email subject "Tomorrow's Client Meeting Brief — [date]", body as a table (Client name | Meeting time | Key topics | Brief link)

Based on all opportunities, contacts, and recent activity records for [Account Name] in @Salesforce:

1. Create an interactive account command center (Sites) including:
   - Pipeline overview (stage, amount, expected close date)
   - Key signals from the past 7 days (emails, meetings, support tickets)
   - Recommended next actions (sorted by priority)
2. Set a Scheduled Task to auto-update this Site every weekday at 8 AM
3. DM me via @Slack when there are major changes

Constraints: Do not auto-send any external emails; amounts must match raw CRM data.

Analyze new leads from the past 30 days in @Salesforce and their follow-up records, cross-referencing sales correspondence in @Gmail.

Find:
1. Leads with no follow-up for more than 48 hours (grouped by source)
2. Broken follow-up chain points (where response rate drops sharply after a step)
3. Estimated pipeline loss amount

Output:
- Excel detail table (Lead ID | Source | Last follow-up date | Break type | Recommended action)
- 1-page executive summary PPT highlighting seven-figure potential loss opportunities
- Suggest a weekly repeatable review workflow (for Scheduled Task use)

I uploaded the following customer research materials: [attachment / @Google Drive link]

Complete an end-to-end marketing workflow:

Phase 1 — Brief:
- Extract target audience, core pain points, competitive positioning
- Output a Campaign Brief (Google Docs) with message pillars and channel recommendations

Phase 2 — Asset generation:
- Based on the Brief, generate: 1 acquisition email, 3 LinkedIn posts, 1 landing page copy outline
- Save to @Google Drive "Campaign / [Product Name]" folder

Phase 3 — Regional adaptation:
- Adapt core assets for US, Europe, and APAC versions (language, cultural references, compliance wording)
- Flag sensitive expressions requiring human review in each version

Pause after each phase and wait for my confirmation before proceeding to the next.

Set up a scheduled task that runs every Monday at 7 AM:

1. Summarize important discussions from the past 7 days in @Slack #product-launch and @Microsoft Teams "Go-to-Market" channel
2. Extract: decisions made, open questions, blockers needing alignment in the meeting
3. Update the "Weekly Meeting Agenda" document in @Google Drive (preserve version history)
4. Post a summary of up to 5 items in @Slack #leadership

Constraints: Only cite publicly discussed content; do not leak messages marked confidential.

Assist with [month] month-end budget variance analysis:

1. Pull corresponding tables from @Google Drive "Finance / Actuals" and "Finance / Forecast"
2. Create a reconciliation workbook in @Google Sheets:
   - Summarize actual vs forecast variance by department
   - Flag line items with variance >5% or >$50K
   - Preserve all original formulas; do not overwrite source files
3. Generate a performance explanation draft (Google Docs), categorized by Revenue / COGS / OpEx with possible reasons
4. Create a 5–8 page management report PPT (with charts, following attached template style)
5. After completion, list 3 key judgment points requiring finance team confirmation

Constraints: Do not modify any source data; cite source cell for all numbers.

You are an accounts payable specialist. Compare the following two datasets:
- Payment register: [@Google Drive link]
- Invoice list: [@Google Drive link]

Flag the following anomalies (return as a table):
| Issue type | Vendor | Invoice # | Amount | Recommended action |
- Amount variance >2%
- Missing tax ID
- Duplicate invoice number
- Vendor name mismatch

Do not initiate payments automatically; output review table for human verification only.

Auto-run every weekday at 6:30 AM:

1. Visit [internal dashboard URL / @SharePoint report page]
2. Compare with yesterday's snapshot; extract significant changes (>10% fluctuation or new red indicators)
3. Generate a 1-page morning briefing (Google Docs) with structure:
   - TOP 3 items to watch today
   - Metric change table
   - Recommended follow-up owners
4. Send via @Gmail to ops-leads@company.com

If dashboard is inaccessible, inform me at Plan stage; do not fabricate data.

Monitor new customer feedback from the past 14 days across:
- @Slack #customer-feedback
- @Gmail label "NPS-Detractor"
- @Google Drive "Support Tickets Export"

1. Cluster feedback into 5–8 themes (with representative quotes)
2. Prioritize by Frequency × Impact × Implementation difficulty
3. Output product evaluation backlog (Notion / Google Docs format)
4. Set a Scheduled Task to auto-refresh this document every Friday

Constraints: Anonymize feedback quotes; no customer names.

Conduct a launch readiness review for [product/feature name]:

1. Pull related Epic / Story completion status and open blockers from @Jira
2. Pull corresponding go-to-market plan from @Google Drive "GTM Plans"; check key milestones
3. Extract unresolved discussions from the past 7 days in @Slack #product-launch
4. Output a Launch Readiness report (Google Docs):
   - Readiness score (Red / Yellow / Green)
   - Blocker list (Owner | Due date | Risk level)
   - Recommended Go / No-Go judgment with rationale

Do not auto-modify Jira status; flag high-risk items requiring human decision.

In Codex mode:
1. Review PR #123 in [repo/name], focusing on [security / performance / test coverage]
2. Leave line-by-line review comments in the PR sidebar
3. If approved, generate a Release Notes draft

Then switch to Work mode:
4. Format Release Notes as a @Confluence page
5. Draft an announcement for @Slack #engineering (do not auto-send)

In Codex mode, across [frontend-repo] and [backend-repo]:
1. Summarize merged PRs this week and open P0/P1 Issues
2. Generate an engineering weekly report in Markdown

Switch to Work mode:
3. Convert to Google Docs and insert this week's burndown chart (pull from @Jira)
4. Set a Scheduled Task to auto-generate every Friday at 5:00 PM

1. Pick a real task you already know the manual duration of (e.g., month-end variance report, usually 2 hours manually)
2. Run once in Work mode with Plan Mode, record step count
3. After execution, check usage (compare to your plan's included usage)
4. Estimate: if run daily / weekly, is monthly usage within budget?
5. If too high → optimize per section 5.2 and rerun to compare