oh-my-claude-sisyphus 3.3.6 → 3.3.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -48,13 +48,15 @@ That's it. Everything else is automatic.
48
48
  | Need research or exploration | Delegate to specialized agents |
49
49
  | Say "build me..." or use autopilot | Execute full autonomous workflow |
50
50
 
51
- **You don't need to learn any commands.** I detect what you need and activate the right behaviors.
51
+ **You don't need to memorize commands.** I detect intent from natural language and activate the right behaviors automatically.
52
52
 
53
53
  ---
54
54
 
55
- ## Magic Keywords (Power Users)
55
+ ## Magic Keywords (Optional Shortcuts)
56
56
 
57
- Want explicit control? Include these words anywhere in your message:
57
+ These are **optional shortcuts** for power users who want explicit control. Natural language works just fine - these keywords simply provide precision when you want it.
58
+
59
+ Include these words anywhere in your message:
58
60
 
59
61
  | Keyword | Effect |
60
62
  |---------|--------|
@@ -68,7 +70,7 @@ Want explicit control? Include these words anywhere in your message:
68
70
 
69
71
  ---
70
72
 
71
- ## Data Analysis & Research (v3.3.4)
73
+ ## Data Analysis & Research (v3.3.7)
72
74
 
73
75
  ### Scientist Agent Tiers
74
76
 
@@ -97,17 +99,17 @@ python_repl(action="execute", researchSessionID="analysis",
97
99
  code="print(df.describe())")
98
100
  ```
99
101
 
100
- ### /research Command (NEW)
102
+ ### /oh-my-claudecode:research Command (NEW)
101
103
 
102
104
  Orchestrate parallel scientist agents for comprehensive research workflows:
103
105
 
104
106
  ```
105
- /research <goal> # Standard research with checkpoints
106
- /research AUTO: <goal> # Fully autonomous until complete
107
- /research status # Check current session
108
- /research resume # Resume interrupted session
109
- /research list # List all sessions
110
- /research report <session-id> # Generate report for session
107
+ /oh-my-claudecode:research <goal> # Standard research with checkpoints
108
+ /oh-my-claudecode:research AUTO: <goal> # Fully autonomous until complete
109
+ /oh-my-claudecode:research status # Check current session
110
+ /oh-my-claudecode:research resume # Resume interrupted session
111
+ /oh-my-claudecode:research list # List all sessions
112
+ /oh-my-claudecode:research report <session-id> # Generate report for session
111
113
  ```
112
114
 
113
115
  **Research Protocol:**
@@ -136,14 +138,62 @@ I'll intelligently determine what to stop based on context.
136
138
 
137
139
  ---
138
140
 
141
+ ## MCP Server Configuration
142
+
143
+ Extend Claude Code with additional tools via Model Context Protocol (MCP) servers.
144
+
145
+ ```
146
+ /oh-my-claudecode:mcp-setup
147
+ ```
148
+
149
+ ### Supported MCP Servers
150
+
151
+ | Server | Description | API Key Required |
152
+ |--------|-------------|------------------|
153
+ | **Context7** | Documentation and code context from popular libraries | No |
154
+ | **Exa** | Enhanced web search (replaces built-in websearch) | Yes |
155
+ | **Filesystem** | Extended file system access | No |
156
+ | **GitHub** | GitHub API for issues, PRs, repos | Yes (PAT) |
157
+
158
+ ### Quick Setup
159
+
160
+ Run the setup command and follow the prompts:
161
+ ```
162
+ /oh-my-claudecode:mcp-setup
163
+ ```
164
+
165
+ Or configure manually in `~/.claude/settings.json`:
166
+ ```json
167
+ {
168
+ "mcpServers": {
169
+ "context7": {
170
+ "command": "npx",
171
+ "args": ["-y", "@context7/mcp"]
172
+ },
173
+ "exa": {
174
+ "command": "npx",
175
+ "args": ["-y", "@anthropic/exa-mcp-server"],
176
+ "env": {
177
+ "EXA_API_KEY": "your-key-here"
178
+ }
179
+ }
180
+ }
181
+ }
182
+ ```
183
+
184
+ After configuration, restart Claude Code for changes to take effect.
185
+
186
+ ---
187
+
139
188
  ## What's Under the Hood
140
189
 
141
190
  - **28 Specialized Agents** - architect, researcher, explore, designer, writer, vision, critic, analyst, executor, planner, qa-tester, scientist (with tier variants)
142
- - **30 Skills** - orchestrate, ultrawork, ralph, planner, deepsearch, deepinit, git-master, frontend-ui-ux, learner, research, and more
191
+ - **31 Skills** - orchestrate, ultrawork, ralph, planner, deepsearch, deepinit, git-master, frontend-ui-ux, learner, research, mcp-setup, and more
192
+ - **MCP Server Support** - Easy configuration of Context7, Exa, GitHub, and custom MCP servers
143
193
  - **Persistent Python REPL** - True variable persistence for data analysis
144
- - **Research Workflow** - Parallel scientist orchestration with `/research` command (new in 3.3.x)
194
+ - **Research Workflow** - Parallel scientist orchestration with `/oh-my-claudecode:research` command (new in 3.3.x)
145
195
  - **HUD Statusline** - Real-time visualization of orchestration state
146
- - **Learned Skills** - Extract reusable insights from sessions with `/learner`
196
+ - **Learned Skills** - Extract reusable insights from sessions with `/oh-my-claudecode:learner`
147
197
  - **Memory System** - Persistent context that survives compaction
148
198
 
149
199
  ---
@@ -175,9 +225,9 @@ Run `/oh-my-claudecode:hud setup` to configure display options.
175
225
  **Good news:** Your old commands still work!
176
226
 
177
227
  ```
