verify

Generates fresh evidence to verify task completion claims before declaring them done.

1|Updated Apr 18, 2026

Search Tags:#verification #evidence #verify #claims #tests

Ready to run

npx skills add https://github.com/mopeyjellyfish/flywheel --skill verify-mopeyjellyfish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/mopeyjellyfish/flywheel/tree/main/skills/verify
Command: npx skills add https://github.com/mopeyjellyfish/flywheel --skill verify-mopeyjellyfish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verify completion claims with fresh evidence before declaring tests, lint, builds, or requirements as done.

Core Features & Use Cases

Enforces a gate on task completion by generating and validating evidence against the claimed result.
Produces auditable bundles that can be attached to tasks, PRs, or records for later review.
Supports multi-step workflows where evidence must be refreshed after changes.

Quick Start

Generate fresh evidence for the current claim and attach it to the task context.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I verify completion claims for tests, lint, and builds before declaring a task done?▼

Evidence verification works by generating fresh evidence and validating it against the claimed result before marking a task complete. It enforces a gate on task completion by requiring live checks and producing auditable traces for tasks and PRs.

What is the best way to attach auditable evidence bundles to pull requests?▼

Task verification requires generating fresh evidence and validating it against the claimed result. It enforces a completion gate by running live checks and producing auditable evidence bundles stored under .context/flywheel/evidence/ for tasks and PRs.

How do I enforce a verification gate on task completion in a multi-step workflow?▼

Yes, evidence verification supports multi-step workflows by allowing evidence to be refreshed after changes. It generates fresh evidence and validates it against claimed results, ensuring auditable traces are maintained across tasks and PRs.

When do I need to generate fresh evidence for requirement completion?▼

Evidence verification is needed before declaring tests, lint, builds, or requirements complete. It generates fresh evidence to substantiate claims with live checks and artifacts, producing auditable bundles stored under .context/flywheel/evidence/ for later review.