--- name: close-work-cycle-e5e90c11c378 description: HAIOS Close Work Cycle for structured work item closure. Use when closing work items. Guides VALIDATE->ARCHIVE->MEMORY workflow with DoD enforcement. recipes: - close-work - update-status generated: 2025-12-25 last_updated: '2026-01-19T17:31:34' --- # Close Work Cycle This skill defines the VALIDATE-ARCHIVE-MEMORY cycle for closing work items with Definition of Done (DoD) enforcement per ADR-033. ## When to Use **Invoked automatically** by `/close` command after observation-capture-cycle. **Manual invocation:** `Skill(skill="close-work-cycle")` when closing an existing work item. --- ## The Cycle ``` [observation-capture-cycle] --> [dod-validation-cycle] --> VALIDATE --> ARCHIVE --> MEMORY --> CHAIN │ | │ [route next] reflection first | (RECALL->NOTICE->COMMIT) /-------------\ INV-* has plan? else | | | investigation implement work-creation -cycle -cycle -cycle ``` **Entry Gates (MUST):** 1. **Observation Capture (E2-278):** Before starting this cycle, **MUST** invoke observation-capture-cycle: ``` Skill(skill="observation-capture-cycle") ``` This forces genuine reflection in dedicated cognitive context before entering "closing mode." 2. **DoD Validation:** Before VALIDATE phase, **MUST** invoke dod-validation-cycle: ``` Skill(skill="dod-validation-cycle") ``` This validates DoD criteria in an isolated bridge skill. --- ### 1. VALIDATE Phase **On Entry:** ```bash just set-cycle close-work-cycle VALIDATE {work_id} ``` **Goal:** Verify work item meets Definition of Done criteria. **Guardrails (MUST follow):** 1. **Tests MUST pass** - Prompt user to confirm 2. **WHY MUST be captured** - Check for memory_refs in associated docs 3. **Docs MUST be current** - CLAUDE.md, READMEs updated 4. **Traced files MUST be complete** - Associated plans have status: complete **Actions:** 1. Read work file: `docs/work/active/{id}/WORK.md` (or `docs/work/active/WORK-{id}-*.md` for legacy) 2. Check work directory for plans: `docs/work/active/{id}/plans/` 3. Check plan statuses - all must be `complete` 4. For INV-* items: Apply investigation-specific DoD 5. Prompt user for DoD confirmation **Exit Criteria:** - [ ] Work file exists and has status: active - [ ] All associated plans have status: complete - [ ] User confirms: tests pass, WHY captured, docs current **Tools:** Read, Glob, Grep --- ### 2. ARCHIVE Phase **On Entry:** ```bash just set-cycle close-work-cycle ARCHIVE {work_id} ``` **Goal:** Update work item status to complete. **Note:** Per ADR-041 "status over location" - work items stay in `docs/work/active/` until epoch cleanup. The `status: complete` field determines state, not directory path. **Actions:** 1. Run atomic close-work recipe: ```bash just close-work {id} ``` This atomically performs: - Update `status: active` to `status: complete` - Update `closed: null` to `closed: {YYYY-MM-DD}` - Run cascade and update-status 2. Update any associated plans to `status: complete` (if not already) **Exit Criteria:** - [ ] `just close-work` succeeded - [ ] Work file has `status: complete` and `closed: {date}` - [ ] Associated plans marked complete **Tools:** Bash(just close-work) --- ### 3. MEMORY Phase **On Entry:** ```bash just set-cycle close-work-cycle MEMORY {work_id} ``` **Goal:** Store closure summary to memory and verify governance events. **Actions:** #### 3a. Governance Event Check (E2-108) 1. **Check for cycle events** (soft gate - warns but does not block): ```bash just events | grep "{id}" ``` - If no events found for the work ID, warn that governance may have been bypassed - Work item can still close, but warning surfaces potential governance bypass #### 3b. Memory Capture 2. Store closure summary via `ingester_ingest`: - Title, backlog_id, DoD status, associated documents - Include observation summary if any captured in observation-capture-cycle - Use source_path: `closure:{backlog_id}` #### 3c. Report Closure 3. Report closure to user with memory concept ID **Exit Criteria:** - [ ] Governance event check completed (warning if no events) - [ ] Closure summary stored to memory - [ ] User informed of successful closure with memory concept ID **Tools:** governance_events.check_work_item_events, ingester_ingest **Note:** Status refresh is handled by `just close-work` in ARCHIVE phase (includes cascade and update-status). --- ### 4. CHAIN Phase (Post-MEMORY) **On Entry:** ```bash just set-cycle close-work-cycle CHAIN {work_id} ``` **Goal:** Checkpoint context then route to next work item. #### 4a. Checkpoint (MUST - E2-287) **MUST** invoke checkpoint-cycle before routing to next work: ``` Skill(skill="checkpoint-cycle") ``` **Rationale:** Work complexity within hardened gating system makes context limits per work item likely. Checkpointing after closure ensures context from completed work is preserved before starting new work. Next session picks up with full context of decisions made. #### 4b. Route to Next Work **Actions:** 1. (Closure already completed in MEMORY phase) 2. (Checkpoint completed in 4a) 3. Query next work: `just ready` 4. If items returned, read first work file to check `documents.plans` 5. **Apply routing decision table** (see `routing-gate` skill): - If `next_work_id` is None → `await_operator` - If ID starts with `INV-` → `invoke_investigation` - If `has_plan` is True → `invoke_implementation` - Else → `invoke_work_creation` 6. Execute the action: - `invoke_investigation` -> `Skill(skill="investigation-cycle")` - `invoke_implementation` -> `Skill(skill="implementation-cycle")` - `invoke_work_creation` -> `Skill(skill="work-creation-cycle")` - `await_operator` -> Report "No unblocked work. Awaiting operator direction." **MUST:** Do not pause for acknowledgment - checkpoint then execute routing immediately. **Exit Criteria:** - [ ] **MUST:** checkpoint-cycle invoked (E2-287) - [ ] Next work item identified (or none available) - [ ] Appropriate cycle skill invoked (or awaiting operator) **On Complete:** ```bash just clear-cycle ``` **Tools:** Bash(just ready), Read, Skill(checkpoint-cycle, routing-gate) --- ## Composition Map | Phase | Primary Tool | Memory Integration | |-------|--------------|-------------------| | (Entry) observation-capture-cycle | Skill | Observation capture via RECALL->NOTICE->COMMIT | | VALIDATE | Read, Glob, Grep | Query for prior work (optional) | | ARCHIVE | Bash(just close-work) | - | | MEMORY | ingester_ingest | Closure summary | | CHAIN | Skill (checkpoint-cycle, routing) | Context preservation (E2-287) | --- ## Quick Reference | Phase | Question to Ask | If NO | |-------|-----------------|-------| | (Entry) | Observations captured? | Invoke observation-capture-cycle first | | VALIDATE | Does work file exist? | STOP - not found | | VALIDATE | Are all plans complete? | STOP or warn user | | VALIDATE | Does user confirm DoD? | STOP - DoD not met | | ARCHIVE | Is work file archived? | Run `just close-work` | | MEMORY | Is closure stored? | Store via ingester | | CHAIN | Is next work identified? | Run `just ready` | --- ## Key Design Decisions | Decision | Choice | Rationale | |----------|--------|-----------| | Three phases | VALIDATE -> ARCHIVE -> MEMORY | E2-278: OBSERVE extracted to observation-capture-cycle | | observation-capture-cycle as entry gate | Dedicated cognitive context | INV-059: Embedding causes completion mode bias | | Keep command lookup | Skill assumes work item found | Command handles "not found" case before skill | | Skill documents steps | Command + Skill redundancy | Command is authoritative; skill provides structure | | MEMORY phase after archive | After archive | Memory should reflect completed state | --- ## Related - **observation-capture-cycle skill:** Entry gate for genuine reflection (E2-278) - **observation-triage-cycle skill:** Processes captured observations - **work-creation-cycle skill:** Parallel workflow for creation - **implementation-cycle skill:** Parallel workflow for implementation - **investigation-cycle skill:** Parallel workflow for research - **ADR-033:** Work Item Lifecycle Governance - **/close command:** Invokes observation-capture-cycle then this skill --- Source attribution: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/close-work-cycle/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/close-work-cycle/SKILL.md Attribution basis: Source repository record Fields of work: Operations, Project & Program Management Roles: Business Process Analyst, Operations Manager, Project Manager Specialties: Specialty not specified Tools: Just Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 6d9900cb67044df4c8b0901546ae61630f9a7880a870943b0597b2246cbac488