| name | daily-refine |
| description | Launch refinement of tickets listed in the 🗂️ Refinement section of today's daily note. Invoke when the user says "/daily-refine", "let's do today's refinement", "refinement from daily", "launch plan refines", or "let's refine the tickets". Automatically reads the current daily note, extracts unchecked tickets, and chains /refine on each sequentially — without {USER_NAME} having to specify everything manually. |
Skill: /daily-refine
Eliminates friction from starting daily refinement: instead of manually specifying each ticket to /refine, this skill reads the daily note and orchestrates refinement in sequence.
Step 1 — Initialize variables
Read /home/vico/.claude/vault-config.json → extract VAULT_PATH.
Read {VAULT_PATH}/99 - Claude code/config/vault-settings.md → extract DAILY_NOTES_FOLDER.
Step 2 — Read today's daily note
Get today's date: date +"%Y-%m-%d".
Read {VAULT_PATH}/{DAILY_NOTES_FOLDER}/YYYY-MM-DD.md.
If the daily note doesn't exist → signal and stop: "No daily note for today — run /today first?"
Step 3 — Extract Refinement tickets
Locate the ### 🗂️ Refinement section in the daily note.
Extract all lines matching the pattern - [ ] [[...]] in this section.
Ignore:
- Lines
- [x] — already processed in the current session or a previous session
- Lines without
[[]] links (free text)
- Lines outside the Refinement section
Items without [[]] (orphans): do not skip silently. List them explicitly before Step 4 and ask {USER_NAME} for each:
- Move to Done directly (item resolved/thrown together — check in daily)
- Create a ticket via
/create-ticket (item that deserves to exist formally)
- Skip this session (leave as is)
Format:
⚠️ Refinement items without [[]] detected:
- "Text of item 1" → Done / ticket / skip?
- "Text of item 2" → Done / ticket / skip?
Process {USER_NAME}'s choices before moving to linked tickets.
If no unchecked tickets found:
- If the Refinement section is missing → "No Refinement section in today's daily note."
- If all are checked → "All Refinement tickets are already processed today ✅"
- In both cases, stop.
Step 4 — Present and confirm
Display the extracted list:
🗂️ Today's Refinement — X ticket(s) to process:
1. [[TicketName1|Title]]
2. [[TicketName2|Title]]
...
Ready to start?
Wait for {USER_NAME}'s confirmation. If the user says "no" or wants to remove tickets → adjust the list before starting.
Step 5 — Launch /refine in sequence
For each ticket in order:
- Announce: "Ticket N/X — /refine [[TicketName]]"
- Invoke
/refine [[TicketName]] — let /refine handle the entire discussion (exploratory or standard format depending on ticket type)
- Wait for {USER_NAME} to give a final outcome ("spec", "trash", "backlog V2", "blocker", "next", "follow-up")
- Move to the next ticket
Don't chain without confirmation — the pace is {USER_NAME}'s, not the skill's.
If the user says "stop" or "let's stop here" along the way → stop cleanly without forcing the rest.
Step 6 — Closure
When all tickets are processed or {USER_NAME} stops:
✅ Refinement complete — X/Y tickets processed.
Unprocessed tickets remain unchecked in the daily note — they will resurface on the next /daily-refine or via /today.
