manage-vault-improvements

Manages improvement backlog indexes and task files in a vault repository.

Updated May 18, 2026
One-click install
npx skills add https://github.com/dodonki1223/vault --skill manage-vault-improvements-dodonki1223
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-vault-improvements
Source: https://github.com/dodonki1223/vault/tree/main/.agents/skills/manage-vault-improvements
Command: npx skills add https://github.com/dodonki1223/vault --skill manage-vault-improvements-dodonki1223

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a vault-wide improvement backlog consistent is tedious: index entries drift from task files, completed tasks pile up, and duplicates accumulate. This Skill maintains the improvements/ directory so the backlog index and task files stay synchronized and clean. ## Core Features & Use Cases - Backlog and Task Management: Add new improvement ideas as kebab-case task files under improvements/tasks/ and register them in the improvements/backlog.md index with status, priority, and a one-line summary. - Update and Deduplication: Update existing tasks, adjust priority (高/中/低) and status (未着手/進行中/保留), and merge overlapping tasks instead of creating duplicates. - Completion Hygiene: Remove completed tasks from both the backlog and tasks directory, migrate durable decisions to README or reference docs, and verify no broken links remain. - Use Case: When you notice a recurring vault workflow problem, ask the assistant to register it as a new improvement task; it will check for duplicates, create the task file, and add a properly formatted index row. ## Quick Start Use the manage-vault-improvements skill to add a new improvement task about standardizing note templates to the backlog.

Frequently Asked Questions about manage-vault-improvements

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

FAQPage Schema
How do I add a new improvement task to the vault backlog?▼

Check backlog.md and existing task files for duplicates first, then create a kebab-case Markdown file under improvements/tasks/ and add one index row to backlog.md with status, priority, link, and a one-line summary. Default priority is 中 if unsure.

How do I mark an improvement task as completed?▼

Verify the completion criteria, migrate any durable decisions to README.md, .agents/README.md, or references, then delete the task file and its backlog row. Completed tasks are not archived; history lives in git log.

What statuses and priorities does the backlog support?▼

Statuses are limited to 未着手 (not started), 進行中 (in progress), and 保留 (on hold). Priorities are 高, 中, or 低. Completed tasks are removed from the backlog rather than kept with a done status.

Can this skill implement the improvements or update external services?▼

No. It only manages backlog hygiene. It does not implement improvements, create or heavily modify skills or scripts, write to Linear, Notion, Slack, or GitHub, or update the projects/ directory.

How do I check the backlog for consistency issues?▼

Verify that every backlog link points to an existing task file, no orphan task files exist besides tasks/README.md, status and priority notation is uniform, no completed tasks remain, and no personal or confidential information is present.