executing-plans-extras

What problem does it solve?

This Skill solves the common pain point of stalled project plan execution when steps include exact file content that fails environment-specific parse checks (such as ESM vs CommonJS module mismatches) or prescribe changing a value to hit a target metric without confirming the change will move the metric in the expected direction.

Core Features & Use Cases

• DONE_WITH_CONCERNS Protocol: For exact-content plan steps that fail parse checks due to environment mismatch (not plan authoring errors), commit the content as-is and generate a clear concern report with the error verbatim, root-cause diagnosis, and minimal one-line fix for the next task author, avoiding unauthorized content modification or silent skip of verification steps.
• Pre-Commit Lever Direction Probe: For steps that prescribe a value to achieve a target metric, run a low-cost diagnostic sweep of the value across a small grid to confirm the sign of the metric change matches the plan's assumption before committing a value, surfacing incorrect causal assumptions as findings instead of applying harmful adjustments that worsen the target metric.
• Use Case: If a plan step specifies cwd: __dirname in a Playwright config for an ESM project, the skill guides you to commit the content as-is and report the ESM-related parse failure with the correct __dirname polyfill fix, rather than modifying the plan content or skipping the check.

Quick Start

Use the executing-plans-extras skill when you encounter a plan step with exact file content that fails an environment-specific parse check or a step that prescribes changing a value to hit a target metric, to follow the appropriate protocol for handling the issue without modifying plan content or applying unvalidated changes.