contexts

Auto-routing context gathering classifies input requests as codebase-oriented, doc-oriented, or both, then dispatches to the appropriate workflow. This targets context collection and accelerates safer coding decisions for architecture discussions or refactoring.

Yes, context classification supports both codebase and documentation workflows simultaneously. It auto-detects the input type and can dispatch to both workflows concurrently, ensuring comprehensive context gathering for complex feature scoping.

When context routing encounters ambiguous pre-implementation requests, it triggers a fallback AskUserQuestion gate. This prompts the user for clarification before proceeding, ensuring the context gathering workflow matches the actual intent.

Auto-detection for codebase versus documentation context works by classifying the input request and outputting a detected acknowledgement. It then routes the inquiry to code-ref, doc-ref, or both workflows based on the classified orientation.

No dependencies are required to classify context for architecture discussions. The classification and routing mechanism operates independently, evaluating input requests to dispatch to codebase or doc workflows without external components.

Use automated context routing for refactoring planning when you need targeted context gathering before implementation. It is applicable to any pre-implementation task where understanding the codebase or documentation context is required for safer decisions.