legion-oracle

Research institutional knowledge before escalating questions to users. Check docs/solutions/ and codebase patterns before asking humans.

SKILL.md

GitHub

Legion Oracle

Research institutional knowledge before escalating questions to users.

Core Principle

Check docs/solutions/ first. This codebase captures learnings from past work.

When to Use

digraph oracle_decision {
    "About to ask user a question?" [shape=diamond];
    "Is it a preference/requirement?" [shape=diamond];
    "Might be documented?" [shape=diamond];
    "Ask user directly" [shape=box];
    "Use oracle" [shape=box];

    "About to ask user a question?" -> "Is it a preference/requirement?" [label="yes"];
    "About to ask user a question?" -> "Ask user directly" [label="no - not asking"];
    "Is it a preference/requirement?" -> "Ask user directly" [label="yes"];
    "Is it a preference/requirement?" -> "Might be documented?" [label="no"];
    "Might be documented?" -> "Use oracle" [label="yes"];
    "Might be documented?" -> "Ask user directly" [label="no"];
}

Use oracle for: patterns, conventions, solved problems, technical approaches

Ask directly for: preferences, requirements, scope decisions, human judgment

Research Strategy

If the deployment instructions name a librarian (or oracle) role, publish your question to notifications.role.<name> with expects_reply: required and wait for the reply before researching yourself. Then run steps 1-2 (parallel OK), and 3-4 if needed, with tools a Legion pane actually has: read, grep, web_search, and task(agent="scout") (fast read-only codebase search) or task(agent="oracle") (deeper read-only analysis when the answer needs judgment across many files). Do not name any other agent.

Step Tool Query
1. Institutional learnings grep then read over docs/solutions/ (front-matter tags, then the body) [question]'s keywords
2. Codebase patterns task(agent="scout"); task(agent="oracle") when judgment across many files is needed Find how [module] handles [topic]
3. Framework docs read the library's documentation URL [library] [topic]
4. External practices web_search, then read the primary source Current best practices for [topic]

Before relying on a step 1 hit, also search for supersedes: docs/solutions/<its-path> and Extends docs/solutions/<its-path> naming it: a newer file may extend or supersede what you found, and Legion runs no pass that reconciles these links, so following them is the only way to know the hit is still current.

Output

Found: Answer with source (file:line or URL)

Not found: "Checked docs/solutions/ and codebase - no relevant learnings found" → search externally OR escalate to user

Example

Question: How should I paginate a GraphQL connection?

grep pagination docs/solutions/   → no matches
task(agent="scout")               → packages/daemon/src/state/fetch.ts loops on
                                    pageInfo.hasNextPage / endCursor (contextsPage)

Answer: cursor-based, per the `while (page.hasNextPage)` loop in packages/daemon/src/state/fetch.ts