Stats
Actions
Available In
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
Create git commits for session changes with clear, atomic messages
Create handoff document for transferring work to another session
Create detailed implementation plans through interactive research and iteration
Create implementation plans with thorough research (no notes directory)
Implement an approved technical plan. By default, creates an isolated worktree environment. Use `--here` to implement in the current directory.
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :)
Locates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
codebase-pattern-finder is a useful subagent_type for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on what you're looking for! It's sorta like codebase-locator, but it will not only tell you the location of files, it will also give you code details!
Analyzes documentation for key insights. Use when you need to deep dive on research topics or extract decisions from notes.
Discovers relevant documents in thoughts/notes/, thoughts/research/, thoughts/plans/, and related directories. Use this when researching to find historical context and documentation.
Executes bash commands
Hook triggers when Bash tool is used
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A marketplace of commands and agents for Claude Code that enhance planning, implementation, and shipping workflows.
Add the marketplace and install the plugin:
/plugin marketplace add ii-vo/claude-meta
/plugin install claude-meta:slash-command
Or install directly from the marketplace:
/plugin install github:ii-vo/claude-meta
| Command | Description |
|---|---|
/create_plan | Create detailed implementation plans through interactive research |
/create_plan_no_thoughts | Create implementation plans (no notes directory) |
/implement_plan | Execute a plan (creates worktree by default, use --here to stay in place) |
/iterate_plan | Update existing plans based on feedback |
/validate_plan | Verify implementation against plan success criteria |
| Command | Description |
|---|---|
/ship | Ship code via PR (with full description) or direct merge |
/commit | Create git commits with clear, atomic messages |
/ship modes:
/ship - Full PR workflow: analyze, describe, create PR, merge, cleanup/ship --direct - Direct merge to main, no PR/ship --pr-only - Create PR with description, don't merge (for team review)/implement_plan modes:
/implement_plan <plan> - Creates worktree, opens new terminal (default)/implement_plan <plan> --here - Implements in current directory| Command | Description |
|---|---|
/create_handoff | Create handoff document for transferring work |
/resume_handoff | Resume work from a handoff document |
/research_codebase | Document codebase with notes for historical context |
Specialized sub-agents spawned by commands for parallel research:
| Agent | Purpose |
|---|---|
codebase-locator | Find files and directories relevant to a task |
codebase-analyzer | Analyze implementation details of components |
codebase-pattern-finder | Find similar implementations and usage examples |
notes-locator | Discover relevant documents in thoughts/ directories |
notes-analyzer | Extract insights and decisions from documentation |
web-search-researcher | Research topics using web search |
/create_plan → Design implementation approach
/implement_plan → Creates worktree + new terminal with Claude
(your main terminal stays free)
/commit → Commit changes (in worktree terminal)
/ship → Merge PR and cleanup worktree
This is the default workflow. /implement_plan automatically creates an isolated worktree environment so you can continue working in your main terminal while Claude implements.
/create_plan
/implement_plan --here → Implement in current directory
/commit
/ship
Use --here when you want to stay in the same terminal/directory.
(make changes)
/commit
/ship --direct → Merge directly, no PR
/create_plan
/implement_plan
/commit
/ship --pr-only → Create PR for review
(wait for approval)
/ship → Merge and cleanup
/create_handoff → Document current state
(new session)
/resume_handoff → Continue from handoff
.claude-plugin/
marketplace.json # Marketplace definition
plugins/
slash-command/ # Main plugin
.claude-plugin/
plugin.json # Plugin metadata
commands/ # Slash commands
agents/ # Sub-agent definitions
MIT
npx claudepluginhub ii-vo/claude-metaInstaller for TÂCHES' Get-Shit-Done workflow system - meta-prompting, context engineering and spec-driven development
Marcel-BichCommands for orchestrating complex workflows
davepoonImplementation planning, execution, and PR creation workflows with multi-agent collaboration
UniswapDrives a full feature-development workflow (clarify -> design -> plan -> execute -> PR -> test) over Slack via the claude-slack-bridge daemon. Ships /process-setup for one-time per-repo configuration and /process for clarification + handoff to the daemon's workflow engine.
tomeraitzProduction-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards
xiaobei930Harness-native ECC plugin for engineering teams - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
affaan-m