vault-update

Update vault item statuses and move items to correct folders.

6|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/anotherben/claude-harness --skill vault-update-anotherben
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vault-update
Source: https://github.com/anotherben/claude-harness/tree/main/skills/vault-update
Command: npx skills add https://github.com/anotherben/claude-harness --skill vault-update-anotherben

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vault item statuses often drift and routing becomes inconsistent. vault-update ensures consistent governance by updating statuses and moving items to the correct folders according to the controller contract.

Core Features & Use Cases

  • Normalize statuses across the lifecycle (open, claimed, in-progress, blocked, done, wont-do) and map legacy values (active->in-progress, closed->done, completed->done).
  • Apply status transitions and trigger the appropriate vault-index coordination tool to keep state and location in sync.
  • Move items between folders (01-Bugs/02-Tasks/03-Ideas/00-Inbox for open items; 04-In-Progress/05-Archive as they progress) to reflect current status.
  • Use to enforce governance before enterprise-verify/enterprise-compound, and to align with the Obsidian-first controller contract.

Quick Start

Update a vault item's status by selecting the item and applying the appropriate transition (e.g., open -> in-progress, in-progress -> done) and then reindex.

Frequently Asked Questions about vault-update

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

FAQPage Schema
How do I automate vault item lifecycle updates to enforce governance and correct routing?▼

Automating vault item lifecycle updates requires applying structured status transitions like open, claimed, in-progress, blocked, done, or wont-do, followed by automatic refoldering and index refreshes to enforce governance and correct routing.

What is the best way to normalize legacy vault item statuses like active or closed?▼

Normalizing legacy vault item statuses involves mapping outdated values to the current lifecycle, such as converting active to in-progress, and closed or completed to done, ensuring consistent governance across the project management vault.

How do I move vault items between folders automatically when their status changes?▼

Moving vault items between folders automatically during status changes is handled by mapping progressions to specific paths, relocating open items to 00-Inbox or 01-Bugs, and progressing items to 04-In-Progress or 05-Archive as they advance.

Can I use vault status transitions to enforce governance before running enterprise verification?▼

Yes, you can use vault status transitions to enforce governance before running enterprise-verify or enterprise-compound, ensuring required fields are validated and coordination-tool calls are executed prior to index refresh and optional handoffs.

Why does vault item routing become inconsistent and how do I fix it?▼

Vault item routing becomes inconsistent when statuses drift across the lifecycle; fixing it requires enforcing required fields, normalizing legacy values, and triggering coordination-tool calls to keep state and folder location in sync.