Skip to content
Back to skills

Execution Discipline Verification Before Completion

ASecurity

Fresh-command proof for every completion claim; 'it should work' is a confession.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsbashgit

Works with

  • terminal
  • cli

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aniruddhaadak80/skills --skill execution-discipline-verification-before-completion --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Execution Discipline Verification Before Completion?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Execution Discipline Verification Before Completion
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/aniruddhaadak80-execution-discipline-verification-before-completio/badge)](https://www.skillsdirectory.com/skills/aniruddhaadak80-execution-discipline-verification-before-completio)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: execution-discipline-verification-before-completion
description: "Fresh-command proof for every completion claim; 'it should work' is a confession."
---
# Verify before claiming done β€” evidence over claims

> Fresh-command proof for every completion claim; 'it should work' is a confession.

**Track:** πŸ”„ Agentic Methodology Β· **Domain:** Execution Discipline Β· **Level:** foundation Β· **~20 min**

**Who this is for:** Agent Power Users, AI-Native Engineers, Teams Shipping With Agents, Solo Builders

## When to Use This Skill

Fresh-command proof for every completion claim; 'it should work' is a confession.
Use it whenever a matching task appears in conversation β€” the agent loads these instructions on demand.

## Steps

1. Run the actual verification command fresh at claim time, not from memory
2. Paste real output into the completion report β€” truncated honestly if long
3. Re-test edge cases named in the original task, not just the happy path
4. Distinguish 'compiles', 'tests pass', and 'works' as three separate proofs
5. If anything remains unverified, say exactly what and why β€” never gloss
6. Treat any 'should' in your own status report as an unfinished task marker

## Common Pitfalls

- Agents declaring success on stale terminal output
- Confident summaries laundering unverified assumptions

## Commands

**Install with skills CLI**
```bash
npx skills add aniruddhaadak80/skills --skill execution-discipline-verification-before-completion
```

**Install globally**
```bash
npx skills add aniruddhaadak80/skills --skill execution-discipline-verification-before-completion -g
```

---

Part of [aniruddhaadak80/skills](https://github.com/aniruddhaadak80/skills) Β· Browse all at https://skills.sh/aniruddhaadak80/skills

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…