القائمة
Generates a quick morning briefing with what happened, what's stuck, and what needs attention today.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | standup-brief |
| version | 1.0.0 |
| description | Generates a quick morning briefing with what happened, what's stuck, and what needs attention today. |
| category | meeting-prep |
| trigger | Before daily standup or as a morning check-in |
| autonomy | autonomous |
| portability | universal |
| complexity | basic |
| type | generation |
| inputs | [{"name":"sprint_tickets","type":"structured-text","required":true,"description":"Current sprint tickets with status, assignee, priority, days in status, and recent changes."},{"name":"previous_day_snapshot","type":"structured-text","required":false,"description":"Yesterday's ticket statuses (enables \"what changed\" detection)."}] |
| outputs | [{"name":"standup_brief","type":"structured-text","description":"3-section briefing (Happened, Stuck, Attention) with ticket-level detail."}] |
| model_compatibility | ["claude","gpt-4","gemini","llama-3"] |
Generate a concise morning briefing that answers three questions: What happened since yesterday? What's stuck? What needs attention today?
Compare current ticket statuses against the previous day (if previous_day_snapshot provided) or infer from last_updated dates:
List as concrete events: "{Person} completed {ticket} ({SP} SP)" or "{Ticket} moved from In Progress to In Review."
Apply a simplified version of stuck-ticket detection:
For each stuck item, note: ticket key, assignee, days stuck, and why (if detectable from linked issues or labels).
Based on priority and sprint timeline:
Keep it short — this is a 2-minute read, not a report.
## Morning Brief — {date}
### What Happened
- {Event 1}
- {Event 2}
- ...
### What's Stuck
- **{TICKET-KEY}** ({summary}) — {assignee}, stuck {N} days. {Reason if known.}
- ...
{If nothing stuck: "Nothing blocked or stale."}
### Needs Attention Today
1. {Action 1} — {who} — {why it matters}
2. {Action 2} — {who} — {why it matters}
3. ...
{If nothing: "Sprint is on track. No immediate actions needed."}
last_updated dates. Note: "Change detection based on last-updated timestamps — may miss same-day changes."Generates messages suggesting a ghost-done ticket be transitioned to Done. Helpful tone, evidence-based, always asks rather than commands.
Generates contextual, humble messages designed to unblock stuck tickets. Use when a stuck ticket needs a nudge comment.
Evaluates whether epics are ready for PI or quarter planning by scoring 7 readiness dimensions.
Computes team capacity for a sprint or PI from headcount, PTO, and run-rate buffer.
Estimates completion probability for remaining work using velocity distribution and Monte Carlo-style simulation.
Annotates agent output with inline source citations to eliminate hallucination risk. Ensures every metric, claim, and ticket reference is traceable to a specific data source.