workspace-hygiene

name	workspace-hygiene
description	Use when the founder asks for daily or weekly workspace checklists, cleanup review, scheduled task review, file hygiene, frontmatter checks, stale workspace areas, or help understanding and fixing issues raised by the daily cleanup or weekly audit.
user-invocable	true

Workspace Hygiene — Daily And Weekly Checklists

Purpose

Keep Founders OS inspectable and trustworthy.

This skill does not replace the morning briefing, weekly audit, or core operating workflows. It gives the founder a simple way to check that the scheduled/background maintenance is running and that the workspace remains clean.

Required Paths

Read:

• data/setup-status.md
• data/connectors.md
• data/tasks.md
• data/ops.log
• views/daily-cleanup.md
• views/daily-checklist.md
• views/weekly-checklist.md
• views/slack-digest.md
• views/teams-digest.md
• recent files in data/research/, data/prep/, data/closeouts/, data/outbound/, and exports/

Write:

• views/daily-checklist.md for daily checks
• views/weekly-checklist.md for weekly checks
• append one line to data/ops.log

Tool Requirements

• No external tools are required.
• If Slack/Teams digests are configured but missing or stale, flag the issue and recommend the relevant digest workflow.
• Do not delete files or rewrite business records without approval.

Daily Checklist

The daily checklist should check:

• scheduled task / agent status: morning briefing, daily cleanup, weekly audit
• whether the morning briefing ran or is ready to run manually
• whether the daily cleanup view exists and has unresolved flags
• whether Slack/Teams digests are current when configured
• open tasks and due-soon follow-ups
• unfiled or suspicious files in workspace areas
• recent data/ops.log entries
• generated views that are stale or missing
• obvious frontmatter or placeholder issues in recent business records

Write:

• views/daily-checklist.md
• append one line to data/ops.log

Weekly Checklist

The weekly checklist should check:

• whether weekly audit ran
• whether views/health-check.md and views/audit-summary.md have unresolved issues
• whether research, prep, closeout, outbound, and artifact files are filed in the right locations
• whether required frontmatter is present where expected
• whether stale areas need cleanup
• whether setup, connector readiness, and agent activation status are current
• whether collaboration channel maps and digests are configured for Slack/Teams when used
• whether the weekly plan exists and reflects current priorities

Write:

• views/weekly-checklist.md
• append one line to data/ops.log

Founder Guidance

If a checklist or audit flags something the founder does not understand:

1. Explain the issue in plain English.
2. Say whether it is cosmetic, operational, or blocking.
3. Recommend the smallest safe fix.
4. Ask before mutating business records.
5. If the user says to fix it, make the safe cleanup and show FILES UPDATED.

Boundaries

• Do not silently delete files.
• Do not rewrite business records without approval.
• Do not invent missing context.
• Do not create full hidden memory, index rebuilds, or advanced scoring.
• Keep the checklist readable; it is for operating discipline, not a giant audit report.