execute-pending-workplan-claude

Pending workplan execution automates the full workflow by moving plans from Pending to Inprogress, executing steps via referenced skills, running tests, and finalizing to Done or continuation issues. It coordinates state transitions and updates GitHub issues throughout the process.

Moving pending workplans to Inprogress follows a six-step workflow: list pending plans, transition state, execute steps via referenced skills, run tests and logical checks, then move to Done or create continuation issues. GitHub issues track progress throughout the orchestration.

Workplan execution resolves each implementation step's required skill, follows that skill's workflow to apply it, runs tests and logical checks for correctness, and updates in-repo progress artifacts. This ensures each step completes successfully before moving forward.

When tests fail during workplan execution, the workflow validates outcomes through tests and logical checks before finalizing. If steps cannot complete, the plan generates continuation work by creating a continuation issue rather than moving the plan directly to Done.

Yes, automated workplan execution updates in-repo progress artifacts and GitHub issues as it orchestrates implementation steps. It tracks state transitions from Pending through Inprogress to Done, ensuring full progress visibility throughout the workflow lifecycle.