BeClaude

verified-done

New
1GitHub TrendingGeneralby jpoindexter

Always-on skill pack that stops AI coding agents from claiming work is done when only the code path (not the real behavior) was verified. Portable SKILL.md for Claude Code, Codex, Cursor, and any agent.

Summary

This skill ensures that AI coding agents do not mark tasks as complete until the actual behavior has been verified, not just the code path.

  • It prevents premature sign-offs by enforcing real-world testing and validation before declaring work done.

Install & Usage

1
Create the agents directory
mkdir -p .claude/agents
2
Save the agent file

Add the configuration to .claude/agents/verified-done.md

3
Invoke with @agent-name
@verified-done

Use Cases

Prevent an agent from claiming a bug fix is complete when only the code compiles but the fix doesn't actually resolve the issue.
Ensure that after refactoring, the agent runs the full test suite and confirms all tests pass before marking the task done.
Stop an agent from closing a feature implementation ticket until end-to-end behavior is verified in a staging environment.
Require the agent to demonstrate the changed behavior with a live example or screenshot before accepting completion.
Force the agent to verify that a deployed hotfix actually resolves the production incident, not just that the code was pushed.
Prevent an agent from marking a code review as complete when only linting passed but logic errors remain.

Usage Examples

1

/verified-done Fix the login button not redirecting after authentication

2

Refactor the payment module and run all integration tests. Only mark done if all tests pass and the checkout flow works end-to-end.

3

/verified-done Update the API rate limiter and verify with a load test that requests are correctly throttled.

View source on GitHub
agent

Security Audits

LicenseUnknownSourceWarnRepositoryPass

Frequently Asked Questions

What is verified-done?

This skill ensures that AI coding agents do not mark tasks as complete until the actual behavior has been verified, not just the code path. It prevents premature sign-offs by enforcing real-world testing and validation before declaring work done.

How to install verified-done?

To install verified-done: create the agents directory (mkdir -p .claude/agents), then add the config to .claude/agents/verified-done.md. Finally, @verified-done in Claude Code.

What is verified-done best for?

verified-done is a agent categorized under General. It is designed for: agent. Created by jpoindexter.

What can I use verified-done for?

verified-done is useful for: Prevent an agent from claiming a bug fix is complete when only the code compiles but the fix doesn't actually resolve the issue.; Ensure that after refactoring, the agent runs the full test suite and confirms all tests pass before marking the task done.; Stop an agent from closing a feature implementation ticket until end-to-end behavior is verified in a staging environment.; Require the agent to demonstrate the changed behavior with a live example or screenshot before accepting completion.; Force the agent to verify that a deployed hotfix actually resolves the production incident, not just that the code was pushed.; Prevent an agent from marking a code review as complete when only linting passed but logic errors remain..