loop-executor

Execute tasks from plan.md sequentially, writing code and updating progress.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill loop-executor-geargrindadmin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-executor
Source: https://github.com/Geargrindadmin/gg-agentic-harness/tree/main/.agent/skills/loop-executor
Command: npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill loop-executor-geargrindadmin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the implementation of tasks defined in a verified plan, ensuring code is written, files are created, and progress is tracked accurately.

Core Features & Use Cases

  • Sequential Task Execution: Works through tasks in plan.md one by one.
  • Automated Code Writing: Implements tasks by writing necessary code and creating files.
  • Progress Tracking: Updates plan.md with completion status, commit SHAs, and summaries after each task.
  • TDD Integration: Follows Test-Driven Development principles for relevant tasks.
  • Use Case: After a plan for a new feature is evaluated and verified, this Skill will take over to build out the components, write tests, and commit the code according to the plan's specifications.

Quick Start

Use the loop-executor skill to implement the first uncompleted task in plan.md.

Frequently Asked Questions about loop-executor

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

FAQPage Schema
How do I automate task execution from a plan and write code sequentially?

Automate task execution by processing a verified plan sequentially, writing code, creating files, and updating the plan's completion status after each task finishes.

Does workflow automation for code generation integrate Test-Driven Development?

Workflow automation integrates Test-Driven Development by automatically following TDD principles specifically when implementing relevant business logic tasks defined in the plan.

How does automated plan implementation track progress and handle git commits?

Automated plan implementation tracks progress by updating the plan file with completion status, commit SHAs, and summaries, while committing changes automatically at defined checkpoints.

What happens during task execution when discovered work is found outside the original plan?

When task execution encounters discovered work outside the original plan, it flags these changes as requiring business document synchronization to maintain project alignment.

Do I need a specific file format to start automated code generation and plan implementation?

Automated code generation requires a verified plan file to start execution, working through tasks sequentially and updating the markdown file with completion summaries and commit SHAs.