# Deliverable On Disk

> Use when about to mark a task as complete, done, finished, or shipped — verifies the deliverable actually exists as a file on disk, in a commit, or as a posted artefact. Blocks claiming completion based on chat output alone.

- Skill: `amitkot/deliverable-on-disk` (Agent Skill)
- Install (CLI): `npx skillmds@latest add amitkot/deliverable-on-disk`
- Raw SKILL.md: https://api.skillmd.com/api/skills/amitkot/deliverable-on-disk/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: amitkot (https://skillmd.com/u/amitkot)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/amitkot/deliverable-on-disk

---


# A task is only complete when its deliverable exists on disk

Don't mark a task done when the only evidence is what you said in chat. The deliverable has to actually exist: file written, commit made, PR opened, plan saved.

## Why

Chat output is ephemeral and not the artefact. If a user comes back later expecting "the plan we wrote" or "the script we built", they need it on disk. "I described the plan in the conversation" doesn't survive a new session, a teammate's review, or a context rotation.

## How to apply

Before declaring a task complete, verify the artefact exists where the user expects it:

- Asked to write a plan? It's on disk at the agreed path (e.g. `docs/plans/<slug>.md`).
- Asked to build a script? The file exists and runs.
- Asked to update a doc? `git diff` shows the change.
- Asked to open a PR? `gh pr view` returns it.

If the deliverable IS "an answer in chat" (a question), then chat output is the deliverable and this skill doesn't apply. Otherwise, verify the artefact exists before claiming completion.