close-work-cycle

Automate work item closure with Definition of Done validation and routing.

1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Rwb3n/haios --skill close-work-cycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: close-work-cycle
Source: https://github.com/Rwb3n/haios/tree/main/.claude/skills/close-work-cycle
Command: npx skills add https://github.com/Rwb3n/haios --skill close-work-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the structured closure of work items by enforcing Definition of Done (DoD) criteria.

Core Features & Use Cases

  • VALIDATE-ARCHIVE-MEMORY workflow for closing work items with DoD enforcement per ADR-033.
  • Entry gates, DoD validation, and automatic routing to the next work item based on availability and context.
  • Memory capture of closure summaries and governance event checks to ensure traceability.

Quick Start

Use the close-work-cycle skill to close an active work item after observation capture. Example: Skill(skill="close-work-cycle")

Frequently Asked Questions about close-work-cycle

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

FAQPage Schema
How do I enforce Definition of Done criteria before closing a work item?

Definition of Done enforcement for work item closure validates entry gates and captures governance events before archival. The process checks DoD criteria, stores closure summaries to memory, and routes to the next work item based on context availability.

What is the correct workflow for archiving work items with governance and memory capture?

Work item archival with governance uses a validate-archive-memory workflow. It validates DoD criteria, stores closure summaries to memory for traceability, and records governance event checks before routing to the next cycle automatically or manually.

Do I need observation-capture-cycle and dod-validation-cycle to automate work item closure?

Yes, work item closure requires integration with observation-capture-cycle and dod-validation-cycle. These dependencies provide observation capture and DoD validation needed before status updates and memory recording occur during the closing lifecycle.

Can I route work items to different cycles after validating Definition of Done?

Yes, after DoD validation, work items route to investigation, implementation, or work-creation cycles automatically. Routing depends on availability and context, handling both automatic and manual invocations for the next work item.

How does automatic routing work when closing work items with DoD enforcement?

Automatic routing during work item closure evaluates context and availability after DoD validation. It performs status updates via just close-work, then routes to investigation, implementation, or work-creation cycles as appropriate.

What happens if Definition of Done criteria are not met during work item closure?

Work item closure enforces DoD criteria through entry gates and validation checks. The process requires passing dod-validation-cycle before proceeding to archival, memory recording, and routing to subsequent work cycles.