菜单
Run a 5-minute personal standup for a solo dev — what shipped yesterday, what's blocked, what's next today. Use when the user asks for a daily check-in, says "what should I work on today", "what did I do yesterday", or wants to break out of a productivity slump.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | standup-solo |
| description | Run a 5-minute personal standup for a solo dev — what shipped yesterday, what's blocked, what's next today. Use when the user asks for a daily check-in, says "what should I work on today", "what did I do yesterday", or wants to break out of a productivity slump. |
A solo standup is three questions, hard limits:
## Standup — YYYY-MM-DD
**Yesterday (shipped):**
- <thing 1>
- <thing 2>
**Yesterday (started but not finished):**
- <thing> — <why not done>
**Blocked:**
- <thing> — <waiting on what / who>
**Today's #1:**
> <one sentence, action-form>
**Today's #2 and #3 (only if #1 finishes):**
- <thing>
- <thing>
To make output sharp, the user can paste any of:
git log --since="yesterday" --author=<me> --onelineIf the dev gives nothing, ask one question only: "What did you work on yesterday — give me 3 bullets, ugly is fine."
Input (raw):
"yesterday i fixed a bug in the auth flow, started on the new pricing page but it's like 60% done, also replied to like 8 customer emails. today i need to finish pricing page and figure out why stripe webhooks are firing twice."
Output:
## Standup — 2026-04-30
**Yesterday (shipped):**
- Fixed bug in auth flow.
- Replied to 8 customer support emails.
**Yesterday (started but not finished):**
- New pricing page — ~60% done; carry over to today.
**Blocked:**
- (none reported)
**Today's #1:**
> Ship pricing page to production (the remaining 40% — copy, layout, deploy).
**Today's #2 and #3 (only if #1 finishes):**
- Investigate duplicate Stripe webhook firings.
## 站会 — YYYY-MM-DD
**昨日已交付：**
- <项 1>
- <项 2>
**昨日开了头没做完：**
- <项> — <为何没做完>
**阻塞：**
- <项> — <等谁/等什么>
**今日 #1：**
> <一句话，动词开头>
**今日 #2 和 #3（仅当 #1 完成后再做）：**
- <项>
- <项>
Draft a launch tweet or short thread for a solo product launch on X / Twitter. Use when the user is shipping something (new product, major feature, side project) and asks for a launch post, "help me announce X", or mentions Product Hunt / Show HN / X launch.
Convert a vague user complaint into a reproducible bug report a solo dev can act on. Use when the user pastes a confusing customer message, says "user says it's broken but I can't repro", "this email makes no sense", or wants to triage a bug report.
Generate a user-facing CHANGELOG entry from raw git log output. Use when the user is preparing a release, says "what changed since last version", asks to write release notes, or wants to summarize a batch of commits for end users.
Draft a polite-but-firm reply to a tricky customer email — refund request, scope creep, complaint, billing dispute. Use when the user pastes a customer email and asks for a reply, mentions "how do I respond", "user is asking for a refund", "they want a discount", or any awkward customer-facing communication.
Run a lightweight, blame-free postmortem after an incident, failed launch, or missed deadline — for one person. Use when the user says "that didn't go well", "the launch flopped", "we had an outage", "I missed my deadline", or wants to learn from a recent failure.
Force a fast, regret-minimizing product decision when a solo founder is stuck choosing between options. Use when the user is paralyzed by a binary or tri-way choice (build A vs B, ship now vs polish, free vs paid, etc.), says "I can't decide", "should I", or asks for a sanity check on a roadmap call.