explorer
claudeExplore a backend codebase ONCE with breadth+depth sub-agents, then write a durable .claude/explorer/ memory so any future session understands the code (what / why / how) without re-exploring.
3 skills · 1 command · 2 agents · hooks
Spec-driven agentic implementation for Claude Code. Reads explorer codebase memory as ground truth, plans a requested change with clarity + technical-plan gates (9/10 required), implements only what the spec says, runs hybrid QA, and keeps the durable memory in sync. Includes a reproduce-first BUG-FIX MODE (failing reproduction + characterization tests + deterministic regression gate) for vague, repro-less bug reports.
Plugin builder from marketplace backend-agentic-marketplace in hafizmirhamza276-lab/backend-agentic-marketplace. Commands read from the repo's manifest — 1 month ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
apply-changeImplement an APPROVED plan (.claude/builder/PLAN.md) exactly as written — edit only the files listed in the plan's Scope, follow the conventions recorded in MEMORY.md, keep diffs minimal, and produce a change report. Use only after the orchestrator has rated the plan 9+/10 and validate-plan.sh has p
diagnose-bugBUG-FIX MODE: turn a vague, repro-less bug report (e.g. 'the search field is not working', empty repro steps) into a verified, regression-safe fix via a deterministic symptom→reproduce→root-cause→characterize→fix→regression-gate workflow. Use when a spec is a bug report (auto-detected by a 'Bug:'/sy
micro-decomposeDecompose a requirement into the smallest INDEPENDENTLY-VERIFIABLE units, then harden each with an explicit edge-case enumeration drawn from a fixed taxonomy plus the codebase-specific risks in MEMORY.md. Use during planning (to write the PLAN.md '## Tasks' breakdown) and during implementation/QA (t
plan-changeTurn a spec (.claude/specs/specN.md) plus the explorer memory into (a) a clarity rating out of 10 and (b) a technical implementation plan that the orchestrator can rate. Use after recall-memory, before any code is written. Enforces evidence-first planning: every claim cites path:line, scope is an ex
qa-verifyVerify a freshly built feature with a hybrid strategy: auto-detect a real test/build harness and (with confirmation) run it for feature-level edge cases AND app-level regression; if no harness exists, fall back to rigorous static analysis and edge-case enumeration. Use after apply-change, before rep
recall-memoryLoad the durable codebase memory written by the explorer plugin (.claude/explorer/MEMORY.md, index.json, TRACK.md, map/*.md) and turn it into a compact, build-ready context brief. Use this BEFORE planning or changing any code. Never re-scan the codebase when valid memory exists — recall is cheap, re
sync-memoryAfter a change is implemented and QA'd, update the durable memory so the next session is accurate: refresh the affected explorer artifacts (.claude/explorer/MEMORY.md, index.json, TRACK.md, map/*.md) and the builder log. Use as the final builder step. CRITICAL: resolve every index.json path on disk
/builder:startSpec-driven build. Reads the explorer memory as ground truth, plans a change from .claude/specs/, gates it (clarity 9+/10, technical plan 9+/10), implements only what the spec says, runs hybrid QA, then syncs the durable memory. Usage: /builder:start [optional note]
/builder:statusShow the current builder state cheaply — reads .claude/builder/ artifacts (PLAN.md, CHANGELOG.md, QA.md, settings.json) and explorer freshness, without spawning any sub-agents. Use to resume or inspect.
builder-context-finderRead-only context loader for the builder flow. Recalls the explorer codebase memory (.claude/explorer/*) and produces a compact build-ready brief. Invoked first by /builder:start. Never scans the codebase from scratch and never edits anything.
builder-diagnosticianCritical-tier bug diagnostician for the builder flow (Opus 4.8, effort xhigh). Invoked by /builder:start in BUG-FIX MODE to run symptom intake → reproduce-first → root-cause → characterization (Phases B0–B3): writes the Bug Brief to .claude/builder/BUG.md, a FAILING reproduction test, characterizati
builder-implementerImplements an APPROVED plan for the builder flow (Sonnet). Invoked by /builder:start only after the plan is rated 9+/10 and validate-plan.sh passes. Edits ONLY the files in the plan's Scope, follows MEMORY.md conventions, keeps diffs minimal, and writes a change report. The PreToolUse scope guard bl
builder-memory-syncFinal builder step (Sonnet): updates the durable memory so the next session is accurate — refreshes the affected explorer artifacts (MEMORY.md, index.json, TRACK.md, map/*.md) and the builder log. Invoked by /builder:start after QA passes. Resolves every index.json path on disk via find/glob (never
builder-planner-deepOpus escalation planner for the builder flow. Invoked ONLY when the Sonnet planner has failed to produce a 9+/10 plan within the configured loop limit (default 2). Same job as builder-planner — recall context, read specs, rate clarity, write .claude/builder/PLAN.md — but with deeper reasoning. Token
builder-plannerSpec-driven planner for the builder flow (Sonnet). Reads the spec(s) in .claude/specs/ plus the explorer memory, rates clarity /10, and — only if clear enough — writes a technical implementation plan to .claude/builder/PLAN.md. Invoked by /builder:start after context is loaded. Does not write code.
builder-qa-deepOpus escalation for QA in the builder flow. Invoked ONLY when the Sonnet QA agent failed to reach a 9+/10 result within the configured loop limit (default 2). Same hybrid method as builder-qa, with deeper edge-case and regression reasoning. Token-heavy; last resort, gated by settings.opus_escalation
builder-qaQuality assurance for the builder flow (Sonnet). Invoked by /builder:start after implementation. Hybrid: auto-detects a test/build harness and (with confirmation) runs feature-level edge cases + app-level regression; if no harness, does rigorous static analysis. Writes a QA report and a confidence s
"${CLAUDE_PLUGIN_ROOT}"/scripts/check-builder-state.sh
"${CLAUDE_PLUGIN_ROOT}"/scripts/guard-scope.sh
"${CLAUDE_PLUGIN_ROOT}"/scripts/guard-bugfix.sh
"${CLAUDE_PLUGIN_ROOT}"/scripts/guard-bash-write.sh
"${CLAUDE_PLUGIN_ROOT}"/scripts/lint-feedback.sh
"${CLAUDE_PLUGIN_ROOT}"/scripts/record-progress.sh
"${CLAUDE_PLUGIN_ROOT}"/scripts/verify-build.sh
"${CLAUDE_PLUGIN_ROOT}"/scripts/regression-gate.sh
Explore a backend codebase ONCE with breadth+depth sub-agents, then write a durable .claude/explorer/ memory so any future session understands the code (what / why / how) without re-exploring.
3 skills · 1 command · 2 agents · hooks
Audits this marketplace against its own F1–F13 failure classes: deterministic pure-shell/awk regression detectors (fail-open, path traversal, broken hook contracts, manifest + vendored-lib drift, notebook/stdin/timeout/line-ending gaps) plus breadth+depth review sub-agents. Writes .claude/auditor/FINDINGS.md and records a HIGH count in the STATUS contract so the pipeline release gate enforces 0-high. Silent on a clean tree; no python dependency.
2 skills · 1 command · 2 agents · hooks
Assesses DEPLOY/RELEASE readiness of the codebase. Deterministic pure-shell/awk checks kept deliberately lean — O1 test-ledger (a recorded RED build/test → BLOCKING; no ledger → CONCERN) and O2 version-consistency (a marketplace entry's version ≠ that plugin's plugin.json version → CONCERN) — plus breadth+depth ops sub-agents that inventory the CI/deploy/observability surface and reason about readiness as advisory CONCERN/NOTE findings. Writes .claude/ops/OPS.md and records a BLOCKING count in the STATUS contract so the pipeline release gate enforces 0-blocking. Fuzzy deploy judgment lives in the agents, never a false-firing detector. Silent on a verified, consistent tree; no python dependency.
2 skills · 1 command · 2 agents · hooks
Reviews a CHANGE (the working-tree diff vs HEAD) against the explorer MEMORY.md invariants and risk map, the approved PLAN scope, and the codebase's surviving callers. Deterministic pure-shell/awk checks — R1 caller-integrity & R2 convention-regression (BLOCKING), R3 risk-touch & R4 scope-discipline (CONCERN) — plus breadth+depth review sub-agents. Writes .claude/reviewer/REVIEW.md and records a BLOCKING count in the STATUS contract so the pipeline release gate enforces 0-blocking. Orthogonal to the auditor (change-vs-invariants, not whole-tree regression). Silent on a clean/in-spec change; no python dependency.
2 skills · 1 command · 2 agents · hooks
Conductor plugin: sequences the explorer -> builder flow (running exploration first when memory is missing/stale, then the spec-driven build or BUG-FIX MODE) and gates the result behind a deterministic RELEASE GATE — fresh explorer memory, builder done with a full task coverage map, bug-fix verification net green, CHANGELOG present, and (when present) auditor 0-high. Advisory by default; enforce via settings.enforce_release or PIPELINE_ENFORCE=1. The gate is pure shell/awk, so it behaves identically on python-less / Windows hosts.
1 skill · 3 commands · hooks
Always-on "write the least code that fully works" discipline. A SessionStart hook injects the full decision LADDER (skills/minimal-code) and a UserPromptSubmit hook re-injects a compact reminder every turn, so the agent ships the SMALLEST code that satisfies the requirement WITHOUT cutting validation, error handling, security, or accessibility. Both hooks are node-guarded and fail-quiet (node is OPTIONAL — absent means the hooks stay silent and the skill still works on demand) and INJECT CONTEXT ONLY (no gate decision; every gate in this marketplace stays pure shell/awk). Intensity off|lite|full|ultra via /minimize, mirrored into STATUS.json. YAGNI applies only to UNREQUESTED scope — anything the builder PLAN or the user mandates stays in-scope. Ladder adapted from Ponytail by Dietrich Gebert (MIT).
1 skill · 1 command · hooks
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development
9 skills · 1 command · 8 agents
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.