← the whole session plugin/skills/complete-agentic-task/SKILL.md
Run the mandatory completion protocol before returning control. Use when finishing any substantive piece of work.
Complete Agentic Task
Execution
Dispatch a Sonnet subagent to run this entire skill. The subagent:
- Fills in every section below using the conversation context
- Prints the completed template directly to the user
- Files a compaction via
/compact-agentic-session— that skill records it the way you've configured it: to a server if you've set one up, otherwise as a local file — or if a compaction already exists for this session, updates it with the work summary
Admin Link (MANDATORY — post-completion)
When the subagent files a compaction via /compact-agentic-session, it MUST print a direct link to it after:
📎 {wherever /compact-agentic-session says the compaction now lives}
If you have a local admin dashboard configured for browsing compactions (optional — see /alignment-harness:harness-setup; one reference setup is at a URL like http://localhost:3000/admin2/session-compactions?q={sessionId}), print that link. Otherwise print the local file path the compaction was saved to. Either way, this proves the compaction was persisted and lets the person you're working with jump directly to it.
The parent agent should pass the subagent: the user's original request (verbatim), what was done, what files were touched, and any gaps.
Template
You are about to complete some work product. Include the following in your response to the user.
Each section contains required reasoning and format. All communications must be:
- UX-first, intent-first, UX-impact, plain clear precise non-vague
- Translating the nuance of "when X then Y"
- Every sentence: immediately understandable, non-obscuring of actual constraints/nuance, all signal no noise
- Connecting the dots between intent and actuality
- Never using jargon to replace actual meaning
- Never obscuring the actual UX flow that results in impact
- Never using more words than required to trigger immediate full understanding
Required Sections
You asked for
{specific verbatim quote of what was requested from user}
What I was working on
{aspect of user quote I just acted on}
My read of the overarching initiative
{If X is my intent, what's my best sense of what X serves, is designed to serve}
My read of your intent
{Exactly what I think your intent was, framed as the explicit change from present moment desired, specifically articulating only what the UX would actually change if I succeeded}
My progress
{What actually got done, vs what's incomplete, to be fully aligned with your verbatim words, in one sentence each}
Exact requirements I sensed you had
{each requirement — mark with X if unaddressed}
- [x] addressed requirement
- [ ] unaddressed requirement
How you could check it
{the exact simplest way the user can consume this work product — NEVER programmatic, NEVER "check logs", EVER — the UX simplest steps to see if this fulfilled its intent}
Rules
- "You asked for" must be a direct quote, not a paraphrase. Copy their words.
- "My read of your intent" is about the UX delta — what changes for a human using the product. Not about code, files, or architecture.
- "My progress" must be honest about gaps. One sentence per item. No padding.
- "How you could check it" is always a human action in the product UI. "Open the app, click X, see Y." Never "run this script" or "check the DB."
- If you cannot describe how to check it in the UI, that's a gap — say so.
- Do not skip sections. Do not combine sections. Do not reorder.
- If your deliverable is a file in a notes vault (for example, one reference setup keeps this at
api/docs/intent/— replace with wherever your own project keeps this kind of documentation) and you have Obsidian (or another linked-note vault) configured (optional — see/alignment-harness:harness-setup), open it there for the person you're working with:
Example:open "obsidian://open?vault=<your-vault-name>&file=PATH_RELATIVE_TO_VAULT_WITHOUT_EXTENSION&newtab=true"open "obsidian://open?vault=intent&file=proposed/LP-042-checkout-fix&newtab=true"Do not include the.mdextension in the URI. If Obsidian isn't set up, just print the file's path so the person can open it directly.