メニュー
Use when running the twice-daily project progress pulse — pulling Jira/Linear tasks and sending a Slack alert on key project movement (status changes, blockers, due-soon items).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when preparing notes for a 1:1 with a report, drafting written feedback, or summarizing a person's recent work/contributions ahead of a conversation or review cycle.
Use when asked to generate or update architecture diagrams or ER (entity-relationship) diagrams from the codebase — the code is the source of truth, not existing docs.
Use when the user asks how to reduce Claude Code costs, manage token usage, choose the right model for a task, or wants a review of whether a session/workflow is running efficiently.
Use when the user asks for a standup update, daily summary, "what did I work on yesterday", or wants to recap recent commits before a team sync.
Use when investigating a bug, test failure, or unexpected behavior and proposing a fix — always runs investigation in Plan Mode so no code changes happen until the root cause and approach are confirmed.
Use when writing or reviewing code that crosses a trust boundary (user input, external APIs, file/network/DB I/O) — guards against invalid input, injection, unsafe failure modes, and missing validation at the edges without over-defending internal code.
| name | jira-progress-pulse |
| description | Use when running the twice-daily project progress pulse — pulling Jira/Linear tasks and sending a Slack alert on key project movement (status changes, blockers, due-soon items). |
Runs twice daily (morning/EOD) as a scheduled routine. Pulls task state from Jira or Linear, identifies what actually matters to an EM, and posts a short Slack alert — not a full dump.
Pull current state via the official MCP servers — don't scrape or hand-roll API calls; the official connectors handle auth, pagination, and stay current with the API:
linear plugin / official Linear MCP server): list_issues
filtered by team/project, list_cycles for the active cyclesearchJiraIssuesUsingJql with a JQL scoped to the
project + sprintclaude mcp add / Settings → Connectors) rather than falling back to
scraping or asking the user for raw API tokens.Filter for what's "key progress", not noise:
Draft a short Slack message (not a wall of text):
📊 Project Pulse — <project> (<AM/PM>)
✅ Done: <issue keys/titles, max 3>
🚧 Newly blocked: <issue keys — flag these first, an EM cares most here>
⏰ Due soon, not started: <issue keys>
Omit any section with nothing to report — don't pad.
Send via the configured Slack integration/webhook. If no Slack MCP/integration is connected yet, say so and show the drafted message instead of failing silently.
/schedule (runs this skill
twice daily, e.g. 9am and 5pm) rather than running it ad hoc.