workflow-complete

Finalize completed workflows by validating criteria and moving packet directories to done.

3|3|Updated Aug 19, 2024
One-click install
npx skills add https://github.com/AMDResearch/dh_comms --skill workflow-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-complete
Source: https://github.com/AMDResearch/dh_comms/tree/main/.agents/skills/workflow-complete
Command: npx skills add https://github.com/AMDResearch/dh_comms --skill workflow-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that all completion steps for a finished workflow are executed in concert, preventing scenarios where the packet directory is not moved, the run-log has no closing entry, or the handoff remains stale.

Core Features & Use Cases

  • Verify acceptance criteria in dossier.md and update its Lifecycle State to done.
  • Update run-log.md with a final closing entry and update handoff.md with final status.
  • Move the workflow packet directory from active to done and archive its entry in active-workflows.md.
  • Prune focus lists and verify state consistency across the workflow files.

Quick Start

Initiate workflow-complete when a workflow reaches done to finalize all artefacts and relocate the packet directory.

Frequently Asked Questions about workflow-complete

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

FAQPage Schema
How do I automate workflow completion and move the packet directory to done?

To automate workflow completion, validate that all acceptance criteria are met, then update the dossier lifecycle to done, close the run-log, finalize handoff, and move the packet directory to done/.

What happens to handoff and run-log files when a workflow reaches the done state?

When a workflow reaches the done state, the run-log receives a final closing entry and the handoff file is updated to reflect the final completion status.

How do I archive completed workflows and update active-workflows.md?

Archive completed workflows by moving the packet directory to done/ and removing or archiving the corresponding entry within the active-workflows.md file.

Why does my workflow state management leave stale handoff files or open run-logs?

Stale handoff files and open run-logs occur when completion steps are not executed in concert, requiring automated state transitions to finalize all artefacts simultaneously.

Can I verify state consistency across dossier, run-log, and handoff files during process orchestration?

Yes, state consistency across workflow files is verified by pruning focus lists and checking that dossier, run-log, and handoff reflect the final done state.

Do I need any external dependencies to finalize workflow state transitions and archive packets?

No external dependencies are required to finalize workflow state transitions, as the process orchestrates dossier updates, run-log closure, and packet archiving natively.