---
title: "hamster"
description: "Orchestrates Hamster Studio brief execution with team personas, parallel wave execution, and deep review modes. Ask Hamster, plus setup, ship, plan, resume, review, QA, and retro."
canonical: https://agentpluginsdirectory.com/plugins/hamster--gethamster
last-updated: 2026-09-16
---

# hamster
Orchestrates Hamster Studio brief execution with team personas, parallel wave execution, and deep review modes. Ask Hamster, plus setup, ship, plan, resume, review, QA, and retro.
- Slug: hamster--gethamster
- Publisher: Hamster
- Repository: https://github.com/gethamster/plugin
- Manifest: plugin.json
- Version: 3.4.3
- License: MIT
- Category (editorial): other
- Skills: 8 (ask-hamster, plan-hamster, qa, resume-hamster, retro, review-hamster, setup, ship)
- MCP servers: 1 (hamster)
- Stars: 9
- Repository created: 2026-03-02
- Repository last pushed: 2026-09-16
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/hamster--gethamster
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What hamster does, in the publisher's words

Install Hamster. One plugin. Talk through hosted MCP or the CLI. Keep the plan on disk, then ship from it.

This is the Hamster product: Agent Plugins skills on every supported client, hosted MCP on every client that installs from GitHub or a marketplace, plus generated native execution workers on Claude Code where that client registers them. The CLI is how the plan stays in this repo. It is not a second install.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/gethamster/plugin/HEAD/README.md

## Skills

- ask-hamster: Ask Hamster to connect the current code or editor context with workspace priorities, blockers, blueprints, related work, or intent. Also supports workspace actions when the user explicitly requests one.
- plan-hamster: Plan a Hamster Studio brief. Read tasks, build dependency graph, detect parallel execution waves, with optional CEO or Eng review modes. Use when the user wants to analyze a brief before executing.
- qa: Systematic QA with diff-aware, full suite, quick smoke, or regression testing modes. Issue taxonomy and optional fix loop. Use when the user wants to run tests or check quality on their changes.
- resume-hamster: Resume an interrupted brief execution. Auto-detect progress, reconstruct state from git history and task statuses, and continue from the correct wave. Use when the user wants to continue a previously interrupted ship session.
- retro: Engineering retrospective from git history. Team metrics, contributor deep-dives, trends, and actionable insights. Use when the user wants a retrospective on recent development activity.
- review-hamster: Paranoid two-pass code review. CRITICAL issues that block shipping, then INFORMATIONAL advisory findings. Interactive resolution for critical issues. Use when the user wants a code review on their current feature branch.
- setup: Install the Hamster CLI, sign in, and sync the plan into this repo. Use when the user says Install Hamster, first-run setup, or when ship/plan-hamster/resume-hamster report SETUP_NEEDED.
- ship: Ship a Hamster Studio brief. Merge base, implement in parallel waves, test, review, create bisectable commits, and optionally PR. Use when the user wants to execute or ship a brief.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- hamster: transport: streamable-http; url: https://tryhamster.com/mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.