execute-pending-workplan

To automate executing pending workplans, this skill orchestrates the entire workflow by selecting plans from the Pending directory, executing steps sequentially, validating results with tests, and moving completed plans to the Done directory while updating GitHub issues.

The best way to orchestrate workflow planning and testing is using a skill that coordinates cross-skill step execution, validates outcomes with logical-response checks, and automatically generates continuation issues for partial successes to ensure continuity.

Workplan validation handles partial success by running tests after step execution, creating a progress report, and generating a GitHub continuation issue for any incomplete steps rather than marking the entire plan as done.

Yes, you can ignore specific pending workplans during automated execution because the orchestration applies predefined ignore rules for items labeled AIIGNORE or FUTUREWORK before selecting the next plan to process.

No, you do not need external dependencies to run the next plan automatically, as the skill operates without external dependencies by managing the workplan lifecycle internally across Pending, Inprogress, and Done directories.

When a workplan completes successfully, the GitHub issue is automatically updated to reflect the finished state after all implementation steps execute and test validation confirms the results.