Close Loop

Verify task artifacts against acceptance criteria and run quality checks.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/beekeeper-lab/repomirrorkit --skill close-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Close Loop
Source: https://github.com/beekeeper-lab/repomirrorkit/tree/main/.claude/skills/close-loop
Command: npx skills add https://github.com/beekeeper-lab/repomirrorkit --skill close-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that completed tasks meet their original requirements, maintaining the quality and reliability of autonomous workflows by verifying outputs against acceptance criteria.

Core Features & Use Cases

  • Automated Verification: Checks produced artifacts against task specifications and quality bars.
  • Quality Enforcement: Runs automated checks like linting and tests.
  • Feedback Loop: Provides actionable feedback for failed tasks or notifies downstream consumers upon success.
  • Use Case: After a developer implements a new API endpoint, this skill verifies the code meets the spec, passes tests, and is ready for integration, automatically notifying the next team in the pipeline.

Quick Start

Use the close-loop skill to verify task 'TASK-007-implement-api' using the provided specification and artifacts.

Frequently Asked Questions about Close Loop

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

FAQPage Schema
How do I verify task completion against acceptance criteria?

Verify task completion by comparing produced artifacts against original acceptance criteria and running automated quality checks. This ensures outputs meet specifications before marking tasks complete, maintaining autonomous workflow reliability.

How does automated verification work for autonomous team workflows?

Automated verification works by comparing produced artifacts against task specifications and running quality checks like linting and tests. It manages the feedback loop between requesting and producing personas by marking tasks complete or returning them with specific failure reasons.

What is the best way to enforce quality contracts for completed tasks?

Enforce quality contracts by running automated checks like linting and tests against produced artifacts. This verifies outputs meet specifications and automatically notifies downstream consumers upon success or provides actionable feedback for failed tasks.

Can I use artifact validation to provide feedback for failed tasks?

Yes, artifact validation provides actionable feedback for failed tasks by comparing outputs against acceptance criteria. When tasks fail verification, they are returned with specific failure reasons to guide the producing persona in correcting the work.

Do I need to provide specifications to run quality checks on artifacts?

Yes, you need to provide task specifications and artifacts to run quality checks. The verification process compares produced artifacts against the provided specification to ensure the output meets the original requirements and quality bar.

When should I not use automated task verification in my pipeline?

You should not use automated task verification when tasks lack clear acceptance criteria or when artifacts cannot be validated through automated checks like linting and tests, as the process relies on comparing outputs against defined specifications.