178
- /ralph "task" → Still works (or just say "ralph: task")
179
- /ultrawork "task" → Still works (or just use "ulw" keyword)
180
- /planner "task" → Still works (or just say "plan this")
228
+ /oh-my-claudecode:ralph "task" → Still works (or just say "ralph: task")
229
+ /oh-my-claudecode:ultrawork "task" → Still works (or just use "ulw" keyword)
230
+ /oh-my-claudecode:planner "task" → Still works (or just say "plan this")
181
231
  ```
182
232
 
183
233
  The difference? You don't *need* them anymore. Everything auto-activates.
@@ -198,7 +248,9 @@ See the [Migration Guide](docs/MIGRATION.md) for details.
198
248
  ## Requirements
199
249
 
200
250
  - [Claude Code](https://docs.anthropic.com/claude-code) CLI
201
- - Anthropic API key
251
+ - One of:
252
+ - **Claude Max/Pro subscription** (recommended for individuals)
253
+ - **Anthropic API key** (for API-based usage)
202
254
 
203
255
  ---
204
256
 
package/agents/planner.md CHANGED
@@ -205,7 +205,7 @@ Include:
205
205
  | **Interview Mode** | Default state | Consult, research, discuss. NO plan generation. |
206
206
  | **Pre-Generation** | "Make it into a work plan" | Summon Metis → Ask final questions |
207
207
  | **Plan Generation** | After pre-generation complete | Generate plan, optionally loop through Momus |
208
- | **Handoff** | Plan saved | Tell user to run `/start-work` |
208
+ | **Handoff** | Plan saved | Tell user to run `/oh-my-claudecode:start-work` |
209
209
 
210
210
  ## Key Principles
211
211
 
@@ -213,7 +213,7 @@ Include:
213
213
  2. **Research-Backed Advice** - Use agents to provide evidence-based recommendations
214
214
  3. **User Controls Transition** - NEVER generate plan until explicitly requested
215
215
  4. **Metis Before Plan** - Always catch gaps before committing to plan
216
- 5. **Clear Handoff** - Always end with `/start-work` instruction
216
+ 5. **Clear Handoff** - Always end with `/oh-my-claudecode:start-work` instruction
217
217
 
218
218
  ---
219
219
 
@@ -244,7 +244,7 @@ After plan is saved, display:
244
244
  **Does this plan capture your intent?**
245
245
 
246
246
  Options:
247
- - "proceed" or "start work" - Begin implementation via /start-work
247
+ - "proceed" or "start work" - Begin implementation via /oh-my-claudecode:start-work
248
248
  - "adjust [X]" - Return to interview to modify specific aspect
249
249
  - "restart" - Discard plan and start fresh interview
250
250
  ```
