Skip to content

v3.0.0 — DOX.md rename & universal multi-harness toolchain

Choose a tag to compare

@jpbaking jpbaking released this 19 Jul 05:00
· 4 commits to main since this release

Breaking: the framework doc is now DOX.md

AGENTS.md has become a shared convention across AI coding harnesses (Codex, Claude Code, Copilot, Cursor, …), so using it for the DOX framework created conflicts. The framework rules now live in DOX.md; a lightweight root AGENTS.md shim points harnesses at it, and CLAUDE.md bridges Claude Code via @AGENTS.md.

Migrating from v2

Run the dox-upgrade skill — it merges the new framework rules while preserving all project content, renames confirmed legacy DOX docs to DOX.md, and creates the AGENTS.md / CLAUDE.md bridges. A no-skills prompt version is in the README. Legacy pre-v3 roots are still detected and governed until you migrate.

Universal multi-harness toolchain

  • One installer (install.sh / install.ps1) replaces the Cline-only installers: portable Agent Skills go to .agents/skills/ (Codex, Antigravity, Cline) and .claude/skills/ (Claude Code), with the shared always-on rule in each host's rule directory. Each file is fetched once and copied to sibling locations; existing root instruction files are never overwritten, and a legacy v2 framework root is detected and pointed at dox-upgrade.
  • Skills are now shared (skills/shared/), using only portable name/description metadata, and all understand both DOX.md and legacy AGENTS.md roots, nested-root boundaries, and the harness bridges.
  • New dox-remap skill — a deep code-reading pass that rebuilds and refines every Feature Map: discovers unmapped features, retires defunct entries, fixes orphaned/mislocated entries.
  • Deeper dox-audit / dox-fix — new checks for orphaned, mislocated, and unmapped Feature Map entries, legacy filenames, and the AGENTS.md/CLAUDE.md bridges.
  • Hardened legacy handling — every AGENTS.md is classified (shim / legacy framework root / legacy child / unrelated harness file) before any rename; destination conflicts are reported, never overwritten; nested roots under either filename stay untouched.