with one click
daily
Daily session wrapper — start with backlog, work, commit, retro
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Daily session wrapper — start with backlog, work, commit, retro
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Manage the project backlog — add, list, filter, update, prioritize, and suggest work items
End-of-session retrospective — summarize work, update backlog statuses, update MEMORY.md
Commit, branch, PR, self-review, fix — then stop for human approval before merge
Pre-flight for parallel work — pick items, check file overlap, set statuses, generate terminal commands
Manage project backlog — add, list, filter, update, prioritize, suggest
Full ship cycle: branch, PR, self-review, fix, human approval, merge
| name | daily |
| description | Daily session wrapper — start with backlog, work, commit, retro |
| user-invocable | true |
A guided checklist for a productive session. Run at the start of a work session — it walks you through the full cycle.
| Invocation | Behaviour |
|---|---|
/daily | Full session flow (start → work → ship → close) |
/daily start | Just the opening steps (1–2) — see what's ready and pick work |
/daily wrap | Just the closing steps (4–5) — commit, retro |
Run /backlog (dashboard mode) to show:
Present a quick summary:
## Today's Board
🔵 In Progress: BL-012 (description), BL-018 (description)
⬜ Ready (top 3): BL-025 (p1/s), BL-031 (p2/xs), BL-014 (p2/m)
🔴 Blocked: none
Ask the user what they want to work on today:
/backlog next scoring)Once decided, set the item to in-progress via /backlog update BL-NNN status=in-progress.
Then hand off to the user: "Ready to go. Work on the task, then run /daily wrap when you're done — or I'll remind you."
STOP HERE and let the user work. Do not proceed to Step 3 automatically.
The user codes, tests, iterates. This step is implicit — the skill resumes at Step 4 when the user runs /daily wrap or asks to wrap up.
Run /commit to ship changes:
If no uncommitted changes exist, skip this step.
Run /retro to close out:
/commit (Step 4)/daily start, stop after Step 2/daily wrap, start from Step 4