skills.rest
mrkhachaturov
mrkhachaturovCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Runs a verification flow before allowing work to be marked complete.

Updated Mar 26, 2026
Search Tags:#verification#completion#build#evidence#quality-assurance#tests
One-click install
npx skills add https://github.com/mrkhachaturov/rkstack --skill verification-before-completion-mrkhachaturov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/mrkhachaturov/rkstack/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/mrkhachaturov/rkstack --skill verification-before-completion-mrkhachaturov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The verification-before-completion skill prevents premature completion claims by enforcing a structured verification flow that requires fresh evidence before marking work as done.

Core Features & Use Cases

  • Enforces a repeatable verification process across tests, builds, and documentation to ensure claim validity.
  • Generates verifiable, per-item evidence outputs that can be attached to PRs or reports.
  • Useful for software teams, auditors, and CI/CD pipelines to guard against premature releases.

Quick Start

Run the full verification flow to confirm fresh evidence before marking work as complete.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce verification before marking code changes as complete?▼

To enforce verification before completion, run a structured flow that executes fresh tests, builds, and linting checks. This guarantees evidence-based completion by capturing verifiable proof before work is marked done.

What is evidence-based completion in software quality assurance?▼

Evidence-based completion requires generating fresh, per-item verification outputs like test suite results and build checks before claiming work is finished. It prevents premature completion claims by demanding verifiable proof attached to PRs or reports.

How do I generate verifiable evidence outputs for pull requests?▼

You can generate per-item evidence outputs by executing verification commands across tests, builds, and documentation reviews. These outputs can be attached directly to pull requests or audit reports to validate claim validity.

Does the verification flow adapt to projects of varying sizes and tech stacks?▼

Yes, the verification flow adapts to projects of varying sizes and tech stacks. It applies across code changes, tests, builds, and documentation reviews, supporting per-item verification commands tailored to your environment.

What's the best way to prevent premature completion claims in CI/CD pipelines?▼

The best way to prevent premature completion claims in CI/CD pipelines is enforcing a repeatable verification process that captures fresh evidence. Running full test suites, build checks, and linting guarantees work is validated before release.

Related Skills

Explore More Software Engineering Skills→
Dmccarty30Dmccarty30
4

using-git-worktrees

Create isolated Git worktrees with dependency installation and baseline tests.

Community
Intermediate
maluradityamaluraditya
1

verification-before-completion

Enforce command-driven verification with fresh outputs before completion claims.

Community
Advanced
miko06miko06

health

Compute code quality scores from type checkers, linters, tests, and dead code detectors.

Community
Intermediate
ZESCODEZESCODE

ZES-verification-before-completion

Validate task completion via multi-agent tests, linting, and requirement checks.

Community
Advanced