hf-finalize

Close out tasks and workflow cycles with state sync and evidence.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hujianbest/garage-agent --skill hf-finalize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf-finalize
Source: https://github.com/hujianbest/garage-agent/tree/main/packs/coding/skills/hf-finalize
Command: npx skills add https://github.com/hujianbest/garage-agent --skill hf-finalize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the safe closure of tasks and entire workflow cycles once completion gates are satisfied, ensuring state consistency and ready handoff.

Core Features & Use Cases

  • Structured closeout process for task-closeout vs workflow-closeout scenarios.
  • Evidence-driven readiness checks using completion, regression, and review records to validate closure.
  • Handoff and archival support with a comprehensive closeout pack that records state, next actions, and synchronized assets.

Quick Start

Trigger a closeout for the current task or workflow when gate conditions are met and document the results in features/<active>/closeout.md.

Frequently Asked Questions about hf-finalize

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

FAQPage Schema
What is task closeout and how does it differ from workflow closeout?

Task closeout finalizes a single finished task, while workflow closeout reconciles remaining tasks and entire cycles. Both apply strict prechecks and update state, but workflow closeout also synchronizes long-term assets and release notes.

How do I finalize a task and generate a closeout pack with evidence?

To finalize a task, trigger a closeout once completion gates are met. The process runs evidence-driven readiness checks using completion, regression, and review records, then writes a closeout pack to features/<active>/closeout.md.

What prechecks are required before closing out a workflow cycle?

Workflow closeout requires evidence-driven readiness checks using completion, regression, and review records to validate closure. These strict prechecks ensure state consistency and verify completion gates before finalizing.

Can I update release notes and synchronize long-term assets during task closure?

Yes, workflow closeout updates release notes and synchronizes long-term assets during finalization. The generated closeout pack records state synchronization, evidence, and Next Action or null according to policy.

What is the best way to document task closure results for team handoff?

The best way to document task closure is generating a comprehensive closeout pack recording state, next actions, and synchronized assets. This ensures ready handoff and archival support by writing results to features/<active>/closeout.md.

When should I not use an automated closeout process for finished tasks?

You should not use automated closeout when completion gates are unmet or evidence is missing. The strict prechecks require valid completion, regression, and review records to validate closure and ensure state consistency.