core

Plugin core from marketplace caderon-pack in brent-hoover/caderon-pack. Commands read from the repo's manifest — today.

Skills (14)

• agent-bus

  Message bus between independent Claude Code sessions on this machine (cmux-hosted). Use when the user asks you to register on the bus, message/ask/tell another agent or session, coordinate with an agent in another terminal, or when a prompt beginning with "[agent-bus]" announces a new message for yo

• agent-teams

  How to orchestrate Claude Code's experimental Agent Teams — spawning teammates as separate sessions, delegating work to them, and waiting for results instead of doing the work yourself in the main thread. Use whenever a task should run as parallel/independent workstreams: multi-file refactors, revie

• bdd-specs

  Behavior-driven design: write executable specifications BEFORE any implementation code. Integrates with the doc-driven-development workflow — reads feature-work/<slug>/plan.md and problem.md when present, otherwise falls back to /docs/PLAN.md and /docs/STORIES.md. Generates spec files in nested Feat

• catch-me-up

  Reconstruct and summarize the state of the current working session — what's been done, what's left, and where things stand right now. Use whenever the user asks to be "caught up", says "catch me up", "where were we", "what have we done so far", "remind me where we are", "status", "recap", "summarize

• code-quality

  Standards for maintaining high code quality including comments, test coverage, and documentation practices

• codebase-visualizer

  Generate an interactive collapsible tree visualization of your codebase. Use when exploring a new repo, understanding project structure, or identifying large files.

• conventional-commit

  Create commit messages following conventional commit conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with issue references.

• explain-code

  Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this

• git-master

  Git expert for atomic commits, rebasing, and history management with style detection

• git-worktrees

  Create, list, and remove git worktrees in a consistent, repeatable way. Use when the user asks to work on a branch in an isolated worktree, set up parallel work, spin up a worktree for an agent/PR, or clean up worktrees. Worktrees ALWAYS live in `.worktrees/` at the repository root (git ignored).

• markdown-review

  Use when you have authored documents (markdown plans, designs, reports, analyses; Gherkin .feature files; other text files) that the user should read and give feedback on. Serves them to the user's browser — markdown rendered, .feature files as Gherkin, anything else as numbered source — with a mult

• retrospective

  Analyze the current (or a past) working session end-to-end and deliver a retrospective — what went well, what could improve, and what to stop doing — covering both the user and Claude, with concrete follow-ups like CLAUDE.md edits, new skills, or hooks. Use whenever the user asks for a "retro", "ret

• user-stories

  Write, split, and refine agile/scrum user stories and acceptance criteria. Produces /docs/STORIES.md as the canonical backlog, formatted to feed directly into the bdd-specs skill (Story → Feature, Given/When/Then acceptance criteria → Scenario/Specification). Use this whenever the user wants to writ

• vue-typescript

  Master Vue TypeScript - Type-safe Components, Generics, Type Inference, Advanced Patterns

Slash commands (3)

• /core:quick-fix

  Make a small, obvious fix directly on the current branch. No sprint, no PLAN, no stories.

• /core:retrospective

  Retrospective on a working session — what went well, what to improve, what to stop — with concrete follow-ups.

• /core:worktree

  Create a git worktree for a feature branch at .worktrees/<slug>.

Similar plugins