infiquetra-codex-plugins

Route proposed Team Mimir profile behavior changes into target-owned Hermes dialogue after producer-owned custody classification.

Compile and review an approved Workflow Contract for Codex V2 graph, profile, write, check, reviewer, fallback, and external-action consistency without launching work.

Explicitly run an operator-approved Infiquetra Workflow Contract as a root-orchestrated Codex V2 DAG with exact profiles, runtime receipts, bounded writes, one independent review, one remediation, and one targeted recheck.

Deep-dive one chosen Infiquetra idea into a right-sized requirements document before planning.

Run a structured Infiquetra code-quality review at the work-to-PR boundary. Reads the merge-base diff, runs a built-vs-planned audit plus judgment-selected review lenses, validates findings, writes a durable review artifact, appends to the work-thread saga, and routes — without mutating code. Triggers on "review this PR", "code review", "check my diff", "pre-PR review", or a /work hand-in before shipping.

Review Infiquetra plans, requirements, and SDLC documents for implementation readiness.

CEO/founder-mode scope and ambition review. Rethink the problem, find the 10x product, challenge premises, expand or cut scope deliberately — across four committed modes (SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION). Fires upstream of execution on a /plan artifact, STRATEGY.md, /brainstorm output, or an ad-hoc scope question; produces a scope decision and routes deep rigor back to /doc-review and /code-review in a closed loop. Triggers on "think bigger", "expand scope", "is this ambitious enough", "rethink this", "scope review", or a /ceo-review invocation. Does not implement, record strategy, file issues, or change code.

Generate and critically evaluate grounded Infiquetra product, architecture, or workflow ideas. Multi-agent divergent→convergent engine — generate many, critique all, explain survivors only. Triggers on "ideate on X", "give me ideas", "what should I improve", "surprise me", "what would you change".

The Infiquetra systematic-debugging engine. Find the root cause of a bug, test failure, error, or unexpected behavior before any fix. Diagnosis is the primary deliverable: it writes an agent-consumable DEBUG REPORT, routes real implementation work to saga:work via a saga:handoff issue, design problems to saga:brainstorm, and trackable defects to saga:handoff. Read-only on the world and the saga; never commits, pushes, opens a PR, or deploys.

The explicit Infiquetra lifecycle router and resume substrate. Three modes — Route (dispatch the one next command), Drive (walk phases across the lifecycle, pausing at every gate and handoff), and Resume (scan the saga, restore the work-thread, re-enter where it left off). Reads the saga at entry, ticks it on every routing decision, and routes to the destination command — which owns its own phase work, gates, AND its own execution backend. Invoke explicitly with "loop", "where does this go", "route this", "drive it through the lifecycle", "resume", "what's in flight", or an issue/plan path.

The two-mode frame-finding front door for early Infiquetra thinking. Startup mode runs the six market/customer forcing questions (stage-aware); Builder mode runs discovery/shaping for infra, workflow, and internal-tooling. Finds the right frame, then routes — to /ideate, /brainstorm, /plan, or /strategy. Triggers on "office hours", "is this worth building", "help me think through this", "I have an idea but I'm not sure what it even is", "what's even the right frame here".

Run a metric-driven Infiquetra optimization loop — define a measurable goal, baseline current behavior, generate a hypothesis backlog, run bounded one-variable experiments, measure each against hard degenerate gates before any LLM-judge, keep the best real improvement and revert the rest, and converge on the measurably-best version. Eight metric classes (perf, cost, reliability, agent-usability, security, quality/accuracy, developer-experience, maintainability). Off-chain and saga-untouched; it finds the winner, then routes it to /work to ship — it never commits, merges, or deploys. Triggers on "optimize this", "make it faster/cheaper", "tune this", "baseline and improve", "drive this metric to a target", or a perf finding handed in from /qa or /loop.

Create durable Infiquetra implementation plans with issue, review, test, and deploy gates. Interrogates HOW work gets built, writes an agent-consumable plan artifact, records a plan saga, and routes to doc-review and /work. Triggers on "plan this", "how should we build this", "create a plan", "break this down", or a handoff issue ready for planning.

Run a risk-driven Infiquetra acceptance-evidence QA gate on shipped work. Restores the work-thread saga, classifies the change into risk classes, runs acceptance checks (including browser behavior via the installed MCP), gathers evidence, assigns severity, derives a ship verdict, writes a durable QA artifact, advances the saga qa-track on pass, and routes by merge state — without fixing, committing, or deploying. Triggers on "qa", "run QA", "does this actually work", "acceptance check", "ship-readiness", or a /work or /code-review hand-in after merge.

Reconstruct an Infiquetra Saga lifecycle across Saga ticks, issues, PRs, committed docs, or explicitly requested multi-session forensics. Use when the user asks to reconstruct lifecycle state, reconcile issue or PR history, recover missing Saga state, or determine the next lifecycle owner. Do not use to continue a known saved Codex chat; native /resume owns that.

The Infiquetra lifecycle META-IMPROVEMENT ENGINE. The TERMINAL, ADVISORY lifecycle phase downstream of /qa — it reads the work that shipped, gathers evidence (git forensics behind a stale-base/wrong-today BLOCK guard, saga trajectory, gh issues/PRs READ-ONLY, session transcripts), interviews the operator, writes a concise agent-consumable retro doc, PROMOTES generalizable findings into the engineering journal (pure-append, auto), CURATES the journal + auto-memory (staleness / contradiction / dedup / rule-enforcement sweeps, propose-diff-and-wait), and runs net-new meta-improvement passes (new-skill detection, refine the lifecycle SKILLs, refine directives, prune memory) — every one gated. It never blocks /loop, never mutates the world, never writes the saga, and never self-applies a non-journal edit. Triggers on "retro", "retrospective", "what did we learn", "leave the system smarter", a /qa or /handoff hand-in, or the end of a meaningful work loop / PR / deploy.

