Task Loop Verification & Completion FAQs

Question 1

When does this skill output a VERIFIED status?

Accepted Answer

It outputs VERIFIED when the verification process confirms that all requirements and acceptance criteria defined in the feature's TASKS.json have been successfully implemented.

Question 2

What happens if a task is marked as INCOMPLETE?

Accepted Answer

The skill cleans up the active state files, logs the failure reason, and informs the user which specific criteria were not met so they can provide manual fixes.

Question 3

Where does the skill get the task requirements from?

Accepted Answer

Requirements and prompts are read dynamically from the .shipspec/planning/ directory based on the active feature and task ID stored in the loop state.

Question 4

What is the purpose of the task-loop-verify skill?

Accepted Answer

It automates the process of checking if a specific development task is complete based on acceptance criteria and signals Claude to end the session using specific completion markers.

Question 5

How does the stop hook interact with this skill?

Accepted Answer

The skill outputs XML-style markers like <task-loop-complete> which the session's stop hook monitors to decide whether to allow a clean exit or trigger another iteration.

Task Loop Verification & Completion

Key Features

Use Cases

Task Loop Verification & Completion

Key Features

Use Cases