omc-setup▌
yeachan-heo/oh-my-claudecode · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
This is the only command you need to learn. After running this, everything else is automatic.
OMC Setup
This is the only command you need to learn. After running this, everything else is automatic.
When this skill is invoked, immediately execute the workflow below. Do not only restate or summarize these instructions back to the user.
Note: All ~/.claude/... paths in this guide respect CLAUDE_CONFIG_DIR when that environment variable is set.
Best-Fit Use
Choose this setup flow when the user wants to install, refresh, or repair OMC itself.
- Marketplace/plugin install users should land here after
/plugin install oh-my-claudecode - npm users should land here after
npm i -g oh-my-claude-sisyphus@latest - local-dev and worktree users should land here after updating the checked-out repo and rerunning setup
Flag Parsing
Check for flags in the user's invocation:
--help→ Show Help Text (below) and stop--local→ Phase 1 only (target=local), then stop--global→ Phase 1 only (target=global), then stop--force→ Skip Pre-Setup Check, run full setup (Phase 1 → 2 → 3 → 4)- No flags → Run Pre-Setup Check, then full setup if needed
Help Text
When user runs with --help, display this and stop:
OMC Setup - Configure oh-my-claudecode
USAGE:
/oh-my-claudecode:omc-setup Run initial setup wizard (or update if already configured)
/oh-my-claudecode:omc-setup --local Configure local project (.claude/CLAUDE.md)
/oh-my-claudecode:omc-setup --global Configure global settings (~/.claude/CLAUDE.md)
/oh-my-claudecode:omc-setup --force Force full setup wizard even if already configured
/oh-my-claudecode:omc-setup --help Show this help
MODES:
Initial Setup (no flags)
- Interactive wizard for first-time setup
- Configures CLAUDE.md (local or global)
- Sets up HUD statusline
- Checks for updates
- Offers MCP server configuration
- Configures team mode defaults (agent count, type, model)
- If already configured, offers quick update option
Local Configuration (--local)
- Downloads fresh CLAUDE.md to ./.claude/
- Backs up existing CLAUDE.md to .claude/CLAUDE.md.backup.YYYY-MM-DD
- Project-specific settings
- Use this to update project config after OMC upgrades
Global Configuration (--global)
- Downloads fresh CLAUDE.md to ~/.claude/
- Backs up existing CLAUDE.md to ~/.claude/CLAUDE.md.backup.YYYY-MM-DD
- Default: explicitly overwrites ~/.claude/CLAUDE.md so plain `claude` also uses OMC
- Optional preserve mode keeps the user's base `CLAUDE.md` and installs OMC into `CLAUDE-omc.md` for `omc` launches
- Applies to all Claude Code sessions
- Cleans up legacy hooks
- Use this to update global config after OMC upgrades
Force Full Setup (--force)
- Bypasses the "already configured" check
- Runs the complete setup wizard from scratch
- Use when you want to reconfigure preferences
EXAMPLES:
/oh-my-claudecode:omc-setup # First time setup (or update CLAUDE.md if configured)
/oh-my-claudecode:omc-setup --local # Update this project
/oh-my-claudecode:omc-setup --global # Update all projects
/oh-my-claudecode:omc-setup --force # Re-run full setup wizard
For more info: https://github.com/Yeachan-Heo/oh-my-claudecode
Pre-Setup Check: Already Configured?
CRITICAL: Before doing anything else, check if setup has already been completed. This prevents users from having to re-run the full setup wizard after every update.
# Check if setup was already completed
CONFIG_FILE="${CLAUDE_CONFIG_DIR:-$HOME/.claude}/.omc-config.json"
if [ -f "$CONFIG_FILE" ]; then
SETUP_COMPLETED=$(jq -r '.setupCompleted // empty' "$CONFIG_FILE" 2>/dev/null)
SETUP_VERSION=$(jq -r '.setupVersion // empty' "$CONFIG_FILE" 2>/dev/null)
if [ -n "$SETUP_COMPLETED" ] && [ "$SETUP_COMPLETED" != "null" ]; then
echo "OMC setup was already completed on: $SETUP_COMPLETED"
[ -n "$SETUP_VERSION" ] && echo "Setup version: $SETUP_VERSION"
ALREADY_CONFIGURED="true"
fi
fi
If Already Configured (and no --force flag)
If ALREADY_CONFIGURED is true AND the user did NOT pass --force, --local, or --global flags:
Use AskUserQuestion to prompt:
Question: "OMC is already configured. What would you like to do?"
Options:
- Update CLAUDE.md only - Download latest CLAUDE.md without re-running full setup
- Run full setup again - Go through the complete setup wizard
- Cancel - Exit without changes
If user chooses "Update CLAUDE.md only":
- Detect if local (.claude/CLAUDE.md) or global (~/.claude/CLAUDE.md) config exists
- If local exists, run:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-claude-md.sh" local - If only global exists, run:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-claude-md.sh" global - Skip all other steps
- Report success and exit
If user chooses "Run full setup again":
- Continue with Resume Detection below
If user chooses "Cancel":
- Exit without any changes
Force Flag Override
If user passes --force flag, skip this check and proceed directly to setup.
Resume Detection
Before starting any phase, check for existing state:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-progress.sh" resume
If state exists (output is not "fresh"), use AskUserQuestion to prompt:
Question: "Found a previous setup session. Would you like to resume or start fresh?"
Options:
- Resume from step $LAST_STEP - Continue where you left off
- Start fresh - Begin from the beginning (clears saved state)
If user chooses "Start fresh":
bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-progress.sh" clear
Phase Execution
For --local or --global flags:
Read the file at ${CLAUDE_PLUGIN_ROOT}/skills/omc-setup/phases/01-install-claude-md.md and follow its instructions.
(The phase file handles early exit for flag mode.)
For full setup (default or --force):
Execute phases sequentially. For each phase, read the corresponding file and follow its instructions:
-
Phase 1 - Install CLAUDE.md: Read
${CLAUDE_PLUGIN_ROOT}/skills/omc-setup/phases/01-install-claude-md.mdand follow its instructions. -
Phase 2 - Environment Configuration: Read
${CLAUDE_PLUGIN_ROOT}/skills/omc-setup/phases/02-configure.mdand follow its instructions. Phase 2 must delegate HUD/statusLine setup to thehudskill; do not generate or patchstatusLinepaths inline here. -
Phase 3 - Integration Setup: Read
${CLAUDE_PLUGIN_ROOT}/skills/omc-setup/phases/03-integrations.mdand follow its instructions. -
Phase 4 - Completion: Read
${CLAUDE_PLUGIN_ROOT}/skills/omc-setup/phases/04-welcome.mdand follow its instructions.
Graceful Interrupt Handling
IMPORTANT: This setup process saves progress after each phase via ${CLAUDE_PLUGIN_ROOT}/scripts/setup-progress.sh. If interrupted (Ctrl+C or connection loss), the setup can resume from where it left off.
Keeping Up to Date
After installing oh-my-claudecode updates (via npm or plugin update):
Automatic: Just run /oh-my-claudecode:omc-setup - it will detect you've already configured and offer a quick "Update CLAUDE.md only" option that skips the full wizard.
Manual options:
/oh-my-claudecode:omc-setup --localto update project config only/oh-my-claudecode:omc-setup --globalto update global config only/oh-my-claudecode:omc-setup --forceto re-run the full wizard (reconfigure preferences)
This ensures you have the newest features and agent configurations without the token cost of repeating the full setup.
How to use omc-setup on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add omc-setup
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches omc-setup from GitHub repository yeachan-heo/oh-my-claudecode and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate omc-setup. Access the skill through slash commands (e.g., /omc-setup) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★47 reviews- ★★★★★Ganesh Mohane· Dec 20, 2024
We added omc-setup from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Hassan Zhang· Dec 16, 2024
Keeps context tight: omc-setup is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Evelyn Khan· Dec 12, 2024
Registry listing for omc-setup matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakshi Patil· Nov 11, 2024
Useful defaults in omc-setup — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Yusuf Park· Nov 7, 2024
omc-setup is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ava Singh· Nov 3, 2024
omc-setup reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Fatima Patel· Oct 26, 2024
Solid pick for teams standardizing on skills: omc-setup is focused, and the summary matches what you get after install.
- ★★★★★Hiroshi Jain· Oct 22, 2024
We added omc-setup from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chaitanya Patil· Oct 2, 2024
Registry listing for omc-setup matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Yuki Thomas· Sep 13, 2024
Keeps context tight: omc-setup is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 47