仕事効率化のスキル

Turns one meeting transcript or recap into a DRAFT action-items document (decisions, owned and dated action items with verbatim source quotes, open questions), a task list ready for the user to enter into their task tracker, and one DRAFT follow-up email per action owner, all returned in the chat for the user to store, create or send. Use when the user shares, names or points to a meeting transcript or recap and asks to "pull the action items from this transcript", "who owns what after today's call", "draft follow-up emails to each owner" or "turn this recap into tasks". Do not use for full minutes, use meeting-minutes-writer instead; a brief before a meeting is meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.

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

Prepares a DRAFT management-of-change intake record from a change description (email, meeting note, marked-up drawing or request form): what changes from what to what and where, the identifiers named, the candidate affected documents matched against the register, the disciplines to consult with the reason for each, and the numbered questions reviewers must answer, with UNKNOWN wherever the description is silent. Prepares the record only: never approves, classifies the change, decides replacement in kind or makes any hazard or safety judgement. Use when the user asks to "raise an MoC for this", "prepare the change request intake", "which documents does this change touch", "who needs to review this change" or "draft the MoC form from this email". Do not use for tracking who owes information to whom across disciplines, use interface-register-builder instead. Drafts for human review; never approves, authorises or signs off.

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

Sweeps the last 24 hours of email, chat messages and meeting transcripts for commitments in both directions, what the user promised others and what others promised the user, reconciles them against a running commitments ledger (open, done, overdue), lists overdue items first and returns the updated ledger plus a proposed task list as Markdown for the user to save. Use when the user asks to "check my commitments", "what did I promise", "what am I owed", "did anything slip" or "run the commitment sweep". Do not use for a general morning summary of mail, calendar and mentions, use custom-daily-brief instead. Drafts for human review; never approves, authorises or signs off.

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

Sorts a personal inbox backlog into five buckets (needs-reply-today, needs-reply-this-week, waiting-on-others, FYI, noise), writes DRAFT reply text for the messages that need an answer (up to 10 per run), and returns a dated triage report as one Markdown document. Lists moves or archives only as proposals for the user to perform, and only where a rule the user supplied says so; the agent changes nothing in the mailbox. Use when the user asks to "triage my inbox", "sort my mail", "clean up my inbox", "catch up after leave" or "what needs a reply today or this week". Do not use for a shared support queue or helpdesk export, use ticket-triage-pack instead; for what the user promised or is owed, use commitment-catcher; for one named thread, answer directly. Drafts for human review; never approves, authorises or signs off.

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

Track vendor support tickets and RMA cases across multiple vendors. Use when managing support ticket lifecycle, updating ticket status from vendor emails, generating status reports, or identifying tickets needing follow-up.

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

End-to-end vendor procurement workflow orchestrating RFQ creation, email sending, vendor response tracking, and client-facing estimate generation. Use this skill when managing the full quote-request-to-client-estimate pipeline, coordinating between vendor-rfq-creator and vendor-estimate-creator skills with email automation and status tracking.

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

フォルダ型のタスクチケット（1ファイル1タスク、todo/doing/blocked/done フォルダ）を定期的に1件ずつ拾って実行し、結果をチケットに書き戻すスキル。毎回、状況を一目で把握できる看板ボード形式のダッシュボード（tasks/dashboard.html）も更新する。Coworkのスケジュール実行（1時間ごと等）から呼ばれる想定。「タスクを1件処理して」「tasksフォルダをチェックして」「タスクランナーを実行」「task-runner」「今日のタスクを進めて」「タスク管理の初期設定」「タスクの状況を見せて」「タスクのダッシュボード」「看板ボード」などと言われたら、明示的にスキル名が出ていなくても必ずこのスキルを使うこと。

Cross-reference project artifacts (WBS, meeting minutes, requirements docs) by date, participant, and action items. Extract commitments from meeting minutes and link to WBS tasks. Generate traceability reports showing which decisions were captured in which documents.

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

Prepare comprehensive meeting assets including agendas, reference materials, decision logs, and action items. Use when user says "prepare meeting", "create agenda", "meeting prep", "会議準備", or needs bilingual (Japanese/English) meeting documentation for cross-regional teams. Triggers include requests for decision log templates, action item tracking, or compiling reference materials from project estimates and specs.

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

Review meeting minutes documents for completeness, action item clarity, decision documentation, and consistency with source materials like hearing sheets. Use when validating meeting minutes quality or preparing minutes for distribution.

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

Generate strategic-consultant-grade meeting minutes from transcripts or notes in Japanese OR English (matching the source language), then run a self-review loop (max 3 iterations) that checks for internal contradictions, action-item omissions, speaker-name errors, and date/day-of-week mistakes before reporting completion. Use this skill whenever the user asks to draft meeting minutes, summarize a transcript, or document a meeting discussion — including Japanese-language transcripts (議事録 / 会議メモ / 文字起こし) and English-language transcripts.

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

Format documents for Japanese enterprise approval workflows including ringi (稟議), purchase requests (購入申請), and internal proposals. Handles bilingual requirements, proper keigo levels, required approval sections, and corporate template compliance.

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

標準原価差異分析スキル。標準原価（予定原価）と実際原価の差異を価格差異・数量差異に分解し、 材料費・労務費・製造間接費のカテゴリ別に集計・分析する。差異の有利/不利判定、 責任部門の特定、根本原因の仮説提示を行う。CSVデータのアップロードによる自動分析に対応。 Use when: 製造原価の差異分析を行いたいとき。標準原価計算制度の運用、 月次原価差異レポート作成、原価低減活動の効果測定に使用。 Triggers: "標準原価", "原価差異", "価格差異", "数量差異", "standard cost", "cost variance", "price variance", "quantity variance", "予定原価", "操業度差異", "原価管理"

Periodic inbox scan that categorizes new emails by project/client, identifies action-required items, and generates prioritized summary with FYI/requires-response/requires-action/blocked-waiting classifications. Use for inbox overview, project-based email grouping, or action item extraction.

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

Compose professional internal emails for coordination tasks like vendor quote requests, task delegation, and follow-up communications. Generates bilingual (JA/EN) email drafts with proper business tone. Use when user needs to draft internal emails for vendor RFQ forwarding, quote compilation requests, status updates, or task delegation.

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

Track and update action item status from natural language updates like 'Seanのメールには返信しておいた' or 'Lu対応予定'. Integrates with daily-comms-ops workflow. Use when managing action items across communication channels.

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

Analyze email threads to extract current status, pending actions, timeline of events, and identify stale/outdated information. Use when asked to summarize email conversations, find outstanding action items in email chains, or detect when a thread summary is out of date.

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

Analyze inbox emails to identify action-required items, prioritize by urgency/importance, classify by topic, and draft contextual replies. Use when triaging unread emails, prioritizing inbox, generating response drafts, or tracking email response status.

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

Use when a learner needs a structured review session prioritizing high-value topics by recency, error history, and upcoming deadlines.

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

Use when scheduling and executing review sessions at scientifically-calibrated expanding intervals for long-term retention.

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

Use when creating, testing, or updating active-recall flashcards grounded in session concepts to reinforce retention.

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

Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.

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

intake 成果物を Notion へ初回公開したいとき、ヒアリングをやり直さず Notion 側だけ更新して再公開したいときに使う。

dev-graph の1 featureを exact 13 task specsへ分解したいとき、独立評価後に13-entry inventory・13-node DAGを atomic promotionしたいときに使う。