fixme-execute-plan

Execute implementation plans with per-step verification and gated commits.

Updated Feb 18, 2026

Search Tags:#verification #workflow-automation #code-review #bug-fix #plan-execution #build-and-test #software-pipeline

Ready to run

npx skills add https://github.com/denis-pingin/fixme --skill fixme-execute-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fixme-execute-plan
Source: https://github.com/denis-pingin/fixme/tree/main/.claude/skills/fixme-execute-plan
Command: npx skills add https://github.com/denis-pingin/fixme --skill fixme-execute-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill executes an implementation plan step by step with strict verification, ensuring work is not considered complete until the full verification suite passes.

Core Features & Use Cases

End-to-end plan execution: loads the plan, reviews locked decisions, and executes tasks with per-step verification and required commits.
Baseline and sacred final verification: runs the full verification suite before declaring success; surfaces plan concerns if issues are found.
Safe, auditable workflow: commits are created at defined points and only buildable states are left in the repository.

Quick Start

Provide the path to a plan file and let the fixme-execute-plan skill run the plan from review to final verification.

Frequently Asked Questions about fixme-execute-plan

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

FAQPage Schema

How do I automate execution of an implementation plan with build and test verification?▼

Plan execution requires a plan file as input to define steps, checks, and final validation gates. The workflow reviews locked decisions, executes tasks with per-step verification, and runs the full verification suite before declaring success.

Why should I use automated plan execution for software maintenance and bug fixes?▼

Automated plan execution for software maintenance prevents incomplete work by enforcing gated commits and per-step verification. It guarantees only buildable repository states remain and surfaces plan concerns if final validation fails.

How do I ensure gated commits happen only after passing checks during a bug fix?▼

To ensure gated commits happen after passing checks, the plan execution workflow commits at defined points and enforces per-step verification. It requires a fully green verification suite across builds, tests, and linters before declaring success.

What happens if the final verification suite fails during plan execution?▼

When the final verification suite fails during plan execution, the workflow surfaces plan concerns and prevents the task from being declared complete. It ensures issues are found before the final validation gate is passed.

Do I need a specific plan file format to run automated workflow verification?▼

Automated workflow verification requires a plan file as input to define the steps, checks, and final validation gates. The plan file drives the end-to-end execution and dictates where gated commits occur.