close-out

Automate post-change closure of issues and documentation across work streams.

Updated Feb 17, 2026

Search Tags:#issue-management #architecture-docs #test-plan #release-pipeline #close-out #operating-guides

Ready to run

npx skills add https://github.com/ajrmooreuk/pfi-w4m-dev --skill close-out

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the closure of work items and documentation after a change cycle, ensuring statuses, docs, and communications stay in sync.

Core Features & Use Cases

Closes out PR-based, story-level, feature-level, commit-based, and session-based work streams.
Updates issue bodies (stories, features, epics) and related documentation across architecture docs and operating guides.
Generates test plans and release/bulletins, with deployment and configuration notes.

Quick Start

Invoke the close-out process after a change to automatically close related issues, update docs, and publish a bulletin.

Frequently Asked Questions about close-out

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate closing out issues and updating documentation after a release?▼

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.

Can I close out feature-level and story-level work items together in one process?▼

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.

How does the close-out process handle test plans and release bulletins?▼

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.

Can I preview changes to issues and docs before finalizing the close-out?▼

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.

What is the best way to keep architecture docs and operating guides in sync with completed epics?▼

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.

What happens if the close-out process encounters an error during issue closure?▼

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.