القائمة
Use when generating the weekly project progress summary (run Fridays) from Jira/Linear — covering what shipped, what's at risk, and what's coming next week.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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.
استنادا إلى تصنيف SOC المهني
| name | weekly-progress-summary |
| description | Use when generating the weekly project progress summary (run Fridays) from Jira/Linear — covering what shipped, what's at risk, and what's coming next week. |
A higher-altitude rollup than the twice-daily pulse — meant for stakeholders, not just yourself. Runs once a week, typically Friday afternoon.
Pull the week's activity through the official MCP servers (same
connectors as jira-progress-pulse — Linear MCP and the official
Atlassian Remote MCP server) rather than ad hoc API calls:
list_issues with date filters, list_cycles)project = X AND updated >= -7d, plus a sprint/board view for burndown contextOrganize into:
## Week of <date> — <Project> Summary
**Shipped this week**
- <outcome-level bullets — "Shipped X", not "closed JIRA-123">
**At risk / blocked**
- <issue + why + what's needed to unblock — be specific, this is the
section stakeholders actually act on>
**Next week**
- <top 3-5 priorities pulled from the upcoming sprint/cycle>
**Velocity note** (optional)
- <only include if the trend is notable — don't manufacture a metric>
Write for the audience: translate ticket titles into outcomes a non-engineer would understand. Group related tickets into one bullet.
Show the draft for review before sending/posting (Slack, email, Confluence — whatever the configured destination is). Don't auto-publish.
/schedule for Friday afternoons.