Interrogate a vague ask into a precise, backlog-ready WHAT spec — five-Why, scope/MVP lock, failure-mode enumeration, read-code-first, quantify-everything. Convergent and relentless on one decided direction. Triggers on "spec this out", "turn this into a spec", "what exactly are we building", "sharpen this ask before handoff", and when /office-hours, /loop, or /brainstorm have settled the WHY but the WHAT is still fuzzy.

Create or maintain the repository root STRATEGY.md — the durable direction anchor (target problem, approach, who it's for, key metrics, tracks). Interview-driven and rerunnable. Triggers on "write our strategy", "update the direction", "what are we working on", "set up the strategy doc", and when /ideate, /brainstorm, or /plan need upstream grounding and no STRATEGY.md exists yet.

Execute a settled Infiquetra plan to PR-ready, then own the round-N PR continuation loop. Restores and writes the work-thread saga (the primary writer), recommends an execution backend, runs risk-gated tests, calls /code-review programmatically and reads its envelope, gates hard on P0/P1 and stale reviews, and coordinates PR-open/review-request/merge under explicit confirmation — without owning deploy. Triggers on "build it", "work this plan", "execute the plan", "resume work on

Alias-style skill for founder-review. Use when the user asks for CEO review, founder review, scope ambition review, scope expansion/reduction, or whether a plan, strategy, feature, or PR is ambitious enough.

Route durable Infiquetra lifecycle artifacts into mission-control prepared issue drafts.

Author profile-backed, builder-ready implementation specs for Infiquetra context libraries. Detects or asks for the target *-context-library, uses that library's own authoring standard, and routes buildability-style review through saga:doc-review when the profile defines exact inputs and pass criteria.

Coordinate a whole outcome as a durable Codex Saga DAG. Use for start, load, status, report, graph, advance, attend, discover, handoff, and attach of outcome subplots. The coordinator routes work and records receipts; it does not execute leaf work in-context.

De-risk surviving Infiquetra ideas before committing to a build. Slots after saga:ideate and before saga:brainstorm or saga:plan. Per idea: riskiest assumption, smallest build-to-learn, success metric threshold, premise check, and operator-confirmed route.

Promote select cross-repo transcendent learnings into the context-library engineering journal as proposed, gated, idempotent entries.

Application security audit focused on URL and input trust boundaries, SSRF-style risks, redirects, metadata endpoints, allowlists, and evidence-backed findings. Use when reviewing code that accepts URLs, fetches remote resources, follows redirects, proxies requests, imports external data, parses user-controlled input, or touches network egress controls.

Assign covered issues to Team Mimir and provide operator-facing GraphQL + REST helpers for the active project boards. Wraps the GitHub APIs the orchestrator uses, so Jeff can do per-card work (set Initiative/Objective fields, link or unlink sub-issues, validate card bodies, self-heal labels, discover project mappings, assign covered issues to Team Mimir) without writing GraphQL by hand. Each command is idempotent where possible, and surfaces partial failures clearly.

Create and manage SDLC issues in Infiquetra GitHub repositories using the 5-type issue taxonomy: capability, enhancement, defect, exploration, and context-update. Handles issue type selection, template-guided creation, Hermes label application, project board assignment, and milestone linking.

Manage GitHub labels and project field options for Infiquetra repositories. Handles applying SDLC labels to issues, auditing repos for missing labels, deploying the full label taxonomy, auto-labeling issues based on title/body patterns, and creating new field options when new initiatives or objectives are introduced.

Manage GitHub Milestones for Infiquetra Objectives. Creates, lists, links, and tracks milestone progress when an Objective needs due-date rollup across one or more repos.

Track and drive SDLC rollout across Infiquetra organization repositories. Provides rollout status dashboards, gap analysis per repo, label and template deployment, and progress tracking. Uses GitHub repos, issue templates, labels, project mapping, and rollout-status tracking.

Manage UniFi network infrastructure — devices, clients, VLANs, firewall rules, traffic routes, port forwards, VPN, DNS, DHCP, and stats — via the UniFi OS API

Manage UniFi Protect cameras, PTZ control, motion/smart events, NVR info, liveviews, lights, sensors, chimes, and viewers

Prepare Discord bot and guild visual identity assets using Codex image generation plus deterministic post-processing, publishing, verification, and receipts.

Manage the Infiquetra GitHub Projects boards: Operations, Asgard, and CAMPPS. Handles board views, status moves, item adds, terminal-item archive, WIP analysis, field discovery, and standup preparation.

Flow metrics and analysis for Infiquetra project boards using GitHub timeline events. Provides cycle time, throughput, WIP age, per-status time breakdowns, and interpretation guidance across Operations, Asgard, and CAMPPS.

Prepare and promote an Infiquetra hotfix tag through the deployment workflow.

Preview release notes for an Infiquetra tag-promotion deployment candidate.

Promote an Infiquetra repository by minting a policy-compliant deployment tag. Use for nonprod, staging, production, and rollback tag-promotion flows.

Infiquetra deployment state and tag-promotion guidance. Use for deploy, deploy-status, deploy-notes, deploy-hotfix, rollback planning, hotfix promotion, and deployment evidence.