cdx-logics-kit

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.

Write architecture decision records (ADR) in `logics/architecture`. Use when Codex identifies a non-trivial decision (trade-offs, alternatives) and should create a concise ADR document with context and consequences.

Groom and promote a Logics request into a backlog item. Use when a request is clear enough to define scope, acceptance criteria, and priority, and Codex should create `logics/backlog/*.md` aligned with the Logics format.

Curate user-facing project changelog entries from Logics release notes or completed tasks. Use when Codex should turn `logics/RELEASE_NOTES.md` into a cleaner project-level `logics/CHANGELOG.md` and remove internal references/noise.

Detect the repository's likely stack/framework (heuristics) and generate an adapted code-structure review (large files, folder hygiene, suggested module/component boundaries) as a Markdown report. Use when Codex needs to check whether code is overly concentrated in single files and propose clearer structure, even when the stack is not yet known.

Ask clarifying questions with suggested defaults to raise Understanding/Confidence above 90% for Logics request/backlog/task docs, and to strengthen product or architecture companion docs with a clarified `# Clarifications` section plus optional status updates.

Connect Confluence (Atlassian) to the Logics workflow: search pages via CQL and import a page into `logics/request/` as a new `req_###_*.md` with the page content as context.

Connect Figma to the Logics workflow: list pages and nodes, export node images, and import a Figma node reference into `logics/backlog/` as a new `item_###_*.md`.

Connect Jira (Atlassian) to the Logics workflow: search issues via JQL and import a Jira issue into `logics/backlog/` as a new `item_###_*.md`.

Connect Linear (GraphQL) to the Logics workflow: list issues and import a Linear issue into `logics/backlog/` as a new `item_###_*.md` with a link back to Linear.

Connect Render (Public API) to the Logics workflow: list services and deploys, snapshot or apply deployment plan changes, and import a Render service context into `logics/backlog/`.

Validate and repair Logics request/backlog/task/product/architecture docs (structure, indicators, and cross‑references) without deleting existing metadata. Use when Codex should audit `logics/request`, `logics/backlog`, `logics/tasks`, `logics/product`, or `logics/architecture` for missing sections/indicators, auto-update Progress from checkboxes, backfill linked refs when safe, or restore dropped indicator lines.

Detect potential duplicates across Logics documents. Use when Codex should scan titles and content of requests/backlog/tasks/specs/product briefs/architecture docs to find similar items and propose merge, split, or de-duplication.

Estimate effort and complexity for Logics backlog items and tasks. Use when Codex should propose a rough estimate (S/M/L or points), identify unknowns/risks, and recommend splitting work.

Run a global review of the repository's Logics workflow and documents, then propose concrete optimizations/improvements (hygiene, placeholders, stale indicators, missing links, progress distribution) as a Markdown report. Use when Codex needs to audit `logics/request`, `logics/backlog`, `logics/tasks`, `logics/specs`, `logics/product`, and `logics/architecture` and suggest next actions.

Use when an operator asks for repetitive delivery help such as `commit all changes`, `summarize this PR`, `summarize validation`, `what should we do next?`, `triage this request`, or `prepare a handoff`. Prefer the shared hybrid assist runtime so Ollama can be used opportunistically when healthy and the flow can degrade cleanly otherwise.

Install and configure the Chrome DevTools MCP server (chrome-devtools-mcp) in projects and control Chrome via MCP for UI automation, debugging, network/console inspection, and performance tracing. Use when wiring MCP clients (Codex, Claude, Cursor, VS Code, etc.) to Chrome DevTools.

Install, configure, and use a Figma MCP server to connect MCP clients to Figma (search files, read nodes, export assets). Use when wiring MCP clients to Figma.

Install, configure, and use a Linear MCP server to connect MCP clients to Linear (query issues, projects, cycles). Use when wiring MCP clients to Linear.

Install, configure, and use the Notion MCP server to connect MCP clients to Notion (read/query/update pages and databases). Use when wiring MCP clients to Notion.

Install, configure, and use the Terminal MCP (server-shell) for running shell commands in Codex/agents. Use when wiring MCP clients to terminal control, executing commands via MCP, or debugging shell access.

Add ownership and success metrics to Logics backlog/spec docs. Use when Codex should define an owner, success metric/KPI, and instrumentation notes for a backlog item or spec to make outcomes measurable.

Enforce migration and backward-compatibility guardrails in Logics docs. Use when Codex should ensure backlog/tasks/specs explicitly cover schema/data evolution, import-export compatibility, and rollback strategy.

Generate quick PNG UI mockups (dashboards/panels) and store them under logics/external. Use when the user asks for on-the-fly visual mockups or PNG previews.

Install, configure, validate, and integrate Ollama for local development. Use when setting up DeepSeek or Qwen coding profiles for terminal, HTTP API, Continue, or Roo Code workflows, or when wiring frontend/backends to Ollama through Vite or Express proxies and fixing CORS or 403 Origin issues.

Generate a pull request description from a Logics task. Use when Codex should read `logics/tasks/*.md` and produce a PR template (summary, scope, validation, risks) suitable for GitHub/GitLab.

Write product briefs in `logics/product`. Use when Codex identifies a structuring product framing need (user problem, target users, scope, trade-offs, success signals) and should create a concise product decision document linked to request/backlog/task docs.

Bootstrap a production-ready React web project with Vite, TypeScript, PWA support, Render blueprint, and CI/testing defaults aligned with the stack patterns used in electrical-plan-editor and Sentry. Use when starting a new app that should ship quickly with lint/typecheck/test/e2e gates, deploy on Render, and support either frontend-only static hosting or a fullstack frontend+Fastify+Prisma setup.

Run project release-readiness gate checks on Logics docs and produce a pass/fail report. Use when Codex should verify completed work has validation evidence, report sections, rollback coverage for risky changes, and project changelog readiness.

Generate project-level release notes from completed Logics tasks. Use when Codex should scan `logics/tasks` and produce a Markdown release notes file grouped by completed work (e.g., Progress 100%).

Add a risk/rollback review to Logics docs. Use when Codex should identify risks, mitigations, rollbacks, and operational considerations for a backlog item or task, and update the Markdown accordingly.

Create lightweight functional specs inside this repo. Use when Codex should write a structured spec document in `logics/specs/*.md` derived from a backlog item or task, with clear scope, acceptance criteria, and validation/test plan.

Break down a Logics backlog item into executable tasks. Use when Codex should turn `logics/backlog/*.md` into one or more `logics/tasks/*.md` with step-by-step plans, validation commands, and progress tracking.