Claude Code Plugins

Public Builder skills for docs-first discipline, autonomous execution, cross-agent review, efficient agent workflows, clear status recaps, and Agent-Native Plan modes.

Design operations skills: handoff specs, design critique facilitation, design sprint planning, asset management, and design debt audits.

19 skills + 1 agent + 2 hooks for the full meeting lifecycle: brief, prep, record, tag, debrief, mirror, weekly synthesis, entity graph, video review, and cross-device voice memo recall

Generate LiftLog workout plans (.liftlogplan files) from a training goal, validated against the app's own schema.

Prices your repo's TODO/FIXME/HACK debt as aging XP bounties, injects the top 3 as opportunistic side quests, and verifies + pays out bounties you genuinely clear.

Writes your daily standup from what your agents actually did across repos — captures tasks, tests, PRs, and blockers from session transcripts and re-injects yesterday's open blockers next session.

Autonomous work mode — pre-flight risk assessment, dangerous-ops approval, blocker decision framework, and session-scoped stop hook. Lets Claude work continuously while you're away.

Use /ljg-roundtable <topic> to launch a structured roundtable discussion on any topic

Structured goal-setting exercise using Mental Contrasting with Implementation Intentions

PRD-CE methodology engine: scaffold (PRD/SoT/EPICs) + lifecycle skills + governance hooks + readiness scoring.

GRC domain knowledge — 15 frameworks, 24 commands, cross-framework mapping, document review, and operational workflows. Cloud-agnostic.

法律诊所全流程：指导老师设置、学生学期导入、结构化接待、跨领域问题识别、案件节点管理、备忘录框架、法律检索路线图、结案移交。适配中国法学院法律诊所教学实践。

Claude Code guide — interactive onboarding walkthrough and Q&A on setup, best practices, automation, and effective workflows

Efficient skill management with progressive discovery — 410+ production-ready skills across 33+ domains.

吃一堑长一智 — 6-step interactive reflection for personal setbacks. Diagnoses which layer (L1 notes / L2 in-the-moment trigger / L3 default-reaction practice) is missing and routes to the right modality, instead of letting every reflection become another notebook entry.

Validate implementation plans against DRY, YAGNI, TDD principles and best practices. Identifies gaps, anti-patterns, and improvement opportunities before execution. Prevents over-engineering and ensures test-first approach.

Autonomous Claude + Codex review loop. Plan a feature with adversarial pushback, or audit code, all in one window.

Delegation system with workflow orchestration, specialized agents, and parallel execution for Claude Code

Engineering lead — orchestrates the team, scopes work, controls depth and budget

Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

Knowledge engineer — architecture docs, ADRs, API specs, system diagrams, onboarding

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".

Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".

Internal legal controls review — approval workflows, doc governance

Draft compliance policies required by a framework

Support engineer — ticket workflow design, SLA architecture, knowledge base, escalation paths, and support operations at scale

Product strategist — roadmap planning, prioritization frameworks, competitive analysis, and market positioning

Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".

OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".

Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.

Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".

Revenue & sales engineer — B2B pipeline, deal strategy, pricing, sales playbooks, and enterprise closing

Plan and execute canary releases for model updates — traffic splitting, rollback triggers, success metrics.

Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hierarchy".

UI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wireframe work.

User research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or synthesis work.

User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".

People engineer — org design, hiring pipelines, compensation frameworks, onboarding playbooks, performance management, and human-to-agent migration