When to Trigger

Memory cleanup belongs at session start — before work begins, when the context is clean and nothing is in-flight. Never during active work or compaction (you might delete something that's still needed).

Good triggers (session start):

/create-stories Step 0 (cleanup phase, before any tickets)
/workspace-launch Step 0 (before fetching ticket)
/infra-ticket Step 0 (before fetching ticket)
When the user explicitly says "clean up", "housekeeping", or "check memory"

Bad triggers (never here):

During /compact — context is under pressure, memories may still be relevant
Mid-implementation — you might delete something you need
During code review — you need the full context

The bash script runs first (0 tokens). Only invoke the skill if warnings are found AND the user says yes.

What to Check

1. MEMORY.md Index Size

When to Trigger

Good triggers (session start):

/create-stories Step 0 (cleanup phase, before any tickets)
/workspace-launch Step 0 (before fetching ticket)
/infra-ticket Step 0 (before fetching ticket)
When the user explicitly says "clean up", "housekeeping", or "check memory"

Bad triggers (never here):

During /compact — context is under pressure, memories may still be relevant
Mid-implementation — you might delete something you need
During code review — you need the full context

The bash script runs first (0 tokens). Only invoke the skill if warnings are found AND the user says yes.

Component	Budget	Why
MEMORY.md	< 1,500 tokens	Loaded every single prompt
Individual memories	< 500 tokens each	Loaded on access
Total memory dir	< 15,000 tokens	Full read during cleanup

Memory Hygiene

When to Trigger

What to Check

1. MEMORY.md Index Size

Memory Hygiene

When to Trigger

What to Check

1. MEMORY.md Index Size

2. Stale Memory Files

3. dream-team-learnings.md Size

4. Token Budget Check

Output Format

What NOT to Do

Promotion Path

Things Mac

Trello

Production Scheduling

Jira Integration

Production Scheduling

Cost Aware Llm Pipeline