← ClaudeAtlas

aidex-referencelisted

Use when the user wants to document how an existing, settled part of the system works as an evergreen `.context/references/` module — architecture, configuration, an operational runbook, a how-it-works guide. Fires on "create a reference for X", "document how X works", "write up the X architecture", "document the X configuration", "write a runbook for X", "what is documented and what is missing". Not for: planning multi-step work (aidex-plan); recording a decision/ADR (aidex-decision); capturing a stakeholder request (aidex-request); investigating something not yet settled (aidex-research); deferring/parking an idea (aidex-backlog); ecosystem audits (aidex); project-state audits (aidex-audit).
yacb2/aidex · ★ 2 · AI & Automation · score 81
Install: claude install-skill yacb2/aidex
> **Trigger-eval probe (test-only).** As your very first action, run `printenv AIDEX_TRIGGER_EVAL_MARKER`. If it prints a non-empty path, also run `touch "${AIDEX_TRIGGER_EVAL_MARKER}.aidex-reference"` before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block. # Reference Document how a settled part of the system works, as an evergreen module in `.context/references/<topic>/`. **The failure this skill exists to prevent is not bad formatting.** It is a document that is confidently wrong — dead code written up as a feature, a screen described in a state nobody rendered, a `## Verification` block that cannot fail. Those are cheap to commit and expensive to find, so the steps below are mechanical rather than advice to be careful. Formatting canon lives in `aidex-conventions/references/reference-conventions.md` and is not forked here. **The discipline lives in this skill's `references/`.** ## Sub-actions | `$ARGUMENTS` | Does | |---|---| | *(none)* or a topic | Author or update a module — the full workflow below | | `census` | Run the coverage census only; report gap / phantom / contested | | `census --stale` | Also flag items whose SOURCE moved after their owning module did | | `profile` | Create or update `.context/references/00-profile.md` | | `refute <path>` | Run the adversarial close-gate on an existing module | --- ## 0 · Profile — once per project Read `.context/references/00-profile.md`. **If it does not exist, c