dx-step-fix

To fix a blocked plan step, diagnose the root cause of build errors or test failures from error context and apply a direct remediation. If a direct fix is not feasible, generate corrective steps in implement.md with verification commands.

Diagnosing compilation errors involves analyzing error context from build outputs and review feedback to determine the remediation path. This process applies direct fixes to the step machinery or creates corrective steps to heal the blocked implementation.

Handling review feedback that blocks a plan step requires analyzing the feedback context to determine a remediation path. You can apply a direct fix and re-verify, or create corrective steps in implement.md with a clear verification command and status.

Yes, you can re-verify a plan step after applying a direct fix. The diagnostic workflow analyzes error context, applies a feasible remediation, and re-verifies the step to ensure the compilation errors or test failures are resolved.

When a direct fix for a blocked step is not feasible, create corrective steps in implement.md to heal the plan. These corrective steps include a clear verification command and status to ensure the compilation errors or test failures are properly resolved.

Automated debugging works directly with steps described in implement.md. It analyzes error context, root causes, and available conventions to determine a remediation path for blocked steps caused by build errors, test failures, or review feedback.