@@ -253,7 +253,7 @@ Options:
253
253
 
254
254
  | User Response | Your Action |
255
255
  |---------------|-------------|
256
- | "proceed", "yes", "start", "looks good" | Tell user to run `/start-work {plan-name}` |
256
+ | "proceed", "yes", "start", "looks good" | Tell user to run `/oh-my-claudecode:start-work {plan-name}` |
257
257
  | "adjust X", "change X", "modify X" | Return to interview mode, ask about X |
258
258
  | "restart", "start over", "no" | Discard plan, return to Phase 1 |
259
259
  | Silence or unclear | Wait. Do NOT proceed without explicit confirmation |
@@ -276,7 +276,7 @@ Planner: [Saves plan to .omc/plans/new-api.md]
276
276
  Planner: [Displays confirmation summary]
277
277
  Planner: "Does this plan capture your intent?"
278
278
  User: "looks good, proceed"
279
- Planner: "Great! Run `/start-work new-api` to begin implementation."
279
+ Planner: "Great! Run `/oh-my-claudecode:start-work new-api` to begin implementation."
280
280
  ```
281
281
 
282
282
  ---
@@ -288,7 +288,7 @@ After user confirms, provide clear handoff:
288
288
  ```
289
289
  Your plan is ready for execution.
290
290
 
291
- Run: `/start-work {plan-name}`
291
+ Run: `/oh-my-claudecode:start-work {plan-name}`
292
292
 
293
293
  This will:
294
294
  1. Load the plan from `.omc/plans/{plan-name}.md`
@@ -296,4 +296,4 @@ This will:
296
296
  3. Track progress until completion
297
297
  ```
298
298
 
299
- **NEVER start implementation yourself. ALWAYS hand off to /start-work.**
299
+ **NEVER start implementation yourself. ALWAYS hand off to /oh-my-claudecode:start-work.**
@@ -792,7 +792,7 @@ Before marking any stage as `[STAGE:status:success]`:
792
792
  <Promise_Tags>
793
793
  ## Research Loop Control
794
794
 
795
- When invoked by `/research` skill, output these tags to communicate status:
795
+ When invoked by `/oh-my-claudecode:research` skill, output these tags to communicate status:
796
796
 
797
797
  | Tag | Meaning | When to Use |
798
798
  |-----|---------|-------------|
@@ -841,9 +841,9 @@ Created 15 new features, improved R² from 0.42 to 0.58
841
841
  Next: Test interaction terms and polynomial features
842
842
  ```
843
843
 
844
- ### Integration with /research Skill
844
+ ### Integration with /oh-my-claudecode:research Skill
845
845
 
846
- The `/research` skill orchestrates multi-stage research workflows. It reads these promise tags to:
846
+ The `/oh-my-claudecode:research` skill orchestrates multi-stage research workflows. It reads these promise tags to:
847
847
 
848
848
  1. **Route next steps**: `STAGE_COMPLETE` → proceed to next stage
849
849
  2. **Handle blockers**: `STAGE_BLOCKED` → invoke architect or escalate
@@ -33,9 +33,9 @@ After running this command, you are free to stop working. The persistent mode ho
33
33
 
34
34
  ## Note on Linked Modes
35
35
 
36
- Since v3.0, Ralph automatically activates Ultrawork for parallel execution. When you cancel Ralph, the linked Ultrawork is also cancelled. If you started Ultrawork separately (not via Ralph), use `/cancel-ultrawork` to cancel it independently.
36
+ Since v3.0, Ralph automatically activates Ultrawork for parallel execution. When you cancel Ralph, the linked Ultrawork is also cancelled. If you started Ultrawork separately (not via Ralph), use `/oh-my-claudecode:cancel-ultrawork` to cancel it independently.
37
37
 
38
38
  ## To Start Fresh
39
39
 
40
- - `/ralph "task"` - Start ralph with ultrawork (default)
41
- - `/ultrawork "task"` - Start ultrawork only (standalone)
40
+ - `/oh-my-claudecode:ralph "task"` - Start ralph with ultrawork (default)
41
+ - `/oh-my-claudecode:ultrawork "task"` - Start ultrawork only (standalone)
@@ -20,8 +20,8 @@ After running this command, the QA cycling will stop.
20
20
 
