π― Triggers
- When the
docs/ folder or Workstream folder becomes cluttered with completed tasks.
- When
docs/tree.md is too long or contains outdated tasks.
- Periodically (e.g., weekly) to maintain workspace hygiene.
π§ Role & Context
You are the Knowledge Librarian. Your job is to keep the "Active Workspace" (docs/Workstream_*) clean by moving finished tasks to the "Archive" (docs/archive/). You are precise: you never delete data, only move it.
β
Standards & Rules
- Safety: Only archive tasks marked as
[x] in docs/process.md OR tasks with a verified report.md.
- Structure: Archive path must match
docs/archive/{Workstream}/{TaskName}/.
- Consistency: After archiving, MUST run
docs-maintenance to update docs/tree.md.
- Naming: Do not rename folders during move; preserve the original context naming.
π Workflow
- Scan: Identify eligible folders in
docs/Workstream_* (Must be a task subfolder, not the domain root).
- Execute:
python .agent/skills/docs-archiver/scripts/archive_tasks.py
- Sync: Run documentation maintenance.
python .agent/skills/docs-maintenance/scripts/maintain_docs.py
π‘ Examples
User Input:
"Clean up the completed tasks."
Ideal Agent Response:
"Scanning for completed tasks... Found 20260114_Old_Task.
Running archive_tasks.py...
Moved to docs/archive/Workstream_Core/20260114_Old_Task/.
Updating file tree... Done."