plan-executor

Execute architectural plans into atomic, testable code changes with verification.

39|6|Updated Nov 7, 2025

Search Tags:#automation #testing #implementation #software-engineering #plan-execution #code-changes #plan-tracking

Ready to run

npx skills add https://github.com/ddobrin/gemini-plan-commands --skill plan-executor-ddobrin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-executor
Source: https://github.com/ddobrin/gemini-plan-commands/tree/main/skills/plan-executor
Command: npx skills add https://github.com/ddobrin/gemini-plan-commands --skill plan-executor-ddobrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to convert a finalized architectural plan into implemented software changes with verifiable progress, ensuring fidelity to the plan and reducing drift.

Core Features & Use Cases

Plan-driven implementation: Convert each plan step into atomic, testable changes.
Iterative verification: Run tests and linting after each change to ensure compliance.
Progress tracking: Update the plan with status after each step.

Quick Start

Implement the given plan exactly as specified, committing small, verifiable changes and validating each step with tests.

Frequently Asked Questions about plan-executor

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

FAQPage Schema

How do I execute an architectural plan with strict adherence and verifiable code changes?▼

Plan execution converts finalized architectural steps into atomic, testable code changes. It enforces strict adherence by running iterative verification like tests and linting after each modification, ensuring plan fidelity and reducing drift.

What is the best way to track progress when implementing software changes step by step?▼

Progress tracking during step-by-step implementation involves updating the architectural plan with status logs after each atomic code change. This transparent tracking method validates every step against test-driven criteria before moving forward.

How does test-driven validation work during plan-driven code implementation?▼

Test-driven validation during plan-driven implementation works by running tests and linting after each small, verifiable code change. This iterative verification ensures strict compliance with the predefined architectural plan before proceeding.

Why does my software implementation drift from the original architectural plan?▼

Software implementation drifts from an architectural plan when changes are not atomic or verifiable. Converting each finalized plan step into small, testable changes with iterative verification prevents this drift and ensures strict adherence to requirements.

Can I use plan execution for software projects requiring deployments and automated testing?▼

Yes, plan execution applies to software projects requiring step-by-step implementation, automated testing, and deployments. It turns finalized architectural plans into verifiable code changes while validating each step to meet strict plan fidelity requirements.