メニュー
This skill should be used when the user asks for "standup", "daily standup", "what did I do yesterday", "what should I work on today", "standup summary", or at the start of a workday.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user asks "should I extract this?", "is this abstraction worth it?", "am I over-engineering?", "should I DRY this up?", or when evaluating whether to create a helper, utility, base class, or shared module. Use for any "extract vs inline" decision.
This skill should be used when reviewing a design proposal, RFC, technical plan, or before starting implementation. Use when asking "what could go wrong?", "what are we assuming?", "where is this fragile?", or "what happens if X changes?". Surfaces hidden dependencies and untested beliefs.
This skill should be used when the user asks to "review this code", "check this implementation", "what's wrong with this code", "review my changes", "code review", or when examining code for quality issues.
This skill should be used when asking "is this module too complex?", "why is this hard to change?", "what's causing coupling here?", or before refactoring a tangled system. Use to audit for accidental complexity, circular dependencies, god objects, and layering violations.
This skill should be used when the user asks to "help me debug", "why isn't this working", "this is broken", "debug this", "find the bug", or when systematically investigating an issue.
This skill should be used when asking "should we add this library?", "is this dependency safe?", "should we upgrade X?", or when evaluating npm packages, gems, crates, or any third-party code. Assesses maintenance risk, security, and exit strategy.
| name | standup |
| description | This skill should be used when the user asks for "standup", "daily standup", "what did I do yesterday", "what should I work on today", "standup summary", or at the start of a workday. |
When this skill is invoked:
Run the standup aggregation script:
bash ~/.claude/skills/standup/scripts/aggregate-standup.sh
Read the generated summary from the script output
Present the standup in this format:
# Daily Standup — [Date]
## Yesterday
[Summary of work from dev-os events]
### Completed
- [Files modified with context]
- [Decisions made]
### Sessions
- [Number of sessions, total duration]
### Pull Requests
- [PRs opened/merged yesterday]
- [PRs awaiting your review]
## Today
[Based on incomplete work, pending items, and patterns]
### Priorities
1. [Most important item based on yesterday's work]
2. [Follow-up items]
3. [Unfinished work]
## Blockers
[Any friction patterns or issues identified]
## Notes
[Any relevant context for the team]
The standup aggregates from:
~/.claude/dev-os-events.jsonl - All dev-os eventsIf the script output is insufficient, ask:
# Daily Standup — March 2, 2026
## Yesterday
### Completed
- Implemented tradeoff auto-capture system (3 files, 150 lines)
- Updated weekly review aggregation for session duration tracking
- Fixed marker expiry from 1h to 24h for long sessions
### Sessions
- 2 sessions, 4.5 hours total
- 1 context compaction (long session)
### Decisions Made
- Chose auto-capture over blocking for tradeoff documentation
- Extended marker expiry to support full-day sessions
### Pull Requests
**Opened (1):**
- [gusto-database_pull] Add validation audit generator (OPEN)
**Merged (2):**
- [.dotfiles] Enhance loop-detector state management
- [gusto-database_pull] Fix template context spec coverage
### Pending Reviews (1)
- [zenpayroll] Update GraphQL federation config
## Today
### Priorities
1. Test the auto-capture agent hook in real usage
2. Continue Phase 2 of Dev OS enhancements
3. Review weekly data for friction patterns
## Blockers
- None identified
## Notes
- High Read tool failure rate (789 failures) needs investigation
- Consider adding diagnostic logging to skill-gap-detector