project-memory-tracking

What this skill does

# Project Memory Tracking Skill

Use this skill to maintain persistent memory of project state, services built, features implemented, and decisions made. This gives agents context about what's been done without re-analyzing the entire codebase.

## When to Use
- **Before starting work** - Load project context
- **After implementing features** - Save what was built
- **After QA testing** - Save test results and screenshots
- **After fixing issues** - Track what was fixed
- **When switching services** - Save/load context
- **During planning** - Reference existing work

## Why This Is Critical

### Without Memory:
- ❌ Agents don't know what's already built
- ❌ Repeat analysis of same code
- ❌ Lose context between sessions
- ❌ Forget decisions made
- ❌ Re-discover same issues
- ❌ Can't reference previous work

### With Memory:
- ✅ Agents know project state
- ✅ Reference existing services
- ✅ Maintain context across sessions
- ✅ Remember decisions and rationale
- ✅ Track issue history
- ✅ Build on previous work

## What This Skill Tracks

### 1. Services Inventory
```yaml
services:
  auth:
    type: microservice
    api:
      project: auth/auth-api
      port: 8001
      docker_ip: 172.18.0.2
      database: stylemate_auth
      health_endpoint: /health
      endpoints:
        - POST /api/auth/login
        - POST /api/auth/register
        - POST /api/auth/refresh
        - GET /api/auth/profile
      jwt_config:
        issuer: stylemate-auth
        audience: stylemate-services
        claims: [sub, email, role, business_id, email_confirmed]
    ui:
      project: auth/auth-ui
      port: 3001
      docker_ip: 172.18.0.3
      routes:
        - /login
        - /register
        - /profile
      federation_remote: auth_ui
    status: production
    last_modified: 2025-01-15T14:30:00Z
    created_by: dotnet-engineer-agent
    qa_status: verified_complete
    qa_date: 2025-01-15T16:00:00Z

  scheduling:
    type: microservice
    api:
      project: scheduling/scheduling-api
      port: 8003
      docker_ip: 172.18.0.4
      database: stylemate_scheduling
      endpoints:
        - GET /api/scheduling/schedules
        - POST /api/scheduling/schedules
        - PUT /api/scheduling/schedules/{id}
        - DELETE /api/scheduling/schedules/{id}
    ui:
      project: scheduling/scheduling-ui
      port: 3003
      docker_ip: 172.18.0.5
      routes:
        - /schedules
        - /schedules/create
        - /schedules/edit/{id}
    status: production
    last_modified: 2025-01-15T17:45:00Z
    features:
      - Schedule CRUD
      - Calendar view
      - Date filtering
    qa_cycles: 2
    screenshots_captured: 70
```

### 2. Features Implemented
```yaml
features:
  schedule_management:
    service: scheduling
    type: crud
    description: Staff can create, edit, delete schedules
    components:
      - ScheduleCalendar.tsx
      - ScheduleForm.tsx
      - ScheduleList.tsx
    api_endpoints:
      - POST /api/scheduling/schedules
      - GET /api/scheduling/schedules
      - PUT /api/scheduling/schedules/{id}
      - DELETE /api/scheduling/schedules/{id}
    implemented_by: ui-engineer-agent
    implementation_date: 2025-01-15T14:30:00Z
    qa_by: qa-frontend-engineer
    qa_status: verified_complete
    qa_cycles: 2
    issues_found: 5
    issues_fixed: 5
    screenshots: [list of 70 screenshot files]
    responsive_breakpoints_tested: [375, 414, 768, 1024, 1280, 1920]
```

### 3. Database Schemas
```yaml
databases:
  stylemate_scheduling:
    service: scheduling
    tables:
      schedules:
        columns:
          - id: UUID (PK)
          - business_id: UUID (FK, indexed)
          - employee_id: UUID (FK)
          - date: Date
          - start_time: Time
          - end_time: Time
          - is_active: Boolean
          - created_at: Timestamp
          - updated_at: Timestamp
        indexes:
          - business_id
          - employee_id
          - date
        migrations:
          - 20250115_CreateSchedules.cs
```

