code

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

Skills (13)

• build-status-cache

  Skip Phase 7 rebuild when no code changed since Phase 5 build passed. Compares git diff hash against stored hash from last successful build validation. Triggers on: entering Phase 7, checking build status, before final build validation. Returns BUILD_CACHE_HIT to skip or BUILD_CACHE_MISS to re-run b

• closedloop-env

  Provides ClosedLoop environment paths (CLOSEDLOOP_WORKDIR, CLAUDE_PLUGIN_ROOT) to agents. This skill should be used by any agent that needs to access ClosedLoop run directories, plugin schemas, or other path-dependent resources.

• codex-review

  Run Codex to review a plan file and return structured feedback with a verdict. Triggers on: debate loop Codex review rounds. Returns VERDICT:APPROVED or VERDICT:NEEDS_CHANGES plus CODEX_SESSION token.

• critic-cache

  Check if critic reviews are still valid before re-running Phase 2.5 critics. Compares plan.json + critic-gates.json content hash against stored hash from last critic run. Triggers on: entering Phase 2.5, checking critic cache, before launching critics. Returns CRITIC_CACHE_HIT to skip critics or CRI

• cross-repo-cache

  Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSS_REPO_CACHE_HIT with ca

• design-inventory

  Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse

• extract-plan-md

  Sync plan.md with plan.json content. MUST be used after ANY edit to plan.json to keep plan.md in sync. Triggers: - After editing plan.json with Edit tool (REQUIRED - always sync after edits) - User asks to "sync plan.md", "update plan.md", "extract the md from a plan" - Converting plan.json to markd

• find-plugin-file

  This skill should be used when needing to locate files within the Claude Code plugins cache directory (~/.claude/plugins/cache). Triggers include finding tool scripts, skill files, or any plugin resource when the hardcoded path is unknown or varies by plugin version. Use when slash commands or orche

• iterative-retrieval

  Protocol for iteratively refining sub-agent queries through follow-up questions to ensure sufficient context

• orchestrator-sequences

  Canonical reusable orchestration procedures for the ClosedLoop planning/implementation orchestrators: PLAN_VALIDATION_SEQUENCE and AWAITING_USER_SEQUENCE. Single source of truth shared by prompts/prompt.md (/code:code), prompts/plan-prompt.md (/code:create-plan) and prompts/execute-prompt.md (/code:

• plan-editing-conventions

  Conventions for editing plan.json implementation plans including task format, structured arrays, and plan structure rules. Use when creating or modifying plan.json files.

• plan-validate

  Deterministic plan.json validation via Python script, replacing most plan-validator agent calls. Performs JSON parsing, schema validation, task checkbox regex, required section checks, sync validation, and data extraction. Only semantic consistency checks (storage/query alignment) require the LLM ag

• prd-creator

  This skill helps PMs draft lightweight PRDs. It should be used when a PM wants to define a new feature, brainstorm requirements, or prep for sprint planning. Triggers include "I have a feature idea", "help me write a PRD", "let's break this into stories", or "what do I need for sprint planning". Opt

Slash commands (6)

• /code:amend-plan

  Plan Amend - Discuss and apply amendments to a plan.json implementation plan

• /code:code

  Begin coding session

• /code:create-plan

  Create an implementation plan

• /code:design-inventory

  Run the Claude Design to ClosedLoop pipeline: Stage A inventories a design export zip into schema-validated findings and publishes a platform Design Review document; Stage B is human review; Stage C derives decisions from the edited document and generates DRAFT feature tickets.

• /code:execute-implementation

  Execute an implementation plan

• /code:plan-with-codex

  Iterative plan refinement debate between Claude and Codex

Subagents (24)

• amend-extractor

  Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.)

• answered-questions-subagent

  Processes answered questions from plan.json and incorporates them into relevant tasks.

• api-spec-writer

  Produces api-requirements.md from an approved plan. Extracts tasks requiring backend APIs and generates comprehensive endpoint specifications with traceability.

• behavior-verifier

  Activates decision-table in verification-only mode against the decision-table artifact and final code. Identifies drift and appends Verification Findings to the artifact. Never modifies code or tests. Returns ALIGNED or MISALIGNED with typed drift rows for orchestrator routing.

• build-validator

  Discovers and runs project validation commands (test, lint, typecheck, build). Caches discoveries as learnings for future runs.

• code-review-guidelines
• code-reviewer

  Reviews code changes for quality, security, and best practices across any language. Use after implementation to identify bugs, security issues, and code quality problems. Returns findings by severity (Critical, High, Medium, Low).

• cross-repo-coordinator

  Discovers peer repositories and identifies cross-repo capability needs. Does NOT verify or search peers - that's done by generic-discovery.

• cross-repo-prd-writer

  Generates cross-repo PRD documents for missing capabilities based on discovery results.

• design-unit-analyst

  Analyzes one design unit (screen, region, component, or flow) from a Claude Design export against the current web-ui codebase ("state vs. spec"). Classifies the unit, itemizes visual/behavioral/component-divergence/backend-gap/token-drift changes, maps added UI elements to existing Storybook compone

• dev-environment

  Detects project types and determines how to start dev servers across all workspace repos. Reads .workspace-repos.json for repo list.

• generic-discovery

  Generic cross-repo discovery agent. Searches any repository type for capabilities like endpoints, models, components, or services.

• implementation-subagent

  Implements missing requirements for a task from the implementation plan.

• learning-capture

  Processes pending learnings from $CLOSEDLOOP_WORKDIR/.learnings/pending/ and classifies them for storage

• plan-agent

  Software architect agent for creating and revising implementation plans. Explores codebases, designs plans, and writes them directly to disk. Used by plan-with-codex for iterative plan refinement.

• plan-draft-writer

  Creates high-level implementation plan drafts from PRDs. Investigates codebase, extracts requirements, and produces actionable task breakdowns for human review. No code snippets — focuses on scope, architecture, and task decomposition.

• plan-evaluator

  Evaluates plan complexity for simple-mode eligibility and selects critic agents

• plan-importer

  Imports an external markdown plan into the ClosedLoop plan.json format. Reads a source markdown plan, normalizes headings and task lines, derives acceptance criteria, populates all JSON arrays, writes plan.json and plan.md, validates the result, and writes a completion marker.

• plan-validator

  Validates plan.json structure. Returns format issues, open questions, and pending tasks.

• plan-writer

  Modifies existing implementation plans — merges critic feedback, finalizes with implementation details, and incorporates addressed gaps. Does not create plans from scratch (use plan-draft-writer for that).

• pre-explorer

  Pre-explores codebase before plan drafting. Produces requirements-extract.json, code-map.json, and investigation-log.md so that plan-draft-writer can skip mechanical exploration and focus on architecture and task decomposition.

• repo-coordinator

  Discovers peer repositories for cross-repo orchestration. Uses CLAUDE_WORKSPACE_REPOS env var or sibling directory scanning.

• verification-subagent

  Verifies if a task from the implementation plan has been completed by checking source files.

• visual-qa-subagent

  Performs visual QA inspection using Playwright browser automation.

Hooks (7)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/session-start-hook.sh

• SessionEnd

  ${CLAUDE_PLUGIN_ROOT}/hooks/session-end-hook.sh

• UserPromptExpansion

  ${CLAUDE_PLUGIN_ROOT}/hooks/user-prompt-expansion-hook.sh

• SubagentStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/subagent-start-hook.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/pre-tool-use.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/post-tool-use-hook.sh

• SubagentStop

  ${CLAUDE_PLUGIN_ROOT}/hooks/subagent-stop.sh

Similar plugins