ChatGPT Work 実践ガイド：6職種別ワークフロー、プロンプトテンプレートと自動化レシピ（2026年）

1. プラグイン接続 → 2. 目標 + 出力形式を記述 → 3. Plan Mode をレビュー → 4. 実行中に軌道修正 → 5. 成果物を受け取り反復

[役割] + [データソース @plugins] + [タスク] + [出力形式] + [制約] + [受け入れ基準]

Create a scheduled task running every weekday at 4pm:

1. Check tomorrow's customer meetings in @Google Calendar (exclude internal-only)
2. For each customer meeting:
   - Pull 30-day account notes and interaction history from @SharePoint / @Salesforce
   - Search 30-day public news and executive updates for that company
   - Write a 2–3 sentence background summary for each external attendee
3. Generate a 2–3 page brief per meeting, save as @Google Drive documents
4. Email me a summary with links via @Gmail

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

From all opportunities, contacts, and recent activity 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 last 7 days (email, meetings, support tickets)
   - Recommended next actions (priority sorted)
2. Set a Scheduled Task: auto-refresh the Site every weekday at 8am
3. DM me via @Slack when major changes occur

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

Analyze @Salesforce leads from the last 30 days and cross-reference @Gmail sales correspondence.

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

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

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

Complete the end-to-end marketing workflow:

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

Phase 2 — Asset generation:
- From 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 (language, cultural references, compliance wording)
- Flag sensitive phrases requiring human review in each version

Pause after each phase and wait for my approval before proceeding.

Set a scheduled task running every Monday at 7am:

1. Summarize important discussions from the last 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 Agenda" document in @Google Drive (preserve version history)
4. Post a summary of 5 bullets or fewer to @Slack #leadership

Constraints: quote only 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. Draft performance narrative (Google Docs) explaining likely causes by Revenue / COGS / OpEx
4. Build a 5–8 slide management deck (with charts, following attached template style)
5. List 3 key judgment calls requiring human finance sign-off

Constraints: do not modify any source data; cite source cell for every number.

You are an accounts payable specialist. Compare these 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 difference >2%
- Missing tax ID
- Duplicate invoice number
- Vendor name mismatch

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

Run automatically every weekday at 6:30am:

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

If the dashboard is unreachable, tell me in Plan Mode — do not fabricate data.

Monitor new customer feedback from the last 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. Rank by frequency × impact × implementation effort
3. Output a product review backlog (Notion / Google Docs format)
4. Set a Scheduled Task to auto-refresh this document every Friday

Constraints: anonymize all customer references; no customer names in output.

Launch readiness review for [product/feature name]:

1. From @Jira: pull linked Epic / Story completion status and open blockers
2. From @Google Drive "GTM Plans": pull the corresponding launch plan and check key milestones
3. From @Slack #product-launch: extract unresolved discussions from the last 7 days
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-update Jira status; flag high-risk items for 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 side panel
3. If approved, draft Release Notes

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

In Codex mode, across [frontend-repo] and [backend-repo]:
1. Summarize this week's merged PRs 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 5pm

Set Scheduled Task:
- Frequency: [daily / every Monday / 1st of month / when keyword appears in @Slack channel]
- Time: [timezone + specific time]
- Action: [specific workflow description]
- Notification: [Slack channel / email / none]
- Human approval: [which steps require my sign-off first]

1. 人間の工数コストが分かる実タスクを選ぶ（例：月末差異表 — 手動では通常 2 時間）
2. Plan Mode 付きで Work モードに 1 回実行し、ステップ数を記録
3. 実行後、プランの含まれる用量と消費量を照合
4. 外挿：日次 / 週次実行した場合、月次消費は予算内か？
5. 高い場合 → セクション 6.2 で最適化し、再実行して比較