← APODICTIC Development EditorCONTENT HISTORY

Update to APODICTIC Development Editor

Snapshot Oct 24, 2026 · 13:33 UTC · version 2.13.3

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save APODICTIC Development Editor and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Codex-generated wrapper for APODICTIC's compatibility command surface. Use when the user explicitly asks for `apodictic-triage-feedback`, or when they say something like \"Sort and prioritize beta-reader / editor feedback.\", or when they want sort, cluster, and prioritize beta-reader and editor feedback. This wrapper mirrors the legacy `/triage-feedback` behavior.\n",
  "included_files": [],
  "name": "apodictic-triage-feedback",
  "skill_md_contents": "---\nname: apodictic-triage-feedback\ndescription: >\n  Codex-generated wrapper for APODICTIC's compatibility command surface. Use when the user explicitly asks for `apodictic-triage-feedback`, or when they say something like \"Sort and prioritize beta-reader / editor feedback.\", or when they want sort, cluster, and prioritize beta-reader and editor feedback. This wrapper mirrors the legacy `/triage-feedback` behavior.\nversion: 2.13.3\n---\n\n<!-- Generated by scripts/build-codex.mjs. Do not edit files in codex/ by hand. -->\n\n# APODICTIC Triage Feedback\n\nThis generated skill exposes the legacy `/triage-feedback` workflow in Codex without duplicating the shared APODICTIC runtime.\n\n## Load Order\n\n1. Read `../../commands/triage-feedback.md` as the canonical command behavior.\n2. Read `../revision-coach/SKILL.md`.\n3. Load only the references, companion skills, and output rules that those source files call for.\n\n## Execution Notes\n\n- Preserve the command's routing, output, and resume behavior.\n- Skip redundant intake when router output or project state has already prefilled the needed context.\n- Follow the folder architecture in `../core-editor/references/output-structure.md` §Folder Architecture: rolling state at the project root, run artifacts in `runs/YYYY-MM-DD_{model}_{type}/`.\n"
}

SHA-256 of public snapshot: b4c9535bab9f410ed502dff7259af1b3db83fcff142d0bf58cfa68cf32cb3633