agent-doc-discipline
Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before…
Invoke parallel document-specialist agents for external web searches and documentation lookup
$ npx -y skills add Yeachan-Heo/oh-my-claudecode --skill external-context --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/external-contextContext preview
The summary Claude sees to decide when to auto-load this skill.
Invoke parallel document-specialist agents for external web searches and documentation lookup
name: external-context description: Invoke parallel document-specialist agents for external web searches and documentation lookup argument-hint: <search query or topic> level: 4
Fetch external documentation, references, and context for a query. Decomposes into 2-5 facets and spawns parallel document-specialist Claude agents.
/oh-my-claudecode:external-context <topic or question>
/oh-my-claudecode:external-context What are the best practices for JWT token rotation in Node.js? /oh-my-claudecode:external-context Compare Prisma vs Drizzle ORM for PostgreSQL /oh-my-claudecode:external-context Latest React Server Components patterns and conventions
Given a query, decompose into 2-5 independent search facets:
## Search Decomposition **Query:** <original query> ### Facet 1: <facet-name> - **Search focus:** What to search for - **Sources:** Official docs, GitHub, blogs, etc. ### Facet 2: <facet-name> ...
Fire independent facets in parallel via Task tool:
Task(subagent_type="oh-my-claudecode:document-specialist", model="sonnet", prompt="Search for: <facet 1 description>. Use WebSearch and WebFetch to find official documentation and examples. Cite all sources with URLs.") Task(subagent_type="oh-my-claudecode:document-specialist", model="sonnet", prompt="Search for: <facet 2 description>. Use WebSearch and WebFetch to find official documentation and examples. Cite all sources with URLs.")
Maximum 5 parallel document-specialist agents.
Present synthesized results in this format:
## External Context: <query> ### Key Findings 1. **<finding>** - Source: [title](url) 2. **<finding>** - Source: [title](url) ### Detailed Results #### Facet 1: <name> <aggregated findings with citations> #### Facet 2: <name> <aggregated findings with citations> ### Sources - [Source 1](url) - [Source 2](url)
For Codex users: Check out oh-my-codex — the same orchestration experience for OpenAI Codex CLI. Liked OmC but found it a bit overkill? Try gajae-code.
Repo: Yeachan-Heo/oh-my-claudecode
Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before…
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then…
Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior