Loading...
Loading...
Found 18 Skills
Audit project documentation against the codebase and fix drift. Run before PRs or after major changes. Compares documented architecture, test counts, and file paths against actual state.
v2.5.0 — Use when bootstrapping, completing, updating, or auditing project documentation, or documenting a feature/module/epic: AGENTS.md + docs/, ADRs, roadmap, docs/features/<slug>/, docs/plans/<slug>/. Triggers: "document this project", "bootstrap docs", "sync docs", "audit docs", "docs vs code", "from zero", "new feature", "nueva feature", "promové el plan", "after ark-check", "arkgate bridge", "knowledge dashboard", /documentation-manager. Intents: integrate, audit, from-zero. Feature autopilot v2; Implementation bridge opt-in; ArkGate post-gate sync; dashboard HTML; polyglot + monorepo hubs; team governance (docs/team); living claims v0 + local CI structural audit (Knowledge OS first increment toward 100×). On conflict code wins.
Docs as QA: audit doc coverage and freshness, validate runbooks, and maintain documentation quality gates for APIs, services, events, and operational workflows. Includes AI-assisted audits, observability patterns, and automated coverage tracking.
Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current source, tests, CLI help, public releases, and repository conventions.
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit without naming a narrower skill.
Periodically audit a repository's docs for staleness against the implementation: run a cheap mechanical scan (dead source-path references, dead links, leftover DEPRECATED/TBD banners, doc-vs-code freshness gap, git-invisible ignored leftovers, completed-but-undeleted plan files), then dispatch parallel read-only agents to verify only the suspicious docs against source, and finally propose update / delete / migrate-to-ADR dispositions for user approval. Use on a monthly or quarterly docs review, after large refactors or renames, or when asked whether docs are stale.