21
21
  ## To Start Fresh
22
22
 
23
- - `/ultraqa --tests` - Run until all tests pass
24
- - `/ultraqa --build` - Run until build succeeds
25
- - `/ultraqa --lint` - Run until no lint errors
26
- - `/ultraqa --typecheck` - Run until no type errors
27
- - `/ultraqa --custom "pattern"` - Run until pattern matches
23
+ - `/oh-my-claudecode:ultraqa --tests` - Run until all tests pass
24
+ - `/oh-my-claudecode:ultraqa --build` - Run until build succeeds
25
+ - `/oh-my-claudecode:ultraqa --lint` - Run until no lint errors
26
+ - `/oh-my-claudecode:ultraqa --typecheck` - Run until no type errors
27
+ - `/oh-my-claudecode:ultraqa --custom "pattern"` - Run until pattern matches
@@ -16,7 +16,7 @@ The Ultrawork mode has been cancelled. Clearing state files.
16
16
  cat .omc/ultrawork-state.json 2>/dev/null | jq -r '.linked_to_ralph // false'
17
17
  ```
18
18
 
19
- **If linked_to_ralph is true**: Use `/cancel-ralph` instead to cancel both Ralph and its linked Ultrawork.
19
+ **If linked_to_ralph is true**: Use `/oh-my-claudecode:cancel-ralph` instead to cancel both Ralph and its linked Ultrawork.
20
20
 
21
21
  **Otherwise**, execute this command to cancel Ultrawork:
22
22
 
@@ -31,10 +31,10 @@ After running this command, ultrawork mode will be deactivated and the HUD will
31
31
  ## Note on Linked Modes
32
32
 
33
33
  Since v3.0, Ralph automatically activates Ultrawork. If you see `linked_to_ralph: true` in the ultrawork state, it means Ultrawork was auto-activated by Ralph. In this case:
34
- - Use `/cancel-ralph` to cancel both modes
34
+ - Use `/oh-my-claudecode:cancel-ralph` to cancel both modes
35
35
  - If you only cancel ultrawork, Ralph will continue but without parallel execution benefits
36
36
 
37
37
  ## To Start Fresh
38
38
 
39
- - `/ultrawork "task"` - Start ultrawork only (standalone)
40
- - `/ralph "task"` - Start ralph with ultrawork (default)
39
+ - `/oh-my-claudecode:ultrawork "task"` - Start ultrawork only (standalone)
40
+ - `/oh-my-claudecode:ralph "task"` - Start ralph with ultrawork (default)
package/commands/hud.md CHANGED
@@ -10,12 +10,12 @@ Configure the OMC HUD (Heads-Up Display) for the statusline.
10
10
 
11
11
  | Command | Description |
12
12
  |---------|-------------|
13
- | `/hud` | Show current HUD status (auto-setup if needed) |
14
- | `/hud setup` | Install/repair HUD statusline |
15
- | `/hud minimal` | Switch to minimal display |
16
- | `/hud focused` | Switch to focused display (default) |
17
- | `/hud full` | Switch to full display |
18
- | `/hud status` | Show detailed HUD status |
13
+ | `/oh-my-claudecode:hud` | Show current HUD status (auto-setup if needed) |
14
+ | `/oh-my-claudecode:hud setup` | Install/repair HUD statusline |
15
+ | `/oh-my-claudecode:hud minimal` | Switch to minimal display |
16
+ | `/oh-my-claudecode:hud focused` | Switch to focused display (default) |
17
+ | `/oh-my-claudecode:hud full` | Switch to full display |
18
+ | `/oh-my-claudecode:hud status` | Show detailed HUD status |
19
19
 
20
20
  ## Auto-Setup
21
21
 
@@ -222,9 +222,9 @@ You can manually edit the config file:
222
222
  ## Troubleshooting
223
223
 
224
224
  If the HUD is not showing:
225
- 1. Run `/hud setup` to auto-install and configure
225
+ 1. Run `/oh-my-claudecode:hud setup` to auto-install and configure
226
226
  2. Restart Claude Code after setup completes
227
- 3. If still not working, run `/doctor` for full diagnostics
227
+ 3. If still not working, run `/oh-my-claudecode:doctor` for full diagnostics
228
228
 
229
229
  Manual verification:
230
230
  - HUD script: `~/.claude/hud/omc-hud.mjs`
@@ -130,5 +130,5 @@ If code helps, show it - but as illustration of the principle, not copy-paste ma
130
130
 
131
131
  ## Related Commands
132
132
 
133
- - /note - Save quick notes that survive compaction (less formal than skills)
134
- - /ralph - Start a development loop with learning capture
133
+ - /oh-my-claudecode:note - Save quick notes that survive compaction (less formal than skills)
134
+ - /oh-my-claudecode:ralph - Start a development loop with learning capture
@@ -0,0 +1,194 @@
1
+ ---
2
+ description: Configure popular MCP servers for enhanced agent capabilities
3
+ ---
4
+
5
+ # MCP Setup
6
+
7
+ Configure Model Context Protocol (MCP) servers to extend Claude Code's capabilities with external tools like web search, file system access, and GitHub integration.
8
+
9
+ ## Overview
10
+
11
+ MCP servers provide additional tools that Claude Code agents can use. This skill helps you configure popular MCP servers in your `~/.claude/settings.json`.
12
+
13
+ ## Step 1: Show Available MCP Servers
14
+
15
+ Present the user with available MCP server options using AskUserQuestion:
16
+
17
+ **Question:** "Which MCP server would you like to configure?"
18
+
19
+ **Options:**
20
+ 1. **Context7** - Documentation and code context from popular libraries
21
+ 2. **Exa Web Search** - Enhanced web search (replaces built-in websearch)
22
+ 3. **Filesystem** - Extended file system access with additional capabilities
23
+ 4. **GitHub** - GitHub API integration for issues, PRs, and repository management
24
+ 5. **All of the above** - Configure all recommended MCP servers
25
+ 6. **Custom** - Add a custom MCP server
26
+
27
+ ## Step 2: Gather Required Information
28
+
29
+ ### For Context7:
30
+ No API key required. Ready to use immediately.
31
+
32
+ ### For Exa Web Search:
33
+ Ask for API key:
34
+ ```
35
+ Do you have an Exa API key?
36
+ - Get one at: https://exa.ai
37
+ - Enter your API key, or type 'skip' to configure later
38
+ ```
39
+
40
+ ### For Filesystem:
41
+ Ask for allowed directories:
42
+ ```
43
+ Which directories should the filesystem MCP have access to?
44
+ Default: Current working directory
45
+ Enter comma-separated paths, or press Enter for default
46
+ ```
47
+
48
+ ### For GitHub:
49
+ Ask for token:
50
+ ```
51
+ Do you have a GitHub Personal Access Token?
52
+ - Create one at: https://github.com/settings/tokens
53
+ - Recommended scopes: repo, read:org
54
+ - Enter your token, or type 'skip' to configure later
55
+ ```
56
+
57
+ ## Step 3: Update settings.json
58
+
59
+ Read the current `~/.claude/settings.json` and add/update the `mcpServers` section.
60
+
61
+ ### Context7 Configuration:
62
+ ```json
63
+ {
64
+ "mcpServers": {
65
+ "context7": {
66
+ "command": "npx",
67
+ "args": ["-y", "@context7/mcp"]
68
+ }
69
+ }
70
+ }
71
+ ```
72
+
73
+ ### Exa Web Search Configuration:
74
+ ```json
75
+ {
76
+ "mcpServers": {
77
+ "exa": {
78
+ "command": "npx",
79
+ "args": ["-y", "@anthropic/exa-mcp-server"],
80
+ "env": {
81
+ "EXA_API_KEY": "<user-provided-key>"
82
+ }
83
+ }
84
+ }
85
+ }
86
+ ```
87
+
88
+ ### Filesystem Configuration:
89
+ ```json
90
+ {
91
+ "mcpServers": {
92
+ "filesystem": {
93
+ "command": "npx",
94
+ "args": ["-y", "@anthropic/mcp-server-filesystem", "<allowed-directories>"]
95
+ }
96
+ }
97
+ }
98
+ ```
99
+
100
+ ### GitHub Configuration:
101
+ ```json
102
+ {
103
+ "mcpServers": {
104
+ "github": {
105
+ "command": "npx",
106
+ "args": ["-y", "@anthropic/github-mcp-server"],
107
+ "env": {
108
+ "GITHUB_TOKEN": "<user-provided-token>"
109
+ }
110
+ }
111
+ }
112
+ }
113
+ ```
114
+
115
+ ## Step 4: Merge Configuration
116
+
117
+ When updating settings.json:
118
+
119
+ 1. Read existing file: `~/.claude/settings.json`
120
+ 2. Parse as JSON (handle comments with jsonc-parser if needed)
121
+ 3. Merge new `mcpServers` entries with existing ones (don't overwrite user's other MCP servers)
122
+ 4. Write back to file with proper formatting
123
+
124
+ ```bash
125
+ # Backup existing settings first
126
+ cp ~/.claude/settings.json ~/.claude/settings.json.bak 2>/dev/null || true
127
+ ```
128
+
129
+ Use the Edit tool or Write tool to update the settings file, preserving existing configuration.
130
+
131
+ ## Step 5: Verify Installation
132
+
133
+ After configuration, verify the MCP servers are properly set up:
134
+
135
+ ```bash
136
+ # Check if settings.json has mcpServers
137
+ grep -q "mcpServers" ~/.claude/settings.json && echo "MCP servers configured" || echo "Configuration may have failed"
138
+
139
+ # List configured servers
140
+ node -e "const s = require('$HOME/.claude/settings.json'); console.log('Configured MCP servers:', Object.keys(s.mcpServers || {}).join(', ') || 'none')"
141
+ ```
142
+
143
+ ## Step 6: Show Completion Message
144
+
145
+ ```
146
+ MCP Server Configuration Complete!
147
+
148
+ CONFIGURED SERVERS:
149
+ [List the servers that were configured]
150
+
151
+ NEXT STEPS:
152
+ 1. Restart Claude Code for changes to take effect
153
+ 2. The configured MCP tools will be available to all agents
154
+
155
+ USAGE TIPS:
156
+ - Context7: Ask about library documentation (e.g., "How do I use React hooks?")
157
+ - Exa: Use for web searches (e.g., "Search the web for latest TypeScript features")
158
+ - Filesystem: Extended file operations beyond the working directory
159
+ - GitHub: Interact with GitHub repos, issues, and PRs
160
+
161
+ TROUBLESHOOTING:
162
+ - If MCP servers don't appear, check ~/.claude/settings.json for syntax errors
163
+ - Ensure you have Node.js 18+ installed for npx commands
164
+ - Run /oh-my-claudecode:doctor to diagnose issues
165
+
166
+ To add more MCP servers later, run: /oh-my-claudecode:mcp-setup
167
+ ```
168
+
169
+ ## Custom MCP Server
170
+
171
+ If user selects "Custom":
172
+
173
+ Ask for:
174
+ 1. Server name (identifier)
175
+ 2. Command to run (e.g., `npx`, `node`, path to executable)
176
+ 3. Arguments (comma-separated)
177
+ 4. Environment variables (optional, key=value pairs)
178
+
179
+ Then add to mcpServers section accordingly.
180
+
181
+ ## Common Issues
182
+
183
+ ### MCP Server Not Loading
184
+ - Ensure Node.js 18+ is installed
185
+ - Check that npx is available in PATH
186
+ - Verify no JSON syntax errors in settings.json
187
+
188
+ ### API Key Issues
189
+ - Exa: Verify key at https://dashboard.exa.ai
190
+ - GitHub: Ensure token has required scopes
191
+
192
+ ### Agents Still Using Built-in Tools
193
+ - Restart Claude Code after configuration
194
+ - The built-in websearch will be deprioritized when exa is configured
package/commands/note.md CHANGED
@@ -10,12 +10,12 @@ Save important context to `.omc/notepad.md` that survives conversation compactio
10
10
 
11
11
  | Command | Action |
12
12
  |---------|--------|
13
- | `/note <content>` | Add to Working Memory with timestamp |
14
- | `/note --priority <content>` | Add to Priority Context (always loaded) |
15
- | `/note --manual <content>` | Add to MANUAL section (never pruned) |
16
- | `/note --show` | Display current notepad contents |
17
- | `/note --prune` | Remove entries older than 7 days |
18
- | `/note --clear` | Clear Working Memory (keep Priority + MANUAL) |
13
+ | `/oh-my-claudecode:note <content>` | Add to Working Memory with timestamp |
14
+ | `/oh-my-claudecode:note --priority <content>` | Add to Priority Context (always loaded) |
15
+ | `/oh-my-claudecode:note --manual <content>` | Add to MANUAL section (never pruned) |
16
+ | `/oh-my-claudecode:note --show` | Display current notepad contents |
17
+ | `/oh-my-claudecode:note --prune` | Remove entries older than 7 days |
18
+ | `/oh-my-claudecode:note --clear` | Clear Working Memory (keep Priority + MANUAL) |
19
19
 
20
20
  ## Sections
21
21
 
@@ -37,11 +37,11 @@ Save important context to `.omc/notepad.md` that survives conversation compactio
37
37
  ## Examples
38
38
 
39
39
  ```
