ai-closeout-reporter

Name: ai-closeout-reporter
Availability: InStock
Author: nguyenpv1980-wq

Generate terminal closeout reports with scope-reduction disclosure and validation evidence.

2|Updated Jul 6, 2026

Search Tags:#validation #audit #reporting #handoff #scope reduction #closeout

Ready to run

npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill ai-closeout-reporter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ai-closeout-reporter
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/ai-closeout-reporter
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill ai-closeout-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill helps produce a trustworthy end-of-task closeout that clearly states what changed, what was intentionally not done, what was validated, and what remains risky or unverified. It prevents silent scope reduction by forcing omissions into a dedicated section instead of hiding them in prose.

Core Features & Use Cases

Terminal task reporting: Create a final handoff after finishing implementation, review, or a PR.
Scope-reduction disclosure: Record anything skipped, partially delivered, or downgraded with explicit reasons.
Evidence-backed validation: List files touched, tests run, actual results, skipped checks, and next actions.
Use case: When a task is complete, use this Skill to generate a closeout report that lets another engineer or stakeholder verify the work without re-deriving it.

Quick Start

Use the ai-closeout-reporter skill to write a final closeout report for the completed task, including the mandatory omitted-items section and the actual validation results.

Frequently Asked Questions about ai-closeout-reporter

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

FAQPage Schema

How do I write a closeout report for a pull request that accurately tracks scope reduction?▼

A closeout report prevents silent scope reduction by forcing omissions into a dedicated section. You record exactly what changed, what was intentionally skipped, and the validation evidence, allowing stakeholders to verify the work without re-deriving it.

What should be included in an audit-ready handoff for completed engineering work?▼

An audit-ready handoff requires file attribution from git, command-level validation evidence, exact omission tracking, and a structured next-action handoff. This ensures another engineer can verify the completed implementation without ambiguity.

Why does task handoff documentation often fail to capture unverified risks?▼

Task handoff documentation often hides unverified risks in prose. A structured closeout report forces scope-reduction disclosure and skipped checks into a dedicated section, ensuring honest validation reporting and explicit risk tracking.

Can I use an automated closeout report for post-implementation summaries?▼

Yes, you can generate a post-implementation summary that documents actual validation results and files touched. This provides an audit-ready record of completed engineering work for review or compliance.

How do I document skipped checks and partial deliveries in a terminal task report?▼

You document skipped checks in a terminal task report by listing them in a mandatory omitted-items section. This explicitly captures partial deliveries, skipped checks, and downgraded items with their reasons for full auditability.

What is the best way to ensure honest validation reporting during a PR closure?▼

The best way to ensure honest validation reporting during a PR closure is to require command-level validation evidence and exact omission tracking. This prevents silent scope reduction and clearly states what remains unverified.