Validate terminal task state and capture outcome reviews for delivery closure.
npx skills add https://github.com/MajesteitBart/delano --skill closeout-skill
Please help me install this Agent Skill. Skill: closeout-skill Source: https://github.com/MajesteitBart/delano/tree/main/.agents/skills/closeout-skill Command: npx skills add https://github.com/MajesteitBart/delano --skill closeout-skill
This Skill helps finish a delivery by confirming that required work is complete, evidence is captured, and the project is ready for closure without leaving status or handoff gaps.
Use the closeout-skill to validate a finished project, capture the outcome review, and produce the closure update with any learning proposals.
High-intent search queries and answers about installing and using this skill.
To validate project completion, you check terminal task states and verify evidence completeness to ensure a clean delivery handoff. The process reviews contract status checks and event logs to confirm all required work is resolved and quality gates have passed before closing.
A closeout process for project delivery is the final validation step that confirms terminal task states, captures outcome reviews, and updates registry state. It ensures work is fully documented and ready for release closure without leaving status or handoff gaps.
You record completion summaries by validating terminal task states and capturing outcome reviews to append closure records. This updates contract or registry state and ensures the final delivery status and evidence are cleanly documented for handoff.
Yes, closure validation works for release workflows by applying contract status checks and validation hooks to ensure documented completion. It verifies terminal states and captures outcome reviews to produce clean closure records for projects requiring documented handoffs.
Yes, you can draft review-first learning proposals during project closeout when the validation process reveals reusable improvements. These proposals target adjustments to rules, schemas, or fixtures and are prepared for review alongside the final closure update.
If contract status checks or event log review fail during delivery closure, the validation hooks prevent the closeout from completing. This ensures terminal task states remain unresolved until evidence completeness is verified and quality gates pass.
jarredkennyRequire fresh verification evidence before marking tasks complete.
d-o-hubComplete learning episodes by scoring outcomes, extracting patterns, and updating heuristics.
ma08Persist task status files and reconcile session metadata across machines.
LerianStudioAutomate development completion validation with acceptance criteria checks and explicit user approval.
