common
Open Engineering - Common MCP configuration, workflows and tools for Software Engineering.
/plugin install common@odyssey
MCP Servers
| MCP | What it does |
|---|---|
| slack | Post messages and read Slack channels via the official MCP server |
| atlassian | Read and interact with Jira and Confluence over HTTP |
| notebooklm | Interact with Google NotebookLM notebooks |
| figma | Access Figma design files, components, and prototypes over HTTP |
| chrome-devtools | Browser automation via Chrome DevTools Protocol (performance, network, emulation) |
| gitlab-cli | Manage GitLab merge requests, pipelines, CI/CD, and repositories via the glab CLI |
Skills
| Skill | Description |
|---|---|
adversarial-code-review | Tiered adversarial review of a GitLab MR: Sonnet finds, then Opus and Fable refuters independently re-verify each blocking candidate before it is posted as an inline discussion in Conventional Comments format. Merge-gate use only — expensive. |
doc-coauthoring | Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. |
frontend-design | Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications. |
internal-comms | Write all kinds of internal communications using company formats: status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, and project updates. |
gather-requirements | Find the product decisions a vague or incomplete piece of work is missing, grounded in a codebase search. For a Jira or Linear issue, posts them as a comment that @mentions the creator (or whoever you name with --to) and assigns the issue to them. |
gitlab-workflow | Manage GitLab branches, commits, and merge requests following project conventions. Use when creating feature branches, committing changes, or creating merge requests. |
grill-me | Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. |
hello | Greet the user with a friendly welcome message. |
jira-engineering-ticket | Write structured Jira tickets for engineering implementation work. Use when turning requirements, decisions, or raw context into an actionable engineering deliverable. |
one-shot | Autonomously takes a feature prompt from idea to merge-ready MR with Jira tracking, GitLab MR, and code review — no human input required after kickoff. |
pm-discovery | Interrogate and refine requirements before producing any deliverable. Pairs with jira-engineering-ticket to build a clear, complete understanding of a piece of work first. |
raptor-flow-data-audit | Audits raptor-flow data in Snowflake to find live flows, trace how a validation or config bug spreads across products, and check repricing triggers, audience gating, and backend hook registration; hands the query off to cortex-code for execution. Explicit-invocation only. |
surface-jira-feedback | Surfaces actionable feedback buried in a Jira ticket's comment thread (QA bugs, design-review asks, open questions) into two regenerated sections of the ticket's description, split into in-scope polish vs. items that raise scope beyond the original acceptance criteria. |
ubiquitous-language | Author and look up a multi-stakeholder ubiquitous-language glossary across PM/Backend/Frontend/Ops lenses. Authoring builds, updates, or imports a glossary from the conversation, a local file, or Confluence; lookup silently aligns terminology turn-by-turn and corrects avoided aliases as you go. |
Hooks
On every session start the plugin fetches and installs the latest common rules bundle from the Odyssey rules server, verifying its checksum before extracting:
SessionStart → install-rules.sh common
Rules are written to .claude/rules/odyssey/common/ inside the current project directory.
Prerequisites
GitLab MCP requires the glab CLI to be installed and authenticated:
brew install glab # macOS
sudo apt install glab # Debian/Ubuntu
glab auth login
Slack MCP requires three environment variables:
export SLACK_BOT_TOKEN=xoxb-...
export SLACK_TEAM_ID=T...
export SLACK_CHANNEL_IDS=C...
Chrome DevTools MCP expects a Chrome instance listening on http://127.0.0.1:9222. Launch Chrome with remote debugging enabled:
google-chrome --remote-debugging-port=9222
# or on macOS:
open -a "Google Chrome" --args --remote-debugging-port=9222