Host: Codex CLI — This skill was designed for Claude Code and adapted for Codex.
Cross-reference commands use installed skill names in Codex rather than /octo:* slash commands.
Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.
For host tool equivalents, see skills/blocks/codex-host-adapter.md.
Context Detection - Internal Skill
Purpose
This skill provides automatic context detection to determine whether the user is working in a Development context (code-focused) or Knowledge context (research/strategy-focused). This replaces the manual /octo:km toggle with intelligent auto-detection.
Detection Algorithm
When a workflow skill activates, detect context using these signals:
Step 1: Check for Explicit Override
If user has explicitly set mode via /octo:km on or /octo:km off, respect that setting.
# Check if knowledge mode is explicitly set
if [[ -f ~/.claude-octopus/config/knowledge-mode ]]; then
EXPLICIT_MODE=$(cat ~/.claude-octopus/config/knowledge-mode)
if [[ "$EXPLICIT_MODE" == "on" ]]; then
echo "knowledge"
exit 0
elif [[ "$EXPLICIT_MODE" == "off" ]]; then
echo "dev"
exit 0
fi
fi
# If "auto" or not set, proceed with auto-detection
Step 2: Analyze Prompt Content (Strongest Signal)
Knowledge Context Indicators (check prompt for these terms):
- Business/strategy: "market", "ROI", "stakeholders", "strategy", "business case", "competitive"
- Research: "literature", "synthesis", "academic", "papers", "research question"
- UX: "personas", "user research", "journey map", "pain points", "interviews"
- Deliverables: "presentation", "report", "PRD", "proposal", "executive summary"
Dev Context Indicators (check prompt for these terms):
- Technical: "API", "endpoint", "database", "function", "class", "module"
- Actions: "implement", "debug", "refactor", "test", "deploy", "build"
- Artifacts: "code", "tests", "migration", "schema", "controller"
Scoring:
- Count knowledge indicators in prompt
- Count dev indicators in prompt
- Higher count wins
- If tied, check project context (Step 3)
Step 3: Analyze Project Context (Secondary Signal)
Dev Project Indicators:
- Has
package.json, Cargo.toml, go.mod, pyproject.toml, pom.xml
- Has
src/, lib/, app/ directories with code files
- Recent files are
.ts, .js, .py, .go, .rs, .java
Knowledge Project Indicators:
- Has
docs/, research/, strategy/, reports/ directories
- Majority of files are
.md, .docx, .pdf, .pptx
- No code package managers detected
Step 4: Default Fallback
If signals are ambiguous or equal:
- In a git repo with code files → Default to Dev Context
- No code files detected → Default to Knowledge Context
Context Output Format
Return detected context as a structured object for use by workflow skills:
{
"context": "dev" | "knowledge",
"confidence": "high" | "medium" | "low",
"signals": {
"prompt_indicators": ["API", "endpoint", "database"],
"project_type": "node_typescript",
"explicit_override": false
}
}
How Workflow Skills Use Context
flow-discover (Research)
| Aspect |
Dev Context |
Knowledge Context |
| Research Focus |
Technical implementation, library comparison, code patterns |
Market analysis, academic synthesis, competitive research |
| Primary Agents |
Codex (implementation), Gemini (ecosystem) |
Gemini (analysis), research-synthesizer |
| Output Format |
Code examples, API comparisons, tech recommendations |
Reports, frameworks, strategic recommendations |
| Visual Banner |
🔍 [Dev] Discover Phase: Technical research |
🔍 [Knowledge] Discover Phase: Strategic research |
flow-develop (Build)
| Aspect |
Dev Context |
Knowledge Context |
| Build Focus |
Code generation, implementation, architecture |
PRDs, strategy docs, presentations |
| Primary Agents |
Codex (code), backend-architect, tdd-orchestrator |
product-writer, strategy-analyst, exec-communicator |
| Output Format |
Source files, tests, migrations |
Documents, frameworks, action plans |
| Visual Banner |
🛠️ [Dev] Develop Phase: Building code |
🛠️ [Knowledge] Develop Phase: Building deliverables |
flow-deliver (Review)
| Aspect |
Dev Context |
Knowledge Context |
| Review Focus |
Code quality, security, performance |
Document quality, argument strength, completeness |
| Primary Agents |
code-reviewer, security-auditor |
exec-communicator, strategy-analyst |
| Quality Gates |
OWASP, test coverage, maintainability |
Evidence quality, clarity, actionability |
| Visual Banner |
✅ [Dev] Deliver Phase: Code review |
✅ [Knowledge] Deliver Phase: Document review |
Visual Indicator Update
When context is detected, update the visual banner to show context:
Dev Context:
🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider research mode
🔍 [Dev] Discover Phase: Researching OAuth implementation patterns
Providers:
🔴 Codex CLI - Technical implementation analysis
🟡 Gemini CLI - Ecosystem and library comparison
🔵 Claude - Strategic synthesis
Knowledge Context:
🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider research mode
🔍 [Knowledge] Discover Phase: Researching market entry strategies
Providers:
🔴 Codex CLI - Data analysis and modeling
🟡 Gemini CLI - Market and competitive research
🔵 Claude - Strategic synthesis
Implementation in Workflow Skills
Each flow skill should:
- Before executing workflow, run context detection
- Show detected context in visual banner
- Adjust behavior based on context:
- Agent selection
- Prompt framing for external CLIs
- Output format expectations
- Quality gate criteria
Example Integration (Pseudocode)
When this skill activates:
1. **Detect context**
- Analyze user's prompt for knowledge vs dev indicators
- Check project type (code repo vs doc-heavy)
- Check for explicit override (~/.claude-octopus/config/knowledge-mode)
- Determine: "dev" or "knowledge" with confidence level
2. **Show context-aware banner**
🐙 CLAUDE OCTOPUS ACTIVATED - Multi-provider [research|implementation|validation] mode
[Phase Emoji] [Context] [Phase Name]: [Description]
Detected Context: [Dev|Knowledge] (confidence: [high|medium|low])
3. **Execute workflow with context-appropriate behavior**
- Frame prompts for external providers based on context
- Select appropriate synthesis approach
- Apply context-specific quality gates
Override Mechanism
Users can still explicitly set context when auto-detection is wrong:
# Force knowledge mode
/octo:km on
# Force dev mode
/octo:km off
# Return to auto-detection
/octo:km auto
When explicit override is set, context detection respects it until user resets to "auto".
Confidence Levels
- High: Strong signals in prompt AND project context agree
- Medium: Signals in prompt OR project context (not both)
- Low: Ambiguous signals, using fallback default
When confidence is "low", consider briefly mentioning the detected context to user:
"I detected this as a [dev/knowledge] task. If that's wrong, you can use /octo:km to override."
Testing Context Detection
To verify context detection is working:
- In a code repository, ask "octo research caching patterns" → Should detect Dev Context
- In same repo, ask "octo research market opportunities" → Should detect Knowledge Context
- With
/octo:km on set, ask "octo research API patterns" → Should use Knowledge Context (explicit override)
Proactive Skill Suggestions
When detecting the user's work stage, surface relevant command suggestions:
| Detected Context |
Suggestion |
| Brainstorming / exploring ideas |
Consider /octo:brainstorm for structured ideation |
| Reviewing a plan or strategy |
Consider /octo:plan for strategic planning |
| Debugging errors or failures |
Consider /octo:debug for systematic investigation |
| Writing or running tests |
Consider /octo:tdd for test-driven development |
| Code review before merge |
Use Claude-native /review for ordinary review; suggest /octo:review for multi-AI escalation |
| Ready to deploy or ship |
Consider /octo:deliver for quality-gated delivery |
| Researching a topic |
Consider /octo:research for multi-source synthesis |
| Working on security |
Use Claude-native /security-review for ordinary security review; suggest /octo:security for escalated OWASP or adversarial audit |
Suggestion Format
Suggestions should be non-intrusive, appended as a brief note:
💡 Tip: You appear to be debugging — `/octo:debug` provides systematic investigation with multi-AI support.
Persistent Opt-Out
- If user says "stop suggesting" or "no more tips": set
OCTO_PROACTIVE_SUGGESTIONS=off in .claude-octopus/preferences.json
- If user says "be proactive" or "turn on tips": set
OCTO_PROACTIVE_SUGGESTIONS=on
- Check preference at suggestion time — never suggest when opted out
- Respect current mode: dev mode suggestions differ from knowledge work suggestions
Re-Enable Suggestions
Users who previously opted out can re-enable suggestions at any time:
- Say "be proactive", "turn on tips", or "enable suggestions"
- Manually edit
~/.claude-octopus/preferences.json and set OCTO_PROACTIVE_SUGGESTIONS to on
- Default state (no preference set) is suggestions enabled
Detection Signals
Detect work stage from:
- Recent tool usage (many Bash calls = likely implementing/debugging)
- File types being edited (.test.ts = testing, .md = documentation)
- Error patterns in recent output (stack traces = debugging)
- Git state (uncommitted changes = implementing, clean tree = ready to review/ship)
1---2name: skill-context-detection3description: "Auto-detect work context (Dev vs Knowledge) — use to tailor workflows based on current task type"4metadata:5 source: https://skillmd.com/skills/concertonotes/skill-context-detection6---78> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.9> Cross-reference commands use installed skill names in Codex rather than `/octo:*` slash commands.10> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.11> For host tool equivalents, see `skills/blocks/codex-host-adapter.md`.121314# Context Detection - Internal Skill1516## Purpose1718This skill provides **automatic context detection** to determine whether the user is working in a **Development context** (code-focused) or **Knowledge context** (research/strategy-focused). This replaces the manual `/octo:km` toggle with intelligent auto-detection.1920## Detection Algorithm2122When a workflow skill activates, detect context using these signals:2324### Step 1: Check for Explicit Override2526If user has explicitly set mode via `/octo:km on` or `/octo:km off`, respect that setting.2728```bash29# Check if knowledge mode is explicitly set30if [[ -f ~/.claude-octopus/config/knowledge-mode ]]; then31 EXPLICIT_MODE=$(cat ~/.claude-octopus/config/knowledge-mode)32 if [[ "$EXPLICIT_MODE" == "on" ]]; then33 echo "knowledge"34 exit 035 elif [[ "$EXPLICIT_MODE" == "off" ]]; then36 echo "dev"37 exit 038 fi39fi40# If "auto" or not set, proceed with auto-detection41```4243### Step 2: Analyze Prompt Content (Strongest Signal)4445**Knowledge Context Indicators** (check prompt for these terms):46- Business/strategy: "market", "ROI", "stakeholders", "strategy", "business case", "competitive"47- Research: "literature", "synthesis", "academic", "papers", "research question"48- UX: "personas", "user research", "journey map", "pain points", "interviews"49- Deliverables: "presentation", "report", "PRD", "proposal", "executive summary"5051**Dev Context Indicators** (check prompt for these terms):52- Technical: "API", "endpoint", "database", "function", "class", "module"53- Actions: "implement", "debug", "refactor", "test", "deploy", "build"54- Artifacts: "code", "tests", "migration", "schema", "controller"5556**Scoring:**57- Count knowledge indicators in prompt58- Count dev indicators in prompt59- Higher count wins60- If tied, check project context (Step 3)6162### Step 3: Analyze Project Context (Secondary Signal)6364**Dev Project Indicators:**65- Has `package.json`, `Cargo.toml`, `go.mod`, `pyproject.toml`, `pom.xml`66- Has `src/`, `lib/`, `app/` directories with code files67- Recent files are `.ts`, `.js`, `.py`, `.go`, `.rs`, `.java`6869**Knowledge Project Indicators:**70- Has `docs/`, `research/`, `strategy/`, `reports/` directories71- Majority of files are `.md`, `.docx`, `.pdf`, `.pptx`72- No code package managers detected7374### Step 4: Default Fallback7576If signals are ambiguous or equal:77- In a git repo with code files → Default to **Dev Context**78- No code files detected → Default to **Knowledge Context**798081## Context Output Format8283Return detected context as a structured object for use by workflow skills:8485```json86{87 "context": "dev" | "knowledge",88 "confidence": "high" | "medium" | "low",89 "signals": {90 "prompt_indicators": ["API", "endpoint", "database"],91 "project_type": "node_typescript",92 "explicit_override": false93 }94}95```969798## How Workflow Skills Use Context99100### flow-discover (Research)101102| Aspect | Dev Context | Knowledge Context |103|--------|-------------|-------------------|104| **Research Focus** | Technical implementation, library comparison, code patterns | Market analysis, academic synthesis, competitive research |105| **Primary Agents** | Codex (implementation), Gemini (ecosystem) | Gemini (analysis), research-synthesizer |106| **Output Format** | Code examples, API comparisons, tech recommendations | Reports, frameworks, strategic recommendations |107| **Visual Banner** | `🔍 [Dev] Discover Phase: Technical research` | `🔍 [Knowledge] Discover Phase: Strategic research` |108109### flow-develop (Build)110111| Aspect | Dev Context | Knowledge Context |112|--------|-------------|-------------------|113| **Build Focus** | Code generation, implementation, architecture | PRDs, strategy docs, presentations |114| **Primary Agents** | Codex (code), backend-architect, tdd-orchestrator | product-writer, strategy-analyst, exec-communicator |115| **Output Format** | Source files, tests, migrations | Documents, frameworks, action plans |116| **Visual Banner** | `🛠️ [Dev] Develop Phase: Building code` | `🛠️ [Knowledge] Develop Phase: Building deliverables` |117118### flow-deliver (Review)119120| Aspect | Dev Context | Knowledge Context |121|--------|-------------|-------------------|122| **Review Focus** | Code quality, security, performance | Document quality, argument strength, completeness |123| **Primary Agents** | code-reviewer, security-auditor | exec-communicator, strategy-analyst |124| **Quality Gates** | OWASP, test coverage, maintainability | Evidence quality, clarity, actionability |125| **Visual Banner** | `✅ [Dev] Deliver Phase: Code review` | `✅ [Knowledge] Deliver Phase: Document review` |126127128## Visual Indicator Update129130When context is detected, update the visual banner to show context:131132**Dev Context:**133```134🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider research mode135🔍 [Dev] Discover Phase: Researching OAuth implementation patterns136137Providers:138🔴 Codex CLI - Technical implementation analysis139🟡 Gemini CLI - Ecosystem and library comparison140🔵 Claude - Strategic synthesis141```142143**Knowledge Context:**144```145🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider research mode146🔍 [Knowledge] Discover Phase: Researching market entry strategies147148Providers:149🔴 Codex CLI - Data analysis and modeling150🟡 Gemini CLI - Market and competitive research151🔵 Claude - Strategic synthesis152```153154155## Implementation in Workflow Skills156157Each flow skill should:1581591. **Before executing workflow**, run context detection1602. **Show detected context** in visual banner1613. **Adjust behavior** based on context:162 - Agent selection163 - Prompt framing for external CLIs164 - Output format expectations165 - Quality gate criteria166167### Example Integration (Pseudocode)168169```markdown170When this skill activates:1711721. **Detect context**173 - Analyze user's prompt for knowledge vs dev indicators174 - Check project type (code repo vs doc-heavy)175 - Check for explicit override (~/.claude-octopus/config/knowledge-mode)176 - Determine: "dev" or "knowledge" with confidence level1771782. **Show context-aware banner**179 ```180 🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider [research|implementation|validation] mode181 [Phase Emoji] [Context] [Phase Name]: [Description]182 183 Detected Context: [Dev|Knowledge] (confidence: [high|medium|low])184 ```1851863. **Execute workflow with context-appropriate behavior**187 - Frame prompts for external providers based on context188 - Select appropriate synthesis approach189 - Apply context-specific quality gates190```191192193## Override Mechanism194195Users can still explicitly set context when auto-detection is wrong:196197```bash198# Force knowledge mode199/octo:km on200201# Force dev mode 202/octo:km off203204# Return to auto-detection205/octo:km auto206```207208When explicit override is set, context detection respects it until user resets to "auto".209210211## Confidence Levels212213- **High**: Strong signals in prompt AND project context agree214- **Medium**: Signals in prompt OR project context (not both)215- **Low**: Ambiguous signals, using fallback default216217When confidence is "low", consider briefly mentioning the detected context to user:218> "I detected this as a [dev/knowledge] task. If that's wrong, you can use `/octo:km` to override."219220221## Testing Context Detection222223To verify context detection is working:2242251. In a code repository, ask "octo research caching patterns" → Should detect **Dev Context**2262. In same repo, ask "octo research market opportunities" → Should detect **Knowledge Context**2273. With `/octo:km on` set, ask "octo research API patterns" → Should use **Knowledge Context** (explicit override)228229230## Proactive Skill Suggestions231232When detecting the user's work stage, surface relevant command suggestions:233234| Detected Context | Suggestion |235|-----------------|------------|236| Brainstorming / exploring ideas | Consider `/octo:brainstorm` for structured ideation |237| Reviewing a plan or strategy | Consider `/octo:plan` for strategic planning |238| Debugging errors or failures | Consider `/octo:debug` for systematic investigation |239| Writing or running tests | Consider `/octo:tdd` for test-driven development |240| Code review before merge | Use Claude-native `/review` for ordinary review; suggest `/octo:review` for multi-AI escalation |241| Ready to deploy or ship | Consider `/octo:deliver` for quality-gated delivery |242| Researching a topic | Consider `/octo:research` for multi-source synthesis |243| Working on security | Use Claude-native `/security-review` for ordinary security review; suggest `/octo:security` for escalated OWASP or adversarial audit |244245### Suggestion Format246247Suggestions should be non-intrusive, appended as a brief note:248249```250💡 Tip: You appear to be debugging — `/octo:debug` provides systematic investigation with multi-AI support.251```252253### Persistent Opt-Out254255- If user says "stop suggesting" or "no more tips": set `OCTO_PROACTIVE_SUGGESTIONS=off` in `.claude-octopus/preferences.json`256- If user says "be proactive" or "turn on tips": set `OCTO_PROACTIVE_SUGGESTIONS=on`257- Check preference at suggestion time — never suggest when opted out258- Respect current mode: dev mode suggestions differ from knowledge work suggestions259260### Re-Enable Suggestions261262Users who previously opted out can re-enable suggestions at any time:263- Say "be proactive", "turn on tips", or "enable suggestions"264- Manually edit `~/.claude-octopus/preferences.json` and set `OCTO_PROACTIVE_SUGGESTIONS` to `on`265- Default state (no preference set) is suggestions enabled266267### Detection Signals268269Detect work stage from:270- Recent tool usage (many Bash calls = likely implementing/debugging)271- File types being edited (.test.ts = testing, .md = documentation)272- Error patterns in recent output (stack traces = debugging)273- Git state (uncommitted changes = implementing, clean tree = ready to review/ship)