workflow-deprecate

Mark repository workflow files as deprecated with reason and optional successor.

Updated Aug 27, 2026

Search Tags:#workflow #audit #repository #yaml #deprecate #successor

Ready to run

npx skills add https://github.com/hollis-labs/volon --skill workflow-deprecate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-deprecate
Source: https://github.com/hollis-labs/volon/tree/main/plugins/workflow-author/skills/workflow-deprecate
Command: npx skills add https://github.com/hollis-labs/volon --skill workflow-deprecate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a safe, auditable way to retire workflows in a repository by updating their metadata and recording deprecation context without deleting historical files.

Core Features & Use Cases

Non-destructive deprecation: sets workflow status to deprecated and updates updated_at while retaining the original file for audit.
Successor linking: optionally validates and links a successor workflow by setting replaces in its frontmatter.
Use Case: When a team replaces an old process, mark the old workflow deprecated, record the reason, and link the new workflow for discoverability.

Quick Start

Mark the workflow my-workflow as deprecated in the user domain and include a brief reason and an optional successor name.

Frequently Asked Questions about workflow-deprecate

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

FAQPage Schema

How do I deprecate a workflow in a repository without deleting the file?▼

To deprecate a workflow non-destructively, set its frontmatter status to deprecated, update the updated_at timestamp, and append a Deprecation section to the file body while retaining the original file for auditing.

How do I link a successor workflow when retiring an old process?▼

Linking a successor workflow involves validating the successor's existence and setting the replaces field in its frontmatter, ensuring the new workflow is discoverable when the old one is deprecated.

What is the best way to audit workflow deprecation history in markdown files?▼

Workflow deprecation auditing relies on appending a Deprecation section with the retirement reason to the markdown file body and updating frontmatter fields like status and updated_at to maintain a recorded lifecycle history.

Can I use this workflow deprecation method for files outside the workflows directory?▼

This deprecation method applies specifically to repository-hosted workflow files located under workflows/<domain>/<name>.md, validating their existence and current status before applying lifecycle updates.

What frontmatter changes when marking a repository workflow as deprecated?▼

When marking a repository workflow as deprecated, the frontmatter status field changes to deprecated and the updated_at field refreshes, with an optional replaces field set on a verified successor workflow.

Why should I retain deprecated workflow files instead of removing them?▼

Retaining deprecated workflow files instead of removing them provides a safe, auditable historical record by preserving the original file content while clearly indicating its retired status and successor.