# Cmd Done Check

> Ask the agent whether it finished everything or has more to do — a lightweight completeness gate for the end of any task

- **Type:** Skill
- **Install:** `agentstack add skill-olshansk-agent-skills-cmd-done-check`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Olshansk](https://agentstack.voostack.com/s/olshansk)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Olshansk](https://github.com/Olshansk)
- **Source:** https://github.com/Olshansk/agent-skills/tree/main/skills/cmd-done-check

## Install

```sh
agentstack add skill-olshansk-agent-skills-cmd-done-check
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Done Check

A quick self-interrogation to catch loose ends before declaring a task complete.

## Instructions

Answer each question honestly. If anything is incomplete, say so and ask the user whether to continue.

### 1. Did you do everything the user asked?

- Re-read the original request. Is every explicit ask addressed?
- Did you skip or defer anything without telling the user?
- Did you say "I'll also..." or "next, we should..." and then not do it?

### 2. Did you leave any loose ends?

- Are there TODOs, FIXMEs, or placeholder values you introduced that should be resolved now?
- Are there commented-out blocks, debug prints, or temporary stubs in the output?
- Are there follow-up steps you mentioned but didn't take?

### 3. Did you handle side effects?

- Are there related files, configs, or tests that should be updated but weren't?
- Did any rename, move, or deletion leave dangling references?
- If you added a skill/command/export — is it wired up and discoverable?

### 4. Are docs and metadata consistent?

- If you added or changed something user-facing, is the README or AGENTS.md updated?
- Are variable names, comments, and doc strings consistent with what shipped?

## Output

**If everything is done:** say "Done — nothing left." in one line.

**If something is incomplete:** list each item as a bullet with what's missing and why, then ask:

> Want me to continue and handle these now, or are you good?

Do not pad the response. One sentence per finding.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Olshansk](https://github.com/Olshansk)
- **Source:** [Olshansk/agent-skills](https://github.com/Olshansk/agent-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-olshansk-agent-skills-cmd-done-check
- Seller: https://agentstack.voostack.com/s/olshansk
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.