メニュー
Optional workflow skill for Slack-style daily reports. Use only when the user works with Slack daily reports and, optionally, Notion worklogs/Todo pages; it summarizes today's work by project with progress percentages.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when starting a new session on a codebase, resuming interrupted work from a previous session, after making an architectural or design decision, or before ending a session or creating a PR — to create, update, or hand off docs/context/ project context files.
Use when a tool, command, sandbox, permission, network, dependency, or approval operation fails or repeats the same infrastructure error — classify the failure, cap retries, choose one bounded fallback, and stop before recovery consumes excessive tokens or time.
Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture, setting up dependency injection, refactoring tightly coupled code, managing singletons or service factories, or when the user asks about inversion of control, service containers, or wiring dependencies in Go.
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code.
Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.
Kotlin Coroutines and Flow patterns for Android and KMP — structured concurrency, Flow operators, StateFlow, error handling, and testing.
| name | daily-report |
| description | Optional workflow skill for Slack-style daily reports. Use only when the user works with Slack daily reports and, optionally, Notion worklogs/Todo pages; it summarizes today's work by project with progress percentages. |
| metadata | {"source":"born-here","summary":"Optional Slack/Notion 일일보고 workflow","routing":{"visibility":"contextual","risk_level":"low","task_types":["reporting"],"triggers":[{"kind":"keyword","values":["일일보고","데일리 리포트","daily report"]},{"kind":"intent","values":["summarize_work_for_slack"]}],"keywords":{"ko":["일일보고","보고","진척률"],"en":["daily report","slack report","progress"]},"use_when":["회사 Slack 일일보고 형식으로 오늘 작업을 프로젝트별 진척률과 함께 정리해야 하는 경우"],"do_not_use_when":["Notion 업무일지나 Done/Todo 형식으로 스캔 가능한 개인 기록을 작성하는 경우"],"requires":["today_session_context"]}} |
오늘 한 일을 회사 슬랙 일일보고로 정리한다. 목적기반 한 줄, 프로젝트별 묶음, 진척률 표기.
노션 개인 업무일지/Todo 정리는 다른 산출물 —
worklog-note참조. 이건 슬랙 보고용(평문, 표 X).
세션마다 다루는 태스크가 달라서 둘을 합친다:
notion-fetch로 그날 Done/진행 항목 가져와 보완. 페이지 URL은 사용자에게 확인.[YYYY-MM-DD]
<프로젝트명>
<작업명> (<진척%>, ~<데드라인>)
<작업명> (<진척%>)
기타
<항목> (<진척%>)
(100%) (40%, ~7/23) 형태. 데드라인 있으면 ~날짜.*텍스트* (단일 별표). ** 안 됨.기타로 빼거나 생략.**) 없나?