AlexAgo83

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…

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,…

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…

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…

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.

Implement one scaffolded Logics task end to end — read it, build it, validate it, record the outcome, close it out. Use when asked to "implement", "develop", "dev", "build", or "finish" a Logics task or backlog item that already exists.

Diagnose why a task's closeout is blocked and run the specific repair sub-command that fixes it — validate-closeout, repair gates/ac-traceability/links/mermaid. Use when asked to "why won't this task close", "fix the closeout", "repair this task", or when…

Scaffold a ready-to-dev Logics corpus (request → product brief → backlog → orchestration task → context pack) from a feature need, validate it, and commit. Use when the user asks to "scaffold a corpus", "create a request chain", or turn a feature idea into…

Split, promote, withdraw, close, finish, or progress an existing Logics request/backlog/task — the lifecycle moves that fall outside scoping (/corpus) and building (/implement-task). Use when asked to "split this request", "promote this backlog item",…

Run the read-only diagnostics — doctor, health, status, followups, product-consistency, audit — and read their combined output as a pre-flight check. Use when asked "is the project healthy", "run diagnostics", "what's blocked", or "check corpus health" before…

Propose, inspect, or validate a versioned roadmap doc, and deliver a request/backlog/task chain straight from a product brief. Use when asked to "propose a roadmap", "check the roadmap", "validate the roadmap", or "deliver this product brief" — the…

Turn external tracker issues (GitHub or otherwise) into a scoped Logics corpus, recording where each one came from. Use when asked to "groom the issues", "turn these issues into a corpus", or "triage the backlog from the tracker".

Review a codebase and capture the findings as one lightweight Logics request — candidates for future work, not a commitment to do any of it. Use when asked to "review this project", "audit the codebase", or "what should we fix here".