skill-context-detection

# 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. ```bash # 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",...