stop
/stop
Stop and reconcile the active Obsidian task note. Use when the user says "stop", "stop task N", "wrap up", "pause this task", "I am done", invokes $stop, clearly ends tracked work, or before tracked implementation or review work in the brain is declared complete. Record material progress and move the task to Done when the outcome is complete or To Do when work remains, asking when the context is ambiguous.
- Author
- lucastamoios ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Stop and reconcile the active Obsidian task note. Use when the user says "stop", "stop task N", "wrap up", "pause this task", "I am done", invokes $stop, clearly ends tracked work, or before tracked implementation or review work in the brain is declared complete. Record material progress and move the task to Done when the outcome is complete or To Do when work remains, asking when the context is ambiguous.
Triggers from the description
Original author description
Stop and reconcile the active Obsidian task note. Use when the user says "stop", "stop task N", "wrap up", "pause this task", "I am done", invokes $stop, clearly ends tracked work, or before tracked implementation or review work in the brain is declared complete. Record material progress and move the task to Done when the outcome is complete or To Do when work remains, asking when the context is ambiguous.
How it works
- Private configuration
- Workflow
SKILL.md preview
--- name: stop description: Stop and reconcile the active Obsidian task note. Use when the user says "stop", "stop task N", "wrap up", "pause this task", "I am done", invokes $stop, clearly ends tracked work, or before tracked implementation or review work in the brain is declared complete. Record material progress and move the task to Done when the outcome is complete or To Do when work remains, asking when the context is ambiguous. --- # Stop ## Private configuration For an ordinary invocation that needs personal defaults or integrations, read the installed `skill-config` skill and resolve the `profile.<key>` fields below. Load only context relevant to the request. Command examples with these fields are templates; substitute configured values as quoted arguments before execution. Ask for required missing fields and skip unavailable optional integrations. For a prepared worker packet, use only its declared access and supplied configuration. The coordinator resolves private defaults and passes the minimum required values or permitted resources. A worker must not load a machine-wide profile or unrelated context unless the packet explicitly permits it. Close one explicit work session tracked in `profile.paths.tasks`. Never act on a task merely because automatic session metadata mentioned it. Before declaring tracked implementation or review work in the brain complete, reconcile its active Obsidian task through this workflow. A final answer is not a substitute for the task update. ## Workflow 1. Resolve the task started through `$start`, or accept an explicit ID. If unknown, list In Progress tasks and ask the user. 2. Inspect what this session actually completed. 3. Choose `Done` when the requested outcome is clearly complete. Choose `To Do` when work remains, including pauses, review handoffs, blockers, or unfinished follow-ups. 4. Use an explicitly supplied valid lane when the user deliberately requests one. Otherwise infer Done or To Do from the session. Move without asking when the evidence is clear; ask a short clarifying question when it is not. 5. Append a concise note only for a material result, decision, blocker, handoff, or next step with `profile.paths.scripts/tasks.py note --id <filename-slug> --text "<note>"`. 6. Move the task with `profile.paths.scripts/tasks.py move --id <filename-slug> --lane "<lane>"`. This updates `status`, `updated`, `completed`, and the task history. 7. Report the note and final lane. For a review handoff, also report the absolute worktree path, one exact copy-paste review command, and the pull request URL and current live state when one exists. Suggest `$retro` when durable project knowledge or a concrete workflow lesson was produced. State the reason briefly, and run it only if the user explicitly asks. If nothing material happened, skip the note. If the task files or command are unavailable, report the exact failure and do not claim an update.
Files in this package (2)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · lucastamoios/skills | 100 | MIT |
| emaballarin/ccplugins | 100 | MIT |
| jtpio/xtralab | 100 | BSD-3-Clause |
| vagonhq/marj | 100 | MIT |
Database snapshot: 13.11.2026 · package version a2b0a8d238e2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95obsidian-tracker-track-stop
Stop tracking and save session to Obsidian. Use when the user invokes /track-stop. - 95obsidian-tracker-done
Complete a task and move to Done on kanban board. Use when the user invokes /done. - 90complete-task
Mark a task as completed. Use when the user wants to mark a task as done or complete. - 90complete-task
Mark a task as completed. Use when the user wants to mark a task as done or complete. - 90to-note
Save content as a Markdown note in the user's Obsidian vault. Use for /to-note, or when asked to save, record, or send something to Obsidian or the notes vault. - 100save
Pause work at a clean stopping point and get ready to continue in a fresh session — commit changes, write the work log, update memory, and leave a handoff note — as a page in the Cairn board's Handoff collection when one is set up, otherwise in .handoff/HANDOFF.md. If no work is…