memory-maintenance

# Memory Maintenance Skill

**Purpose**: Provide Memory file structure guidance when Claude updates Memory files

**Invocation**: Claude autonomously uses this skill when updating Memory/*.md files

---

## When to Use This Skill

This skill provides guidance for:
- Creating new Memory files
- Updating existing Memory files
- Maintaining frontmatter schema
- Understanding file interdependencies
- Determining update triggers

## Memory File Structure

### Required Files

**Memory/activeContext.md**:
- Current project status
- Recent activities (last 2-3 sessions)
- Critical reference information
- Next steps
- Update: Every session

**Memory/projectbrief.md**:
- Project overview
- Scope (in/out)
- Objectives
- Constraints
- Update: Rarely (major scope changes)

**Memory/communicationStyle.md**:
- Persona
- Communication patterns
- Audience
- Voice examples
- Update: Occasionally (persona refinements)

### Optional Files

**Memory/workflowProtocols.md**:
- Project-specific patterns
- Tool usage conventions
- Process documentation
- Create when: Patterns emerge across multiple sessions

**Memory/techEnvironment.md**:
- Stack (languages, frameworks, tools)
- Code conventions (naming, imports, style)
- Build system
- Discovered patterns from codebase
- Create when: Software development projects

**Custom Files**:
- Create project-specific Memory files as needed
- Examples: agentCoverageTest.md, wireframeReference.md

## Frontmatter Schema

All Memory files MUST include:

```yaml
---
version: "X.Y"
lastUpdated: "YYYY-MM-DD HH:MM UTC"
lifecycle: "initiation|planning|execution|maintenance"
stakeholder: "technical|business|regulatory|all"
changeTrigger: "≥25% code impact|pattern discovery|user request|context ambiguity"
validatedBy: "human|ai|system"
dependencies: ["file1.md", "file2.md"]
---
```

**Field Requirements**:
- **version**: Increment minor (X.Y+1) for content, major (X+1.0) for structure
- **lastUpdated**: Update on every modification
- **lifecycle**: Current pro