메뉴
Turn today's coding sessions into a standup update — what you did, what's blocked, what's next — from your own OpenStory store. Use when the user asks "write my standup", "what did I do today", "standup", or "summarize today's work".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Narrate the story of a project or topic from your session history — the key decisions and turning points, as a deterministic timeline grounded in real sessions and git. Use when the user asks "tell the story of <project>", "how did <X> come to be", "trace the arc of <topic>", "what's the history of this", or wants a narrative built from the record (not a vibe summary).
Prime yourself with prior OpenStory context before starting — pick up exactly where the last session on this project left off: what was done, what's open, the tools used. Use at the START of work, or when the user says "where did we leave off", "resume", "pick up where I left off", "catch up on this project", or "what was I doing here".
See who on your team has an active or recent OpenStory session and what each person is working on — live roster, per-teammate summaries, and recent focus. Requires federated sessions (multiple hosts/users reporting to one store). Use when the user asks "who's working right now", "what is <teammate> on", "team activity", "what did my team do today", or "sync me before our standup".
Show where your time actually goes across coding sessions — by project, by hour, and how focused vs scattered your work is. Distinct from cost (money) and tools (frequency). Use when the user asks "where does my time go", "how much time on X", "when am I most productive", "am I focused or scattered", or "time breakdown".
Show which tools and commands you rely on most across coding sessions — tool histogram, top shell commands, and Read:Write ratio. Frequency, not duration (that's time) or cost (that's cost). Use when the user asks "what tools do I use most", "my top commands", "what do I reach for", "how often do I edit vs read", or "tool breakdown".
Watch the work happening on a branch or project through OpenStory and summarize it live as it streams — a real-time feed of tools and edits plus a rolling summary of what the work is converging on. Use when the user says "watch this branch", "what's happening on <branch> right now", "stream the work", "follow along live", "show me activity as it happens", or "tail the agent on <project>".
| name | standup |
| description | Turn today's coding sessions into a standup update — what you did, what's blocked, what's next — from your own OpenStory store. Use when the user asks "write my standup", "what did I do today", "standup", or "summarize today's work". |
Compose a standup from the day's sessions. Pull → synthesize. Ground every line in the sessions; don't pad.
Call the OpenStory MCP tools (named mcp__openstory__*):
mcp__openstory__list_sessions with a 1-day window — today's sessions (label,
project, branch, event counts).mcp__openstory__session_synopsis (goal, tools,
errors) and/or mcp__openstory__session_story to recover what happened and what
was left open.Standup — <date>
Did:
• <completed work, grounded in the sessions>
Blocked:
• <unresolved errors / open threads, or "nothing blocking">
Next:
• <queued or explicit next steps surfaced in the sessions>
<N> sessions · <M> turns · top tools: <short histogram>
Infer Blocked from unresolved errors or trailing unfinished work; infer Next from explicit TODOs or where a session left off. If a field is genuinely empty, say so rather than inventing filler.
/openstory:recap.