fix-engine

Generate executable checklists from acceptance criteria and orchestrate retry loops.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/blueif16/amazing-claude-code-plugins --skill fix-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-engine
Source: https://github.com/blueif16/amazing-claude-code-plugins/tree/main/infistack/skills/fix-engine
Command: npx skills add https://github.com/blueif16/amazing-claude-code-plugins --skill fix-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

From acceptance criteria, generate an executable checklist and orchestrate an executor → validator loop with retry logic. It tracks attempts and accumulates failure context, escalating after max retries.

Core Features & Use Cases

  • Checklist generation: Automatically converts acceptance criteria into actionable checks.
  • Execution loop: Iterate between executor and validator, retrying on failures.
  • Failure history: Capture attempts, executor notes, and relevant code snippets for diagnostics.

Quick Start

Use this Skill to build a retry-enabled validation loop from your acceptance criteria.

Frequently Asked Questions about fix-engine

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

FAQPage Schema
How do I automate retries when validation fails during testing?

Automate retries by orchestrating an executor-validator loop that repeatedly attempts failing checks up to a maximum retry count. The Skill generates executable checklists from acceptance criteria and accumulates failure context across attempts, enabling diagnostic escalation after exhausting retries.

How do I convert acceptance criteria into automated checks?

Acceptance criteria are automatically converted into actionable executable checklists. The Skill transforms your criteria into validation checks that can be executed and monitored, forming the foundation for orchestrated retry loops.

What information does a retry loop capture when tests fail?

The Skill captures attempt history, executor notes, relevant code snippets, and detailed error context. This accumulated failure information is formatted into a comprehensive error report for escalation after maximum retries are exhausted.

Can I use this for multiple validation attempts with different code implementations?

Yes. The executor-validator loop applies to sub-coordinators during implementation or validation failures, enabling multiple distinct attempts while collecting code snippets and context from each iteration for diagnostics.

When should I use orchestrated retry logic instead of failing on first error?

Use orchestrated retries when you need to explore multiple implementation paths, gather diagnostic context, or give multiple chances to fix issues before escalation. Retry logic is most valuable for complex validation scenarios where failure context improves debugging.