Description

The memory.agent.md exists in .github/agents/ but is undocumented in .github/CUSTOM-AGENTS.md. This agent provides repository memory persistence capabilities but contributors cannot discover its purpose or usage through the central reference.

Acceptance Criteria

• Review .github/agents/memory.agent.md to understand purpose and constraints
• Determine appropriate category (likely "Utility Agents" - new category or "Documentation and Planning")
• Add table entry with agent name, purpose, and key constraint
• Add details section following existing pattern (Creates, Workflow, Critical)

Proposed Solution

1. Review agent file first

Read .github/agents/memory.agent.md to extract:

• Primary purpose
• Output artifacts
• Key constraints
• Workflow steps

2. Add to appropriate category table

If creating new Utility Agents category:

### Utility Agents

| Agent | Purpose | Key Constraint |
| ----- | ------- | -------------- |
| **memory** | Persists repository facts for future tasks | Store only actionable, durable facts |

Or add to existing "Documentation and Planning Agents" category.

3. Add Agent Details section

Follow pattern:

### memory

**Creates:** Repository fact files:

* `/memories/repo/<descriptive-name>.jsonl`

**Workflow:** Identify actionable fact → Validate criteria → Store with citations → Available for future tasks

**Critical:** [Extract from agent file]

Files to Modify

Research Required

• Read .github/agents/memory.agent.md to understand full functionality
• Determine if new "Utility Agents" category is warranted

Time Estimate

45 minutes