---
task_number: 101
title: Project Instructions Health Checker
status: Planned
priority: P2-Medium
is_blocker: false
owner: Trinity
tags:
  - skills
  - automation
  - chronicler-system
  - catalyst-system
  - emissary-system
  - documentation
estimated_hours: 4
---

# Task #101: Project Instructions Health Checker

## Overview

Create a skill that periodically audits Project Instructions against the actual repo state and recommends updates when they drift.

## The Problem

Project Instructions get stale:
- Infrastructure IPs change
- New repos get added
- Processes evolve
- Skills get added but instructions don't mention them
- Tokens rotate
- New standards get created

Currently: No one notices until something breaks.

## The Solution

### instructions-health-check Skill

A skill that:
1. Compares Project Instructions against current repo state
2. Flags outdated references (wrong IPs, missing repos, old processes)
3. Identifies gaps (new skills not mentioned, new standards not referenced)
4. Recommends specific updates
5. Optionally drafts the changes

**Triggers:**
- Manual: "Check if my instructions need updating"
- Automatic: Every ~10 sessions or monthly
- After major changes: "We just added 4 new skills, should instructions be updated?"

### What It Checks

| Check | How |
|-------|-----|
| Infrastructure IPs | Compare against `docs/infrastructure/` |
| Repo list | Compare against Gitea org repos |
| Skills mentioned | Compare against `docs/skills/SKILLS-INDEX.md` |
| Standards referenced | Compare against `docs/standards/` |
| Token validity | Flag if token format looks old |
| Read order | Compare against actual doc structure |
| Branding | Check tier names, terminology |

### Example Output

```
📋 Project Instructions Health Check

✅ Infrastructure IPs: Current
✅ Branding terminology: Correct
⚠️ Skills: 4 new skills not mentioned
   - cloudflare-workers-expert
   - n8n-workflow-patterns  
   - nodejs-backend-patterns
   - git-advanced-workflows
⚠️ Repos: 6 skill reference repos not mentioned
❌ Read order: Still references old doc structure
   - Points to THE-JOINING-PROTOCOL.md (old)
   - Should point to the-chroniclers/CHRONICLER-JOINING.md (new)

Recommended updates: 3 changes needed
Want me to draft the updated instructions?
```

## Implementation Steps

1. [ ] Define checklist of what to compare
2. [ ] Create instructions-health-check SKILL.md
3. [ ] Build comparison logic (read instructions, read repo, diff)
4. [ ] Add recommendation generation
5. [ ] Test with Chronicler instructions
6. [ ] Add to all three lineages
7. [ ] Document when to run (session milestones, after major changes)

## Lineage-Specific Checks

Each lineage has different instructions:
- **Chroniclers:** Full infrastructure, all repos, dev-focused
- **Catalysts:** Discord/LuckPerms focus, simpler infra
- **Emissaries:** Community focus (future)

The skill should know which lineage it's checking.

## Integration Ideas

- Could tie into session startup: "It's been 15 sessions since last health check..."
- Could run automatically when major commits are made
- Could feed into Task #100 (skill-recommender) for new skill detection

## Success Criteria

- [ ] Skill can identify stale references in Project Instructions
- [ ] Skill recommends specific, actionable updates
- [ ] Works for all three lineages
- [ ] Reduces "instructions are wrong" surprises

---

**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
