closedloop-core

Plugin closedloop-core from marketplace closedloop-ai in closedloop-ai/claude-plugins. Commands read from the repo's manifest — today.

Skills (12)

• closedloop-intel

  ClosedLoop ticket + codebase intelligence over a shared remote instance. Use PROACTIVELY for questions about ticket scope overlap or duplicate work ("do these tickets overlap", "is someone already doing this", "is this a duplicate"), blast radius ("if I change this file or symbol, what breaks", "whi

• decision-table

  Use when the user wants a code-grounded decision table for current behavior, wants to compare current behavior against a plan or work item, or needs a control-flow artifact for recovery, retry, finalization, validation, state-machine, or review-heavy edge cases.

• erd-diagram

  Generate or update an interactive ERD (entity relationship diagram) as a single offline HTML file for a Postgres repository, built only from the repo's schema code (a Prisma schema, a SQL schema dump, or a folder of SQL migrations; other ORMs through a model the agent writes from the code). Two styl

• gh-monitor-pr

  Start a detached GitHub pull-request monitor that wakes the exact launching Codex Desktop or CLI root through the managed Codex App Server when review, CI, conflict, merge-queue, closure, readiness, or merge events need attention. Use when the user asks Codex to watch, monitor, babysit, or wait on a

• guided-manual-qa

  Derive and run an interactive, evidence-recorded manual QA session for a code change, ticket, branch, or pull request. Use when a human should validate live behavior checkpoint by checkpoint after repository-aware setup; do not use as a substitute for automated tests or a read-only code review.

• measurement-discipline

  Use when optimizing, benchmarking, profiling, or running a performance experiment; when evaluating whether a change actually helped; or when recording or checking past optimization attempts. Prioritizes the largest credible gains against experiment cost, then enforces one-variable experiments, repea

• mermaid-visualizer

  This skill should be used when a user asks to explain a complex idea, concept, or system architecture, or when a diagram would be helpful to visualize control flows, system architectures, data flows, state machines, sequence diagrams, or entity relationships.

• plan-structure

  Used when creating or updating implementation plans.

• prd-dependency-graph

  Build an interactive dependency graph of ClosedLoop tickets from live BLOCKS links, for a PRD or any other document (PRD-751, ISS-123) or a whole project (PRO-67). Hovering a ticket lights up what blocks it (purple) and what it blocks (teal); clicking pins the whole upstream and downstream chain. Ti

• prevent-recurrence

  Use when correcting an issue or failure reveals a reusable prevention lesson, including code, setup, measurement, validation, workflow, agent mistakes, or accepted code-review findings; when someone says "this keeps happening" or asks how to stop it; or in post-incident follow-up. Fixes the instance

• repo-hardening

  Audit a repository the way a rigorous engineer would and produce an evidence-backed, prioritized improvement plan covering instruction files, lint and source gates, type strictness, test quality, CI and merge flow, review and verification habits, and the mistake classes agents keep repeating in git

• workflow-code-review

  Run a worker-backed code review using its bundled review lenses: approach correctness, architecture ownership, correctness, guardrails, validation, compatibility, and security. Use when asked to review a PR, branch, diff, or uncommitted changes with workflow-level rigor.

Similar plugins