issue-status-sync

To post execution progress to GitHub Issues without closing them, trigger a status synchronization skill after role execution completes. It formats a progress comment using a standard template and leaves the GitHub Issue open for final management acceptance.

Synchronizing execution status to GitHub Issues for management review requires generating a DOC-003 compliant progress report. The process consumes upstream artifacts like acceptance decisions and posts a styled comment template enforcing evidence-driven reporting on the related GitHub Issue.

Yes, you can post a progress comment on a GitHub Issue while keeping it open for acceptance. This applies when a dispatch originates from a GitHub Issue and all roles have completed their work, ensuring traceable progress updates without altering the Issue state.

To generate a DOC-003 report and GitHub comment template from upstream artifacts, process acceptance decisions and verification results. This builds a traceable progress narrative and formats a standard GitHub comment for managerial review and controlled closure.

Automated workflows prematurely close GitHub Issues when lacking controlled closure enforcement. To prevent this, issue-status synchronization enforces issue-context validation and managerial acceptance, posting deterministic progress updates without altering the Issue state until final approval.

Yes, you need upstream acceptance decisions and verification results to build a traceable progress narrative on GitHub Issues. Consuming these upstream artifacts ensures evidence-driven reporting and generates a DOC-003 compliant progress report for management review.