Menu
Archive Done tickets (with linked notes) to C:\Archive\ — all kanbans or a single one. Request confirmation before any physical action.
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
Generates a complete eval.json for a Claude Code skill via 2-pass pipeline — local draft with Ollama (qwen2.5-coder:14b, $0, ~3min) then Sonnet refinement (claude -p headless, $0 via Max subscription). Launches final verify-eval for validation. Use when you want to cover a skill that doesn't yet have an eval.json, or in batch across multiple skills. Target: increase coverage of the skill auto-evaluation loop (ticket auto-evals-binaires-evaluateskills). Ex: /author-eval closeweek, /author-eval (no arg → interactive list), /author-eval --random 5 (batch).
End-of-day wrap-up — synthesize sessions, update daily note with observed patterns, detect WIP hobby in progress, verify essay-check overdue. Trigger when the user says one of these phrases: "closeday", "I'm stopping", "I'm done", "that's finished", "end of session", "good night", "good day", "stopping for today", "that's enough", "day finished", "I'm stopping now", "it's done" or via /closeday.
Guided commit on explicit request /commit — breaks changes into atomic commits ordered by layer, passes two validations (file selection, then message), handles branch (creation/switch with stash), then executes git add + git commit. Use whenever the user says /commit, 'commit that', 'make the commit', or wants to commit finished work. Never push, merge, rebase or reset EVER. Never commit outside this skill.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Scan the daily notes to extract ideas to capitalize on and links to process. Use when the user says "harvest", "do the harvest", "scan my notes", or when /harvest is late in the command-tracker, or at the end of a session if daily notes have been mentioned.
Complete vault scan over an extended period to detect emerging patterns, recurring ideas across different contexts, and deep connections. Use once a month or when the user says "harvest deep", "deep harvest", "analyze the vault".
| name | archivedone |
| description | Archive Done tickets (with linked notes) to C:\Archive\ — all kanbans or a single one. Request confirmation before any physical action. |
/archivedone # All kanbans
/archivedone [kanban] # A specific kanban (filename or path portion)
Read {VAULT_PATH}\{PROJECTS_FOLDER}\INDEX.md once.
Build the list of kanbans to process :
Special kanbans (always included unless kanban filter is applied) :
{VAULT_PATH}\{CLAUDE_CODE_FOLDER}\Claude Code Kanban.mdProject kanbans — for each project in the "Active projects" table :
[[...]] or direct path).md kanban file (usually Project management.md)If [kanban] parameter provided, filter the list (pattern matching on filename or path).
Read all discovered kanban files in parallel with Read.
For each kanban read, extract all items from the ## Done section.
Classify each item by type :
[[FileName]] or [[FileName|alias]] (Obsidian syntax)[[...]]Build two lists per kanban : tickets with link + tickets without link.
If all Done columns are empty → stop, signal to {USER_NAME} and do nothing.
Otherwise, display what will be proposed for archiving :
[Kanban Name 1] — [X archivable tickets] + [Y without link]
Archivable (with linked note) :
Will remain in Done (without linked note) :
(repeat for each kanban with non-empty Done)
Ask {USER_NAME} :
**ADR-XXX**) ?Wait for explicit response before Step 4.
Before any file movement :
{VAULT_PATH}\Archive\ exists (create if missing via bash, signal to {USER_NAME})Wait for confirmation before Step 5.
For each ticket validated in Step 3 :
{VAULT_PATH}\Archive\ via bash[TicketName].[ext] if collision (add _YYYYMMDD-HHMM before ext)For each kanban processed, empty only the archived tickets :
## Done
For each successfully copied ticket, delete the original from source folder via bash.
Display to {USER_NAME} :
Read {VAULT_PATH}\{CLAUDE_CODE_FOLDER}\command-tracker.md.
Find the /archivedone line and update its date to YYYY-MM-DD format (today).
If file missing or line missing : signal to {USER_NAME}, do not create.
| Situation | Behavior |
|---|---|
| Broken link (file doesn't exist) | Step 4 : display impossible path, ask {USER_NAME} : ignore or continue anyway |
| Ticket without linked note (plain text) | Display as "Will remain in Done", never archive |
| Empty kanban (0 items Done) | Include in report with count=0, no processing for that kanban |
| INDEX missing | Fatal error → stop, signal to {USER_NAME}, don't guess |
## Done section missing or malformed | Signal to {USER_NAME}, ignore kanban, continue |
| user says "no" in Step 3 | Stop, do nothing, return without action |
| {USER_NAME} excludes certain tickets | Ignore excluded tickets, archive others |
| Collision in Archive (file already exists) | Add _YYYYMMDD-HHMM before extension |
| Archive/ doesn't exist | Step 4 : create via bash, signal to {USER_NAME} |
## Done header — just empty it, never delete the section