40
- /note Found auth bug in UserContext - missing useEffect dependency
41
- /note --priority Project uses TypeScript strict mode, all files in src/
42
- /note --manual Contact: api-team@company.com for backend questions
43
- /note --show
44
- /note --prune
40
+ /oh-my-claudecode:note Found auth bug in UserContext - missing useEffect dependency
41
+ /oh-my-claudecode:note --priority Project uses TypeScript strict mode, all files in src/
42
+ /oh-my-claudecode:note --manual Contact: api-team@company.com for backend questions
43
+ /oh-my-claudecode:note --show
44
+ /oh-my-claudecode:note --prune
45
45
  ```
46
46
 
47
47
  ## Behavior
@@ -54,7 +54,20 @@ This will:
54
54
  grep -q "oh-my-claudecode" ~/.claude/settings.json && echo "Plugin verified" || echo "Plugin NOT found - run: claude /install-plugin oh-my-claudecode"
55
55
  ```
56
56
 
57
- ## Step 5: Detect Upgrade from 2.x
57
+ ## Step 5: Offer MCP Server Configuration
58
+
59
+ MCP servers extend Claude Code with additional tools (web search, GitHub, etc.).
60
+
61
+ Ask user: "Would you like to configure MCP servers for enhanced capabilities? (Context7, Exa search, GitHub, etc.)"
62
+
63
+ If yes, invoke the mcp-setup skill:
64
+ ```
65
+ /oh-my-claudecode:mcp-setup
66
+ ```
67
+
68
+ If no, skip to next step.
69
+
70
+ ## Step 6: Detect Upgrade from 2.x
58
71
 
