cancel-sprint

Detect and terminate active Harness sprint loops by deleting .harness/sprint-loop.md.

8|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/zxdxjtu/harness --skill cancel-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel-sprint
Source: https://github.com/zxdxjtu/harness/tree/main/skills/cancel-sprint
Command: npx skills add https://github.com/zxdxjtu/harness --skill cancel-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancels an active sprint loop by removing the sprint-loop indicator file and logging the cancellation, helping teams halt automated sprint workflows safely.

Core Features & Use Cases

  • Detect an active sprint loop by checking for the .harness/sprint-loop.md file.
  • Cancel the sprint by deleting the sprint-loop.md and appending the cancellation to .harness/progress.md.
  • Report the cancellation status, including iteration and wave when available.

Quick Start

Cancel the current sprint loop by running the cancel-sprint skill.

Frequently Asked Questions about cancel-sprint

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

FAQPage Schema
How do I safely cancel an active sprint loop in Harness?

To cancel an active sprint loop, remove the .harness/sprint-loop.md flag file and append a cancellation log entry to .harness/progress.md to halt progress safely.

What happens to progress logs when I terminate a sprint loop?

When you terminate a sprint loop, the cancellation is appended directly to the .harness/progress.md file, preserving the iteration and wave status for auditability.

How does the sprint cancellation process detect an active automation loop?

The sprint cancellation process detects an active automation loop by checking for the existence of the .harness/sprint-loop.md indicator file before attempting safe deletion.

Can I halt automated sprint workflows without losing the current iteration status?

Yes, you can halt automated sprint workflows without losing status because the process reports the final cancellation status, including the specific iteration and wave details.

Do I need any dependencies to remove a sprint loop flag file?

No dependencies are required to remove a sprint loop flag file, as the process operates directly on the local .harness directory structure using basic file existence checks.

When should I avoid using an automated script to cancel a sprint?

You should avoid using an automated script if the .harness/sprint-loop.md file does not exist, as there is no active sprint loop to safely delete or log.