메뉴
Morning startup workflow for daily notes, yesterday summary, agenda, status comments, meeting sections, and daily branch setup. Use when invoked as `$work-start` or when the user asks to start the work day.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
End-of-day — draft and post daily comments for tracked tickets missing a comment
Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track` or when the user asks to track a work item.
Start work on a Linear ticket by gathering context, planning, creating a branch/worktree, implementing, testing, opening a draft PR, and updating Linear. Use when invoked as `$linear-plan` or when the user asks to start a Linear ticket.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Load the shared skill from ~/.agents/skills/linear-plan/SKILL.md.
| name | work-start |
| description | Morning startup workflow for daily notes, yesterday summary, agenda, status comments, meeting sections, and daily branch setup. Use when invoked as `$work-start` or when the user asks to start the work day. |
Create or refresh today's daily note, populate yesterday summary and agenda, post daily status comments when appropriate, create meeting sections, and run $pr-daily.
On macOS, run every linear ... command outside the sandbox on the first
attempt so the CLI can access credentials stored in the system keychain. Use
scoped escalation with prefix_rule: ["linear"]. If a sandboxed command
reports No keyring entry or No API key configured, retry outside the
sandbox before asking the user to authenticate. Never print, log, or expose
linear auth token or an API key.
Determine paths:
today_date=$(date +%Y-%m-%d)
today_day=$(date +%A)
today_year=$(date +%Y)
today_file="${today_date} ${today_day}"
vault="$HOME/2ndBrain"
notes_dir="${vault}/daily-notes/${today_year}"
Create today's note if missing from ${vault}/templates/daily-note.md. Replace Obsidian date placeholders and fix the yesterday link to the most recent earlier daily note.
Update startup checks:
gh api orgs/getditto/actions/runner-groups/8/runners.#ci unchecked unless a Slack integration is available.Build the ## Yesterday section from:
Preserve the auto-population comment for reruns.
Build today's agenda:
triage, backlog, or unstarted state for the active cycle.If calendar tools are unavailable, report that and continue with Linear/GitHub sections.
Post daily Linear status comments for in-progress tickets that do not already have today's comment by the user. Use linear-cli:linear-cli before Linear CLI commands.
Add or update Work Items sections in today's note using the same format as $work-track; set commented:: true for tickets that received comments.
Populate empty meeting sections under # Meetings with one H2 per meeting.
Run $pr-daily to set up the daily branch and draft PR.
Report daily note path, previous note, meetings, tickets needing comment, tickets to pick up, branch, and PR.