Automate post-change closure of issues and documentation across work streams.
npx skills add https://github.com/ajrmooreuk/pfi-w4m-dev --skill close-out
Please help me install this Agent Skill. Skill: close-out Source: https://github.com/ajrmooreuk/pfi-w4m-dev/tree/main/pfc-core/skills/close-out Command: npx skills add https://github.com/ajrmooreuk/pfi-w4m-dev --skill close-out
This Skill automates the closure of work items and documentation after a change cycle, ensuring statuses, docs, and communications stay in sync.
Invoke the close-out process after a change to automatically close related issues, update docs, and publish a bulletin.
High-intent search queries and answers about installing and using this skill.
Automating close-out after a release involves parsing arguments to discover the work hierarchy and executing stages to update issue statuses, architecture docs, and operating guides. This keeps statuses, docs, and communications in sync without manual effort.
Yes, you can close out feature-level and story-level work items together. The process applies to PR-based, story-level, feature-level, commit-based, and session-based entry points, updating related issues and documentation across all levels simultaneously.
The close-out process generates test plans and release bulletins automatically. It extracts deployment and configuration notes during the execution stages, ensuring that communications and release documentation are published alongside the updated issue statuses.
Yes, you can preview changes using the optional dry-run mode. This allows you to parse arguments, discover the work item hierarchy, and simulate the execution of all six closure stages without permanently modifying issue bodies or publishing documentation.
The best way to keep docs in sync is automating post-change closure. By discovering the epic hierarchy and executing the six-stage close-out process, architecture docs and operating guides are updated automatically to reflect the completed work items.
If an error occurs during issue closure, the process includes proper error handling to manage the failure. The six execution stages are designed to parse arguments and discover the hierarchy safely, preventing silent failures during documentation and status updates.
crewrigCompose pull request titles, bodies, logbook entries, and squash-merge commit messages.
monoPublish SkiaSharp packages to NuGet.org and finalize releases.
clover-stormDetect code changes from git diffs and update corresponding documentation sections.
voidrotGenerate project breakdown plans with Epic, Feature, Story/Enabler, and Test hierarchies.
