execution

Execute approved PLAN.md tasks with TDD and deterministic commits.

Updated Jan 18, 2026

Search Tags:#automation #TDD #github #execution #plan #code #tests

Ready to run

npx skills add https://github.com/rom-orlovich/agents-system --skill execution-rom-orlovich

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execution
Source: https://github.com/rom-orlovich/agents-system/tree/main/claude-code-cli-poc/executor-agent/.claude/skills/execution
Command: npx skills add https://github.com/rom-orlovich/agents-system --skill execution-rom-orlovich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements code according to an approved PLAN.md, following a TDD-driven workflow to execute tasks such as feature work or bug fixes.

Core Features & Use Cases

TDD-driven execution: Write tests first and implement code changes in small, reviewable commits.
PLAN-based automation: Interpret PLAN.md to drive implementation steps, dependencies, and task traceability.
Auditable workflow: Leverage PLAN.md, task.json, and commit history for reproducibility and accountability.

Quick Start

Use the executor agent to apply PLAN.md instructions to the repository, creating commits that reflect each task.

Frequently Asked Questions about execution

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

FAQPage Schema

How do I automate TDD code execution from an approved plan?▼

Automating TDD code execution from an approved plan requires an Execution Agent to interpret PLAN.md, write tests first, and implement code changes in small deterministic commits. The agent reads task.json for context and dependency traceability.

What is the best way to enforce tests-first development during automated feature implementation?▼

Enforcing tests-first development during automated feature implementation is achieved by following a PLAN.md-driven workflow that mandates writing tests before code and committing changes in small, reviewable increments.

Can I use a plan-based workflow for both bug fixes and feature implementation?▼

Yes, a plan-based workflow supports both bug fixes and feature implementation. The Execution Agent applies TDD and deterministic commits to execute any task defined in the approved PLAN.md file.

How does an execution agent maintain auditable commit history?▼

An execution agent maintains auditable commit history by strictly adhering to PLAN.md instructions and task.json dependencies, generating small deterministic commits that map directly to each implemented task.

Do I need a PLAN.md file to start automated code execution?▼

Yes, a PLAN.md file is required to start automated code execution. The workflow depends on an approved plan to drive implementation steps, enforce TDD, and ensure deterministic commits.

What are the limitations of deterministic commit workflows for software projects?▼

Deterministic commit workflows for software projects are limited by strict adherence to PLAN.md. Deviations from the approved plan or missing task.json context can disrupt the automated TDD execution and commit traceability.