### 4. QA Test Results
```yaml
qa_results:
  schedule_calendar_page:
    feature: Schedule Calendar Page
    date: 2025-01-15T17:45:00Z
    qa_agent: qa-frontend-engineer
    cycles: 2

    cycle_1:
      date: 2025-01-15T15:00:00Z
      pass_rate: 75%
      passed: 15
      failed: 5
      critical_issues: 2
      screenshots: 35
      issues:
        - Horizontal scroll on mobile 375px (CRITICAL)
        - Touch targets 32px, need 44px (CRITICAL)
        - Tablet layout broken
        - Console error: undefined property
        - Loading state not visible
      status: REJECTED

    cycle_2:
      date: 2025-01-15T17:45:00Z
      pass_rate: 100%
      passed: 20
      failed: 0
      critical_issues: 0
      screenshots: 35
      status: APPROVED

    final_status: VERIFIED_COMPLETE
    total_screenshots: 70
    screenshot_files: [list of files]
```

### 5. Architectural Decisions
```yaml
decisions:
  decision_001:
    date: 2025-01-15T10:00:00Z
    title: Use Clean Architecture in single project
    context: Need to organize .NET microservices
    decision: Implement Clean Architecture within single project (not separate assemblies)
    rationale: Simpler for small microservices, easier to maintain
    alternatives_considered:
      - Separate projects for each layer (too complex for small services)
      - No architecture (too messy)
    decided_by: work-planner-agent
    status: active

  decision_002:
    date: 2025-01-15T11:30:00Z
    title: Mobile-first responsive design
    context: UI must work on mobile and desktop
    decision: Design for mobile first (375px), then enhance for desktop
    rationale: Most staff use phones in salon
    decided_by: software-engineer-agent
    status: active
```

### 6. Issues Tracked
```yaml
issues:
  issue_001:
    feature: Schedule Calendar
    date_found: 2025-01-15T15:00:00Z
    found_by: qa-frontend-engineer
    severity: CRITICAL
    description: Horizontal scroll on mobile 375px
    cause: Fixed width container (1200px)
    fix: Removed fixed widths, used max-width 100%
    fixed_by: ui-engineer-agent
    date_fixed: 2025-01-15T16:30:00Z
    verified_by: verification-agent
    date_verified: 2025-01-15T17:45:00Z
    status: RESOLVED

  issue_002:
    feature: Schedule Calendar
    date_found: 2025-01-15T15:00:00Z
    found_by: qa-frontend-engineer
    severity: CRITICAL
    description: Touch targets only 32px (need 44px)
    fix: Increased button size to 48px
    status: RESOLVED
```

### 7. Docker Network Configuration
```yaml
docker:
  network:
    name: stylemate_net
    subnet: 172.18.0.0/16
    driver: bridge

  containers:
    auth_ui:
      image: auth-ui:latest
      ip: 172.18.0.3
      ports: ["3001:80"]
      status: running
      health_check: /remoteEntry.js

    auth_api:
      image: auth-api:latest
      ip: 172.18.0.2
      ports: ["8001:80"]
      status: running
      health_check: /health

    scheduling_ui:
      image: scheduling-ui:latest
      ip: 172.18.0.5
      ports: ["3003:80"]
      status: running
      health_check: /remoteEntry.js
```

## Memory Operations

### Load Project State
```bash
# Get all context at start of session
memory_load_all()
```

Returns complete project state:
- All services
- All features
- Recent QA results
- Open issues
- Architectural decisions
- Docker configuration

### Save Service Built
```bash
memory_save_service(
  name: "scheduling",
  type: "microservice",
  api: { ... },
  ui: { ... },
  features: [ ... ]
)
```

### Save Feature Implemented
```bash
memory_save_feature(
  name: "schedule_management",
  service: "scheduling",
  components: [ ... ],
  endpoints: [ ... ],
  implemented_by: "ui-engineer-agent"
)
```

### Save QA Results
```bash
memory_save_qa_result(
  feature: "schedule_calendar_page",
  cycle: 1,
  pass_rate: 75,
  issues: [ ... ],
  screenshots: [ ... ]
)
```

### Save Architectural Decision
```bash
memory_save_decision(
  title: "Use mobile-first design",
  decision: "Design for mobile first..