skill-align

# Lattice Sync **Core responsibility:** Keep every public-facing document in sync with the actual skill inventory. The skills directory is the source of truth — all documents derive from it. **Input:** None required. Reads the live state of `skills/` and all documentation on every run. Optionally: a specific skill name or tier to focus the audit. **Output:** - A findings report listing every gap as `[GAP]`, `[STALE]`, or `[WRONG]` with file and description - All found gaps fixed in-place across: `README.md`, `docs/how-it-works.md`, `docs/configuration.md`, `docs/practical-guide.md`, `CLAUDE.md`, `.github/ISSUE_TEMPLATE/bug_report.yml` - A final clean confirmation: "No gaps found" or a list of what was changed **How to verify this skill did its job:** ```bash grep -rn "requirements atom\|framework:requirements\b" \ docs/ README.md CLAUDE.md .github/ skills/ \ --include="*.md" --include="*.yml" ``` Any result from this grep means the sync is incomplete. A clean run returns no output. Also verify: every skill in `skills/` appears in the bug_report.yml dropdown and the how-it-works.md inventory tables. ## When to run - After creating any new atom, molecule, or refiner - After renaming or removing a skill - After changing a skill's config key, consumed-by relationships, or output path - When a user suspects docs are out of date ## Phase 1 — Build the live inventory Read the skills directory tree. Do NOT assume you already know the inventory — always read from files. ...