implementation-harness-pre-loop-checkin

Check build harness backlog status before unattended loop runs.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/RyanMKrol/LocalJobs --skill implementation-harness-pre-loop-checkin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementation-harness-pre-loop-checkin
Source: https://github.com/RyanMKrol/LocalJobs/tree/main/.claude/skills/implementation-harness-pre-loop-checkin
Command: npx skills add https://github.com/RyanMKrol/LocalJobs --skill implementation-harness-pre-loop-checkin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

This Skill ensures that the autonomous build harness is ready for unattended runs by checking for any blockers, session hygiene issues, dependency short-circuits, and task definition quality before initiating a loop.

Core Features & Use Cases

  • Read-only Check: Ensures no changes are made to the harness backlog, files, or owner overlays.
  • Runnable Work Assessment: Identifies tasks that can be built on the next pass and needs-human blockers.
  • Session Hygiene: Checks for uncommitted work, running loop processes, and repo locks.
  • Dependency Short-circuits: Flags tasks that depend on already completed tasks.
  • Task Definition Quality: Validates the presence and correctness of facets, spec files, and scope definitions.
  • Use Case: Before starting an unattended build loop, use this Skill to verify that all conditions are met for a smooth run.

Quick Start

Run the pre-loop check-in Skill by providing an optional task ID to focus on, e.g., /pre-loop-checkin T042.

Frequently Asked Questions about implementation-harness-pre-loop-checkin

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

FAQPage Schema
How do I validate build environment readiness before an unattended loop run?

This Skill checks build environment readiness by validating task dependency resolution, identifying runnable work, and flagging tasks that depend on already completed items before the loop starts.

What is a pre-loop check for build harness backlog and when do I need it?

You need this check before starting any unattended build loop to verify session hygiene, task definition quality, and dependency resolution without modifying files or overlays.

How do I check for uncommitted work and repo locks before starting a build loop?

The session hygiene check verifies no uncommitted work, running loop processes, or repo locks exist, ensuring a clean state for the automated build environment.

Do I need jq installed to perform harness validation checks?

The Skill depends on jq to process JSON data for validating facets, spec files, and scope definitions within the build harness backlog.

Can I use this pre-loop check to validate task definition quality for specific tasks?

This allows you to confirm the presence and correctness of scope definitions and spec files for individual tasks before they enter the build loop.

What are the limitations of using a read-only check for build automation readiness?

It only flags dependency short-circuits and needs-human blockers, requiring manual intervention to resolve any identified issues before the build loop can safely run.