Pending: Vault maintenance frequency (daily / weekly)?
Pending: Hook approach — validate-feature-format as PreToolUse or separate script?
User Tasks
Summary
Opus regularly cleans, organizes, and maintains both the vault and the codebase.
Problem / Motivation
Over time the vault accumulates stale notes, misplaced files, and inconsistent formatting. The codebase grows without consistent quality checks. Without scheduled maintenance, entropy wins.
Proposed Solution
Scheduled maintenance routines that run on a regular basis (daily/weekly) to audit and improve the system. Vault maintenance can start before VPS (run locally). Code maintenance depends on having actual code and tests.
Open Questions
No open questions.
Phase Overview
Phase
Description
Status
Phase 1
Vault maintenance
—
Phase 2
Codebase maintenance
—
Phase 3
Scheduled execution
—
Phase 1: Vault Maintenance —
Goal: Ensure vault files follow templates, are in correct folders, and have consistent formatting.
File / Feature
Details
Owner
Status
Template compliance check
All feature requests follow the template
opus
—
File placement audit
Flag files in wrong folders
opus
—
Naming/frontmatter check
Report inconsistencies
opus
—
Archive completed features
Move features older than X days to done/
opus
—
Vault health report
Generate summary of vault state
opus
—
validate-feature-format hook
PreToolUse: validates naming, frontmatter on save
opus
—
auto-format hook
PostToolUse: auto-fix formatting issues
opus
—
Phase 2: Codebase Maintenance —
Goal: Automated code quality checks and test coverage.
File / Feature
Details
Owner
Status
Lint all code
Python, shell scripts, configs
opus
—
Full test suite
Run tests and report failures
mv
—
Dead code check
Unused files, stale imports
opus
—
Test coverage
Verify all features have tests
mv
—
Coverage report
Test coverage percentage
mv
—
Phase 3: Scheduled Execution —
Goal: Automate maintenance on a regular schedule with results visible in briefings.