dev-loop

Generate a development harness and run headless tasks with guarded commits.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/XIYBHK/claude-skills --skill dev-loop-xiybhk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-loop
Source: https://github.com/XIYBHK/claude-skills/tree/main/dev-loop
Command: npx skills add https://github.com/XIYBHK/claude-skills --skill dev-loop-xiybhk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The dev-loop skill eliminates the heavy overhead of manually wiring and running repeatable development loops across projects, ensuring consistent harness setup and progress tracking.

Core Features & Use Cases

  • Provides an Init phase that auto-generates a complete harness (CLAUDE.md, architecture.md, .devloop/task.json, config.json, and helper scripts) for a new project.
  • Drives a Run phase that headlessly executes tasks with strict verification, two-stage prompting, and guarded commits to ensure auditability.
  • Supports a reusable, script-driven workflow with gates and persistent state so teams can scale the harness across multiple projects.

Quick Start

Start a project with /dev-loop init to generate the harness, then run /dev-loop run to begin headless task execution.

Frequently Asked Questions about dev-loop

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

FAQPage Schema
How do I set up an automated development loop for my project?

To set up an automated development loop, generate a complete harness with configuration and helper scripts using an init phase, then execute headless tasks through a run phase with automated verification and guarded commits.

What is a headless development loop and how does it work?

A headless development loop drives task execution automatically through a script-driven harness, using strict gating, two-stage prompting, and persistent state to ensure reliability and auditability without manual intervention.

Can I use PowerShell to drive automated workflow verification and commits?

Yes, you can use PowerShell within a script-driven workflow to enforce strict gating, execute automated verification, and manage guarded commits for reliable, auditable task progression.

What's the best way to scale repeatable development workflows across multiple projects?

The best way to scale repeatable workflows is using a reusable, script-driven harness with persistent state and structured artifacts, ensuring consistent setup and automated progress tracking across projects.

Do I need to manually wire task verification for each automated workflow?

No, you do not need to manually wire task verification; the automated harness generates structured artifacts and helper scripts that enforce strict gating and automated verification during execution.

Why does my automated task execution require strict gating and persistent state?

Automated task execution requires strict gating and persistent state to ensure reliability and auditability, preventing unverified changes from being committed and maintaining progress tracking across the workflow.