// Use when coding standards, security patterns, or project conventions need to be discovered before implementation begins.
Install context files from registry. Use when user runs /install-context, says "install context", "setup context", or when context is missing and the user needs to get started.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when the task involves an external library or package and current API docs are needed before writing code.
Use before any implementation — understands the request, discovers project context, and proposes a concise plan for user approval before writing any code.
Use when starting any conversation — establishes how to find and use OAC skills, requiring Skill tool invocation BEFORE ANY response including clarifying questions, this is your secret weapon to best perform your tasks
Orchestrate multi-agent workflows for feature development using planning agents, context handoff, and stage management
| name | context-discovery |
| description | Use when coding standards, security patterns, or project conventions need to be discovered before implementation begins. |
| context | fork |
| agent | context-scout |
Discover project standards and patterns before implementing features. Context-scout resolves the context root using the OAC Context Discovery Protocol, then finds and ranks relevant files based on your request.
Announce at start: "I'm using the context-discovery skill to find relevant standards for [feature/task]."
Run the skill with your implementation topic:
/context-discovery [what you're implementing]
Examples:
/context-discovery JWT authentication/context-discovery React form validation/context-discovery database migration workflowRead EVERY file marked Critical Priority (paths returned by context-scout, relative to the resolved context root):
Read: {context_root}/core/standards/code-quality.md
Read: {context_root}/core/standards/security-patterns.md
These are mandatory—proceed only after loading.
Read files marked High Priority:
Read: {context_root}/core/workflows/approval-gates.md
These are strongly recommended for your implementation.
Read Medium Priority files for additional context:
Read: {context_root}/project-intelligence/architecture.md
These are optional but helpful.
When invoking subagents, pass discovered context files:
Invoke coder-agent:
Task: Implement JWT service
Context to load:
- .opencode/context/core/standards/code-quality.md
- .opencode/context/core/standards/security-patterns.md
Instructions: Follow functional patterns and security best practices.
"No context files found"
/install-context to download context first"Too many files returned"
"Which files do I load?"
Task: Discover context files for $ARGUMENTS
Follow navigation-driven discovery and return ranked recommendations.