odin-claude-plugin

Demolish bloated code and re-derive it clean, cutting every surface the rebuilt contract does not name. Use for a repo-wide bloat sweep, when patching a subsystem has stopped paying, or when the user says "this whole module is bloated", "rewrite this properly", or "break it and rebuild".

Use when the user says "deslop", "remove debug code", "find placeholders or stub code", or "remove dead code".

Dispatch compress operations. Use when the user says "tidy" or names a file, diff, memory, workspace, git stack, or doc to tidy.

Reduce internal duplication, dead code, and ceremony. Use when you spot dead fields, redundant wrappers, or speculative abstractions in code you are already editing.

Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly.

Use when the user says "simplify this diff", or asks for a compression pass over a change-set.

Design-by-Contract (DbC). Use when crossing public API boundaries, guarding complex state invariants, or hardening untrusted inputs and integration seams.

Drive decomposable work as a deterministic multi-subagent workflow: phased fan-out under per-task contracts with adversarial verification. Use for audits, migrations, broad research or review sweeps, work needing independent cross-checks before committing, or scale one context cannot hold.

Use when user, agent, and codebase may hold different pictures of the current state: before substantive work after a gap, or mid-session when parties talk past each other. Triggers: "mutual sync", "sync up", "are we on the same page", stale user claims about the code, refuted agent assumptions.

Use when the user wants to walk a complex design space round by round: map the decision tree, fire the current frontier as batched single-select questions, and loop until shared understanding is reached. Triggers: multi-fork decisions, ambiguous requirements, unresolved prerequisites, "batch ask me", "clarify the design space".

Use when the user wants to design a recurring personal or team workflow: capture loops, write specs in workflows/*.md, and run a stateful askme session until the spec is implementer-ready. Triggers: "loop me", "design a workflow", "automate this recurring task", morning routine, inbox processing.

Use when the user wants to turn a knowledge gap into an async questionnaire for someone else: identify the recipient and the needed answers, then write a discovery questionnaire to to-questionnaire-<slug>.md. Triggers: "turn this into a questionnaire", "questionnaire for X", "I need to ask someone else", async information gathering.

Use when the user wants to build an article as a choose-your-own-adventure journey of beats, sequence raw material one move at a time, or says "write this beat by beat", "journey-style article", or "assemble beats".

Use when the user wants to generate raw writing material before structuring it, has scattered ideas for an article, or says "collect fragments", "mine this topic", or "gather notes first".

Use when the user wants to turn a pile of fragments into a polished article, shape raw material paragraph by paragraph, or says "write this up", "turn this into a post", or "structure these fragments".

Snapshot the current session into a resumable handoff artifact so a cold session, agent, or person continues without replaying context. Use when the user says "write a handoff", "hand off", "snapshot this session", "I'm running low on context", "pause and pack this up for the next session", or "resume this later".

Use when the user wants to learn a skill or concept across multiple sessions in a persistent teaching workspace at the cwd: they ask you to set up a course, design lessons, build a learning workspace, or explicitly request ongoing teaching. Not for one-off explanations or quick answers.

Wire dependency-cruiser into a TypeScript repo so each package is a deep module: implementation hidden in subfolders, reachable only through its entry-point files. Use when the user asks to enforce package boundaries, set up deep modules, stop deep imports, or wants code outside a package to import only its entry points.

Use when starting UI work, defining palettes or design tokens, or when output looks AI-generic, vibe-coded, or default-framework sloppy.

Use when the user asks to be onboarded, oriented, given a tour, or shown where to start in a repo.

Surface in-task AI collaboration protocols one tactic at a time. Use when the user refers to entities by colloquial labels, asks how to structure a Claude workflow, or describes a multi-step workflow without durable URLs.

Guide stable API and interface design. Use when creating REST or GraphQL endpoints, defining type contracts, or establishing frontend/backend or module boundaries.

Publish a change-set as atomic GitHub issues or PRs. Use when the user says "atomic PRs" or wants one issue/PR per logical change.

Compound a solved problem into a durable in-repo learning doc. Use when a verified non-trivial fix lands, the user says "compound this", "document this fix", or "remember this".

Run a hands-off plan-to-ship pipeline by chaining existing skills. Use when the user says "autopilot", "take this from plan to shipped", "run the whole pipeline", "hands-off ship it", or "do the end-to-end build".

Route contributors to data-backed contribution opportunities. Use when the user asks "where can I help", "what can I contribute", "find a good first issue", or "what should I work on".

Use when removing old code, migrating users to a new implementation, or deciding whether to maintain or sunset something.

Generate a personal taste skill from local evidence and confirmation forks. Use when the user says "generate my taste skill", "make my taste skill", or "derive my taste spine".

Use when a change spans multiple files, or you're about to write a lot of code at once.

Use when the user asks to audit memory or find stale or duplicate memories.

Use when the request has multiple independent sub-tasks, cross-domain research, or parallelizable file or module work.

Use when PRs may conflict with each other or the base, or require ordered application.

Use when validating a set of PRs together on a staging branch before advancing the base branch.

Use when researching a named library, framework, SDK, API, or service, or finding a migration guide.

Use when defining product strategy, setting a north star, starting or redirecting a product, or an existing STRATEGY.md has gone stale.

Bootstrap strict-mode tooling and per-task GOALS.md scaffolding so an agentic loop can self-verify. Use when setting up a new project, making a task self-verifying, or scaffolding goals for an agentic loop.

Execute a multi-task plan. Use when the user says "execute with subagents", or hands you an ordered multi-task plan to run.

Run code analysis and refactoring with ast-grep. Use when doing AST-based modifications, structural search, linting across code shape, or replacing regex-fragile transformations.

Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.

Use when asked to ship/publish commits without opening a PR.