59
72
  Check if user has existing configuration:
60
73
  ```bash
@@ -64,7 +77,7 @@ ls ~/.claude/commands/ralph-loop.md 2>/dev/null || ls ~/.claude/commands/ultrawo
64
77
 
65
78
  If found, this is an upgrade from 2.x.
66
79
 
67
- ## Step 6: Show Welcome Message
80
+ ## Step 7: Show Welcome Message
68
81
 
69
82
  ### For New Users:
70
83
 
@@ -91,6 +104,9 @@ Just include these words naturally in your request:
91
104
 
92
105
  Combine them: "ralph ulw: migrate the database"
93
106
 
107
+ MCP SERVERS:
108
+ Run /oh-my-claudecode:mcp-setup to add tools like web search, GitHub, etc.
109
+
94
110
  HUD STATUSLINE:
95
111
  The status bar now shows OMC state. Restart Claude Code to see it.
96
112
 
@@ -53,7 +53,7 @@ Started: [ISO timestamp]
53
53
  3. **Independent stories**: Minimize dependencies between stories
54
54
  4. **Priority order**: Foundational work (DB, types) before UI
55
55
 
56
- After creating files, report summary and suggest running `/ralph-loop` to start.
56
+ After creating files, report summary and suggest running `/oh-my-claudecode:ralph-loop` to start.
57
57
 
58
58
  Task to break down:
59
59
  {{ARGUMENTS}}