Lint and validate the Logics Markdown conventions. Use when Codex should verify filenames, top headings, and required indicators across `logics/request`, `logics/backlog`, `logics/tasks`, `logics/product`, and `logics/architecture`, and report inconsistencies.
Update Logics indicators consistently. Use when Codex should update request/backlog/task indicators (`From version`, `Understanding`, `Confidence`, `Progress`, `Complexity`, `Theme`) or companion doc indicators in `logics/product|architecture/*.md` such as `Date`, `Status`, `Drivers`, related refs, and `Reminder`.
Manage this repository's Logics workflow (logics/request -> logics/backlog -> logics/tasks) and keep companion product or architecture refs aligned: create new request/backlog/task docs, promote between stages, keep From version, Understanding, Confidence, and Progress indicators consistent, and generate correctly-numbered filenames. Use when a user asks to triage an idea, write a request, promote it to a backlog item, or create an executable task plan.
Bootstrap the Logics directory structure in a new repository (create `logics/architecture`, `logics/product`, `logics/request`, `logics/backlog`, `logics/tasks`, `logics/specs`, `logics/external`) and add `.gitkeep` files for empty folders so the structure stays versioned. Use when setting up Logics in a fresh project or validating that required directories exist.
Generate Logics workflow Mermaid blocks with a deterministic fallback that stays compatible with the flow manager.
Generate a consolidated index of Logics documents. Use when Codex should build or refresh `logics/INDEX.md` summarizing requests, backlog items, and tasks with titles and progress.
Build and maintain relationships across Logics documents. Use when Codex should discover or summarize links between `logics/request`, `logics/backlog`, `logics/tasks`, `logics/specs`, `logics/product`, and `logics/architecture` by scanning references and generating a relationship report.
Convert acceptance criteria into a concrete validation/test plan. Use when Codex should turn backlog/spec acceptance criteria into unit/integration/e2e test ideas and update the task/spec validation section with relevant commands.