close-day ยท diff
git:20261007.e522be7 to git:20261008.3bb2705
29 added, 46 removed. Audit A to A.
---
name: close-day
- description: End-of-day ritual that records a resume state, triages sharing receipts, and confirms carry-forward.
+ description: Review today's daily log, mark confirmed tasks complete, and optionally capture what changed.
disable-model-invocation: true
---
# Close Day
- Close today's active loop without turning the ritual into a portfolio review.
-
- ## 1. Load today's cockpit
-
- Read `AGENTS.md`, resolve today's note, and inspect the schema-defined sections corresponding to:
-
- - daily outcome and next action;
- - active focus and work notes;
- - ideas or receipts worth sharing;
- - ready-to-resume state;
- - carry-forward items.
-
- If the note is missing, stop and offer `/daily`. Sparse sections trigger a question, not an
- inference of inactivity.
-
- Completion: current state, unresolved work, and captured receipts are visible.
-
- ## 2. Record a resume state
-
- Have the user confirm:
+ A lightweight, optional check-in. The daily note remains the user's log, not a status report.
- - outcome state: complete, deliberately stopped, or blocked;
- - what is now true;
- - the next visible action;
- - the file, link, or command needed to resume.
+ ## 1. Read today's log
- Draft one concise resume state and obtain approval before writing it.
+ Read the vault's `AGENTS.md` and `../vault/SKILL.md` for paths, ownership, and safe writes.
+ Resolve today's note using the real local date, on weekdays or weekends alike.
- Completion: future-you can resume without reconstructing the task.
+ If the note is missing, stop and offer `/daily`; do not create it as a side effect.
+ Read `## Today`. For an older-format note, read the existing entries without migrating its structure.
+ Show unchecked tasks briefly as unresolved entries, not assumed commitments for tomorrow. Ignore empty
+ checkbox placeholders. Sparse notes are evidence gaps, not proof of inactivity.
- ## 3. Triage receipts
+ Completion: today's recorded entries and unresolved tasks are visible.
- For every captured sharing idea, ask for one decision:
+ ## 2. Ask one optional question
- - **Promote:** hand the sourced idea to `capture-receipt`.
- - **Defer:** leave it for the weekly review.
- - **Discard from pipeline:** remove its sharing candidacy without deleting the underlying work note.
+ > What changed today, and is there anything you don't want to forget?
- Only explicitly public-safe material may proceed to publication drafting. Never publish, claim
- publication, or expose confidential information.
+ If the user already supplied this information, use it without asking again. If they have nothing to
+ add or correct, finish without modifying the note.
- Completion: each receipt is promoted, deferred, or discarded.
+ Use only explicit user confirmation to:
- ## 4. Confirm carry-forward
+ - mark an existing task complete;
+ - append thoughts, events, observations, or links as ordinary bullets;
+ - append a short `Resume:` bullet only when the user explicitly requests a reminder for resuming work.
- Extract unfinished promises and blockers with source locations. Ask which items truly belong to the
- next workday. Prepare one canonical carry-forward section containing only confirmed items.
+ Preserve the user's voice. Leave unresolved tasks where they are; no automatic migration, external
+ activity reconstruction, sharing-idea triage, or additional questionnaire.
- Nothing rolls forward automatically; unselected work remains in its source system.
+ Completion: the requested changes are clear, or there is nothing to write.
- Completion: tomorrow's candidates are confirmed and no commitment was inferred.
+ ## 3. Write and verify
- ## 5. Write and verify
+ Preview the exact changes and obtain approval using the vault safe-write flow. Update confirmed
+ checkboxes in place and append new bullets under `## Today`. For an older-format note without that
+ heading, append the approved bullets at the end; preserve its existing sections.
- Preview all named-section changes together. After approval, use the `vault` safe-write flow and
- respect ownership declared in `AGENTS.md`. Reread the note and verify the resume state and single
- carry-forward section.
+ Keep shutdown, carry-forward, idea-triage, and resume sections out of this operation. Do not change
+ other notes or external systems.
- Return only the outcome state, resume action, receipt decisions, confirmed carry-forward, and any
- unresolved item.
+ Reread the affected content and verify that unrelated entries were preserved and every change traces
+ to the user's confirmation. Return the note path and exact changes, or state that nothing changed.