# Documentation Update: Skills Reference

**Date:** 2026-02-10
**Purpose:** Add references to installed Aphoria skills in dogfooding documentation

---

## What Was Added

### Context

User has 8 Aphoria skills installed in `~/.claude/skills/`:
- `aphoria/` - Main scan skill
- `aphoria-claims/` - Diff analysis, claim authoring
- `aphoria-suggest/` - Pattern suggestion from observations
- `aphoria-custom-extractor-creator/` - Generate extractors for patterns
- `aphoria-corpus-import/` - Bulk import from wikis/RFCs
- `aphoria-install/` - Installation and setup
- `aphoria-post-commit-hook/` - Autonomous post-commit integration
- `aphoria-ci-setup/` - CI/CD pipeline integration

Documentation should reference these skills as the primary workflow.

---

## Files Updated

### 1. CHECKLIST.md - Pre-Execution Skills Verification

**Location:** Lines 103-140

**Added:**
- List of all 8 skills with verification command
- Expected output showing skill directories
- Skill purposes with emoji markers (⭐ for primary Day 1 skills)
- Autonomous workflow section (post-commit hook, CI/CD)
- Updated skill count: "2 skills" → "8 skills total"

**Before:**
```markdown
Type: /aphoria
Autocomplete should show:
  /aphoria-claims     # Diff analysis, claim authoring
  /aphoria-suggest    # Pattern suggestion from observations
```

**After:**
```markdown
ls -la ~/.claude/skills/ | grep aphoria

Expected skills (8 total):
  aphoria/                         # Main Aphoria scan skill
  aphoria-claims/                  # ⭐ Diff analysis, claim authoring
  aphoria-suggest/                 # ⭐ Pattern suggestion from observations
  aphoria-custom-extractor-creator/ # Generate extractors for patterns
  aphoria-corpus-import/           # Import corpus from external sources
  aphoria-install/                 # Installation and setup
  aphoria-post-commit-hook/        # Autonomous post-commit integration
  aphoria-ci-setup/                # CI/CD pipeline integration
```

---

### 2. CHECKLIST.md - Day 1 Step 4 Skills Table

**Location:** Lines 322-345

**Added:**
- Skills reference table with "Use When" and "Purpose" columns
- Shows 4 skills relevant to Day 1 claim creation:
  - `/aphoria-claims` - Analyzing diffs, authoring claims
  - `/aphoria-suggest` - Growing coverage, finding gaps
  - `/aphoria-corpus-import` - Importing external corpuses
  - `/aphoria-custom-extractor-creator` - Day 3-4 (if needed)

**Impact:**
- Clarifies which skill to use at which stage
- Shows skills are organized by workflow phase
- Makes it easy to find the right tool for the job

---

### 3. STATE-2026-02-10.md - Skills Documentation

**Location:** Lines 59-63

**Added:**
- Complete list of 8 skills with purposes
- Organized by workflow:
  - Primary (claims, suggest, custom-extractor-creator)
  - Import (corpus-import)
  - Automation (post-commit-hook, ci-setup)
  - Setup (install, main aphoria)

**Before:**
```markdown
- Cross-project corpus verification
```

**After:**
```markdown
- References all 8 skills installed in `~/.claude/skills/aphoria*`:
  - `/aphoria-claims` - Diff analysis, claim authoring
  - `/aphoria-suggest` - Pattern suggestion from observations
  - `/aphoria-custom-extractor-creator` - Generate extractors
  - `/aphoria-corpus-import` - Bulk import from wikis/RFCs
  - `/aphoria-post-commit-hook` - Autonomous commit-time integration
  - `/aphoria-ci-setup` - CI/CD pipeline setup
  - `/aphoria-install` - Installation and setup
  - `/aphoria` - Main scan skill
- Cross-project corpus verification
```

---

### 4. docs/multi-project-setup.md - Skills for Pattern Reuse

**Location:** Lines 72-84

**Added:**
- Skills reference table for Project 2+ workflow
- Shows which skill to use when for cross-project knowledge compounding
- Clarifies purpose of each skill in flywheel context

**Table added:**
```markdown
| Skill | When to Use | Purpose for Project 2+ |
|-------|-------------|------------------------|
| `/aphoria-suggest` | Before Day 1 claim creation | Discover reusable patterns from Project 1 |
| `/aphoria-claims` | Day 1 claim authoring | Enforce naming consistency with Project 1 |
| `/aphoria-corpus-import` | Importing shared standards | Reuse vendor corpus across projects |
| `/aphoria-custom-extractor-creator` | Day 3-4 if gaps exist | Generate extractors aligned with Project 1 patterns |
```

---

### 5. docs/multi-project-setup.md - Production Automation

**Location:** Lines 247-270 (NEW SECTION)

**Added:**
- "Production Automation (Beyond Dogfooding)" section
- Explains post-commit hooks vs CI/CD integration
- Shows how to use `/aphoria-post-commit-hook` and `/aphoria-ci-setup`
- Clarifies when to use each (local dev vs team workflow)

**Purpose:**
- Bridges dogfooding to production use
- Shows autonomous operation setup
- Demonstrates full flywheel in practice

**Content:**
```markdown
### Option 1: Post-Commit Hooks (Local Development)
/aphoria-post-commit-hook
"Set up automatic scanning on every commit for this project"

### Option 2: CI/CD Integration (Team/Enterprise)
/aphoria-ci-setup
"Configure GitHub Actions to run Aphoria on every PR"
```

---

## Summary of Changes

| File | Lines Changed | What Added |
|------|---------------|------------|
| CHECKLIST.md | ~50 lines | Skills verification (8 skills), workflow table |
| STATE-2026-02-10.md | ~10 lines | Complete skills list with purposes |
| multi-project-setup.md | ~30 lines | Skills table, production automation section |

**Total:** 3 files, ~90 lines added/modified

---

## Impact

### Before
- Documentation mentioned 2 skills generically
- No clear guidance on which skill to use when
- No reference to automation skills (post-commit, CI)
- Skills felt like "optional enhancement"

### After
- All 8 skills documented with specific purposes
- Clear workflow tables showing when to use each
- Production automation path explained
- Skills positioned as primary workflow (manual CLI as fallback)

---

## Verification

Users can now:
1. ✅ See all installed skills at a glance
2. ✅ Know which skill to use at which workflow stage
3. ✅ Understand automation options (local hooks vs CI/CD)
4. ✅ Find skill names quickly for invocation

**Example user flow:**
```
User: "I need to create claims from a diff"
→ Reads CHECKLIST Step 4 table
→ Sees: /aphoria-claims - "Analyzing diffs, authoring claims"
→ Invokes: /aphoria-claims "analyze this diff and suggest claims"
```

---

## Related Documentation

- `.claude/skills/aphoria-claims/SKILL.md` - Claim authoring skill
- `.claude/skills/aphoria-suggest/SKILL.md` - Pattern suggestion skill
- `.claude/skills/aphoria-post-commit-hook/SKILL.md` - Post-commit automation
- `.claude/skills/aphoria-ci-setup/SKILL.md` - CI/CD integration

---

**Status:** ✅ Complete
**Next:** Users can reference installed skills when following dogfooding guides