Use when user wants to align docs with the current project status or new discoveries
Install via CLI
openskills install reidemeister94/development-skills---
name: align-docs
description: "Use when user wants to align docs with the current project status or new discoveries"
user-invocable: true
---
# Align Docs
Align all project documentation with actual disk state.
## Principles
- Maximize simplicity. Small improvement + ugly complexity = not worth it.
- All signal, zero noise. Deduplicate; link to single source of truth.
- Agent context files (`AGENTS.md` or `CLAUDE.md`) are cheat sheets. Tables, code snippets, direct statements. Maximize density.
## Execution Checklist
### Step 1: Inventory — diff docs against disk
| Check | How |
|-------|-----|
| **Project structure** (`AGENTS.md`/`CLAUDE.md`) | `ls` root → compare with structure tree |
| **Plugin versions** (`AGENTS.md`/`CLAUDE.md`, `MEMORY.md`) | Read each `plugins/*/.claude-plugin/plugin.json` |
| **Skills per plugin** (READMEs) | `ls plugins/*/skills/` → compare with skills table |
| **Agents per plugin** (READMEs) | `ls plugins/*/agents/` → compare with agents table |
| **Shared files** (READMEs) | `ls plugins/*/shared/` → verify architecture matches |
| **Conventions & paths** (`AGENTS.md`/`CLAUDE.md`) | Verify every path exists |
| **Cross-references** | Check doc links point to existing files |
### Step 2: Fix misalignments
| Document | Purpose | What to check |
|----------|---------|---------------|
| **`AGENTS.md`** (or `CLAUDE.md` if primary) | Project-wide, loaded every conversation | Structure, versions, paths, conventions |
| **`MEMORY.md`** | Cross-session memory | Versions, stable facts, iteration numbers |
| **Plugin READMEs** | Plugin-specific docs | Skills, agents, architecture, quick start |
| **`docs/chronicles/`** | Narrative records | Only if referencing incorrect content |
| **Other `docs/`** | Domain docs | Only if stale |
### Step 3: Remove noise
- Delete entries referencing nonexistent things
- Deduplicate: keep in one place, link from others
- Remove empty sections or placeholders
No comments yet. Be the first to comment!
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments