task-loop-verify

Verify the current task in a task-loop workflow and emit a completion marker.

20|2|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/jsegov/shipspec-claude-code-plugin --skill task-loop-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-loop-verify
Source: https://github.com/jsegov/shipspec-claude-code-plugin/tree/main/skills/task-loop-verify
Command: npx skills add https://github.com/jsegov/shipspec-claude-code-plugin --skill task-loop-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies the current task in the Ralph-style loop and outputs a completion marker to signal the stop hook, enabling clean session exit.

Core Features & Use Cases

  • Validates the active task loop state and task metadata, ensuring the loop progresses only after verification.
  • Emits a standardized completion marker (<task-loop-complete>VERIFIED</task-loop-complete>) to integrate with session control.
  • Intended for end-to-end task verification in iterative development cycles where tasks must pass acceptance criteria before moving on.

Quick Start

Run the verification step after implementing a task to signal loop completion when criteria pass.

Frequently Asked Questions about task-loop-verify

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

FAQPage Schema
How do I automate task verification in an iterative development loop?

Task verification in an iterative development loop is automated by reading the current loop state, loading the task prompt from TASKS.json, delegating to a verifier, and handling VERIFIED, INCOMPLETE, or BLOCKED outcomes to manage progression.

What completion marker is used to signal a successful task-loop verification?

A successful task-loop verification emits the standardized completion marker <task-loop-complete>VERIFIED</task-loop-complete> to integrate with session control and signal the stop hook for a clean session exit.

How does an automated task-loop handle incomplete or blocked verification outcomes?

Automated task-loops handle incomplete or blocked verification outcomes by evaluating the verifier response and preventing the loop from progressing until acceptance criteria are satisfied or the block is resolved.

When do I need to emit a loop-stopping marker during development automation?

A loop-stopping marker is needed during development automation after implementing a task, ensuring the loop exits cleanly only when the task passes all acceptance criteria and verification succeeds.

Do I need a TASKS.json file to verify tasks in a Ralph-style loop?

Yes, verifying tasks in a Ralph-style loop requires a TASKS.json file to provide the task prompt and metadata, ensuring the loop validates the active task state and progresses only after verification.