omnilearn-workflow 1.0.1 → 1.0.3

package/commands/omnilearn-refine.md

@@ -43,12 +43,43 @@ Both scenarios follow the same core flow: research → analyze → produce struc
         └── runs/
 ```
 
+## Current Date Context
+
+```bash
+CURRENT_DATE=$(date +%Y-%m-%d)
+CURRENT_YEAR=$(date +%Y)
+```
+
+**Every subagent that does research or content generation MUST receive the current date and be told to prioritize current information over deprecated or outdated resources.**
+
+## MCP Tool Call Semantics (CRITICAL — Subagents Frequently Get This Wrong)
+
+All subagents that use MCP tools MUST follow these exact calling conventions:
+
+### `context7_resolve-library-id` + `context7_query-docs`
+1. **ALWAYS call `context7_resolve-library-id` FIRST** with the library name to get the correct library ID.
+2. Use the returned library ID (format: `/org/package`) as the `libraryId` parameter in `context7_query-docs`.
+3. Do NOT guess or hardcode library IDs.
+4. Max 3 calls per question.
+
+### `google_search` / `websearch_web_search_exa`
+- Use specific, well-formed queries — not keywords, but what you want to find.
+- Good: `"best practices for error handling in Rust 2024"`
+- Bad: `"Rust error handling"`
+- Pass the `query` parameter as a string, not an object.
+
+### General Rules
+- Match tool call parameter names EXACTLY as specified in the tool definitions.
+- Do NOT wrap string parameters in objects.
+- Do NOT nest tool calls unless required by the API.
+- If a tool call fails, check parameter names and types before retrying.
+
 ## MANDATORY TOOLS
 
 | Tool | When | Why |
 |------|------|-----|
 | `google_search` / `websearch_web_search_exa` | Research | Topic research, answer questions, validate changes |
-| `context7_query_docs` | Tech topics | Official documentation for precise answers |
+| `context7_resolve-library-id` + `context7_query-docs` | Tech topics | Official documentation for precise answers — MUST call resolve first |
 | `task(category="unspecified-high", background)` | Heavy work | Research, analysis, topic updates |
 | `read`, `write`, `edit`, `bash`, `grep`, `glob` | All phases | File operations |
 
@@ -131,7 +162,7 @@ task(category="unspecified-high", run_in_background=false, prompt="
 1. TASK: Create a focused micro-exercise that tests the user's understanding of '{concept}' in '{skill}'. The user is confused about: '{user_request}'.
 2. EXPECTED OUTCOME: A self-contained micro-exercise (5-15 min) that isolates the specific concept and lets the user figure it out by coding/building.
 
-3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_resolve-library-id, context7_query_docs, read, write
+3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_resolve-library-id, context7_query-docs, read, write
 
 4. MUST DO:
    - Read the current topic-roadmap.md to understand what's been covered: {TOPIC_ROADMAP}
@@ -244,7 +275,7 @@ task(category="unspecified-high", run_in_background=true, prompt="
 1. TASK: Research online to find better ways to structure and teach '{topic}' in '{skill}'.
 2. EXPECTED OUTCOME: A research document with web-sourced findings about best practices for teaching/learning this topic.
 
-3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_resolve-library-id, context7_query_docs, read, write
+3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_resolve-library-id, context7_query-docs, read, write
 
 4. MUST DO:
    - Analyze the user's refinement request: '{user_request}'

package/commands/omnilearn-roadmap-edit.md

@@ -12,6 +12,37 @@ description: Edit an existing learning roadmap with full research-backed revisio
 /omnilearn-roadmap-edit Python I want to add web scraping and automation
 ```
 
+## Current Date Context
+
+```bash
+CURRENT_DATE=$(date +%Y-%m-%d)
+CURRENT_YEAR=$(date +%Y)
+```
+
+**All subagents that do research or content generation MUST receive the current date and prioritize current information over deprecated or outdated resources.**
+
+## MCP Tool Call Semantics (CRITICAL — Subagents Frequently Get This Wrong)
+
+All subagents that use MCP tools MUST follow these exact calling conventions:
+
+### `context7_resolve-library-id` + `context7_query-docs`
+1. **ALWAYS call `context7_resolve-library-id` FIRST** with the library name to get the correct library ID.
+2. Use the returned library ID (format: `/org/package`) as the `libraryId` parameter in `context7_query-docs`.
+3. Do NOT guess or hardcode library IDs.
+4. Max 3 calls per question.
+
+### `google_search` / `websearch_web_search_exa`
+- Use specific, well-formed queries — not keywords, but describe the ideal page.
+- Good: `"current best practices for REST API design 2025"`
+- Bad: `"REST API"`
+- Pass `query` as a plain string, not wrapped in an object.
+
+### General Rules
+- Match tool call parameter names EXACTLY as defined in the tool schema.
+- Do NOT wrap string parameters in extra objects or arrays.
+- Do NOT nest tool calls unless the API explicitly requires it.
+- If a tool call fails, verify parameter names match before retrying.
+
 ## Core Behavior
 
 This command performs the same rigorous research-backed process as `/omnilearn-roadmap`, but operates on an EXISTING roadmap. It:
@@ -226,9 +257,10 @@ task(category="unspecified-high", run_in_background=true, prompt="
 1. TASK: Research online to validate and inform the user's requested roadmap changes for {skill}.
 2. EXPECTED OUTCOME: A research document with web-sourced findings about the topics the user wants to add/modify.
 
-3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_resolve-library-id, context7_query_docs, read, write
+3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_resolve-library-id, context7_query-docs, read, write
 
 4. MUST DO:
+   - **CURRENT DATE: {CURRENT_DATE}** — ONLY research current information. Check for deprecation warnings. Prioritize resources from the last 1-2 years. Prefer latest stable versions of any library/framework/tool.
    - Analyze the user's change request: '{user_change_request}'
    - Use google_search / websearch_web_search_exa to research:
      * The specific topics/areas the user wants to add or modify

package/commands/omnilearn-roadmap.md

@@ -89,6 +89,37 @@ echo "Using learning directory: $LEARNING_DIR"
 
 All subsequent paths in this command use `$OMNILEARN_DIR` as the base.
 
+## Current Date Context (CRITICAL — Must Pass to ALL Subagents)
+
+```bash
+CURRENT_DATE=$(date +%Y-%m-%d)
+CURRENT_YEAR=$(date +%Y)
+```
+
+**Every subagent that does research or content generation MUST receive the current date and be told to prioritize current information.**
+
+## MCP Tool Call Semantics (CRITICAL — Subagents Frequently Get This Wrong)
+
+All subagents that use MCP tools MUST follow these exact calling conventions:
+
+### `context7_resolve-library-id` + `context7_query-docs`
+1. **ALWAYS call `context7_resolve-library-id` FIRST** with the library name to get the correct library ID.
+2. Use the returned library ID (format: `/org/package`) as the `libraryId` parameter in `context7_query-docs`.
+3. Do NOT guess or hardcode library IDs.
+4. Max 3 calls per question.
+
+### `google_search` / `websearch_web_search_exa`
+- Use specific, well-formed queries — not keywords, but describe the ideal page.
+- Good: `"blog post comparing Rust error handling patterns 2024"`
+- Bad: `"Rust error handling"`
+- Pass `query` as a plain string, not wrapped in an object.
+
+### General Rules
+- Match tool call parameter names EXACTLY as defined in the tool schema.
+- Do NOT wrap string parameters in extra objects or arrays.
+- Do NOT nest tool calls unless the API explicitly requires it.
+- If a tool call fails, verify parameter names match before retrying.
+
 ## MANDATORY TOOLS
 
 | Tool | When | Why |
@@ -97,7 +128,7 @@ All subsequent paths in this command use `$OMNILEARN_DIR` as the base.
 | `task(category="unspecified-high", background)` | Content creation | Heavy research, roadmap synthesis, file writing |
 | `task(category="deep", background)` | Autonomous multi-step | Complex subtasks that need internal orchestration |
 | `google_search` / `websearch_web_search_exa` | Research phases | Web research for content, learning paths, best practices |
-| `context7_resolve-library-id` + `context7_query_docs` | Tech skills | Official documentation for languages, frameworks, libraries |
+| `context7_resolve-library-id` + `context7_query-docs` | Tech skills | Official documentation for languages, frameworks, libraries |
 | `read`, `write`, `edit`, `bash`, `grep`, `glob` | Every phase | File operations and navigation |
 | `bash(git ...)` | Completion phase | Git commit after roadmap creation |
 
@@ -194,9 +225,10 @@ task(category="unspecified-high", run_in_background=true, prompt="
 
 2. EXPECTED OUTCOME: A comprehensive, structured markdown file covering all knowledge areas, concepts, tools, and practices needed for real-world proficiency in {skill} — **filtered and prioritized based on what the user already knows**.
 
-3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_resolve-library-id, context7_query_docs, read, write
+3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_resolve-library-id, context7_query-docs, read, write
 
 4. MUST DO:
+   - **CURRENT DATE: {CURRENT_DATE}** — ONLY search for and reference current information. Prioritize resources from the last 1-2 years. Check for deprecation warnings on any library/framework/tool. Prefer latest stable versions. If something has been superseded (e.g. Create React App → Vite, npm → pnpm/uv), flag it.
 
    FIRST — Consider the user's level and existing knowledge:
    - User's stated experience with {skill}: {user level}
@@ -256,6 +288,7 @@ task(category="unspecified-high", run_in_background=true, prompt="
 3. REQUIRED TOOLS: google_search, websearch_web_search_exa, read, write
 
 4. MUST DO:
+   - **CURRENT DATE: {CURRENT_DATE}** — ONLY search for and reference current information. Prioritize resources from the last 1-2 years. Check for deprecation warnings on any library/framework/tool. Prefer latest stable versions. If something has been superseded (e.g. Create React App → Vite, npm → pnpm/uv), flag it.
 
    FIRST — Consider the user's level:
    - User's experience with {skill}: {user level}
@@ -334,14 +367,15 @@ task(category="unspecified-high", run_in_background=false, timeout=300000, promp
 1. TASK: Synthesize research into a personalized, level-adaptive, cross-skill-integrated master roadmap for {skill}.
 2. EXPECTED OUTCOME: A detailed roadmap.md file with a learning path TAILORED to this user's level and existing knowledge — skipping what they already know, integrating related skills, and focused on real-world readiness.
 
-3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_query_docs, read, write, grep
+3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_query-docs, read, write, grep
 
 4. MUST DO:
+   - **CURRENT DATE: {CURRENT_DATE}** — ONLY reference current information. If you do additional online research, prioritize resources from the last 1-2 years. Check for deprecation warnings. Prefer latest stable versions of any library/framework/tool mentioned.
    - Read BOTH research files:
      * Content research: {RUNS_DIR}/research-content.md
      * Learning path research: {RUNS_DIR}/research-learning.md
    - Read cross-skill context: existing skills the user has
-   - If there are gaps or contradictions, do additional research online
+   - If there are gaps or contradictions, do additional research online (using current date context)
    
    CRITICAL — Personalization rules:
    - **Do NOT include topics the user already knows.** If the user is experienced in Python and learning FastAPI, skip Python fundamentals entirely.

package/commands/omnilearn-start.md

@@ -58,6 +58,37 @@ The goal metric: **Can the user apply what they learned to real-world problems t
                 └── ...
 ```
 
+## Current Date Context (CRITICAL — Must Pass to ALL Subagents)
+
+```bash
+CURRENT_DATE=$(date +%Y-%m-%d)
+CURRENT_YEAR=$(date +%Y)
+```
+
+**Every subagent that does research or content generation MUST receive the current date and be told to prioritize current information over deprecated or outdated resources.**
+
+## MCP Tool Call Semantics (CRITICAL — Subagents Frequently Get This Wrong)
+
+All subagents that use MCP tools MUST follow these exact calling conventions:
+
+### `context7_resolve-library-id` + `context7_query-docs`
+1. **ALWAYS call `context7_resolve-library-id` FIRST** with the library name to get the correct library ID.
+2. Use the returned library ID (format: `/org/package`) as the `libraryId` parameter in `context7_query-docs`.
+3. Do NOT guess or hardcode library IDs.
+4. Max 3 calls per question.
+
+### `google_search` / `websearch_web_search_exa`
+- Use specific, well-formed queries — not keywords, but describe the ideal page.
+- Good: `"current state of Rust async patterns 2025"`
+- Bad: `"Rust async"`
+- Pass `query` as a plain string, not wrapped in an object.
+
+### General Rules
+- Match tool call parameter names EXACTLY as defined in the tool schema.
+- Do NOT wrap string parameters in extra objects or arrays.
+- Do NOT nest tool calls unless the API explicitly requires it.
+- If a tool call fails, verify parameter names match before retrying.
+
 ## MANDATORY TOOLS
 
 | Tool | When | Why |
@@ -67,7 +98,7 @@ The goal metric: **Can the user apply what they learned to real-world problems t
 | `task(category="writing")` | Content writing | Topic explanations, solution guides |
 | `task(category="unspecified-high", ["programming"])` | Technical work | Test scripts, scaffold code |
 | `google_search` / `websearch_web_search_exa` | Research | Learning resources, topic best practices |
-| `context7_query_docs` | Tech skills | Official docs for languages/frameworks |
+| `context7_query-docs` | Tech skills | Official docs for languages/frameworks |
 | `question` tool | User interaction | Present topic choices, ask for preferences |
 | `read`, `write`, `edit`, `bash`, `grep`, `glob` | Every phase | File operations |
 | `bash(git ...)` | Completion | Commit progress |
@@ -180,9 +211,10 @@ task(category="deep", run_in_background=false, timeout=600000, prompt="
 1. TASK: Create a comprehensive subtopic roadmap and initial learning materials for the topic '{topic}' within the skill '{skill}'.
 2. EXPECTED OUTCOME: A detailed topic-roadmap.md with structured learning path, AND the first assignment with question, test script, scaffold, and solution guide.
 
-3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_resolve-library-id, context7_query_docs, read, write, bash, grep
+3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_resolve-library-id, context7_query-docs, read, write, bash, grep
 
 4. MUST DO — Step-by-Step:
+   - **CURRENT DATE: {CURRENT_DATE}** — ONLY research current information. Prioritize resources from the last 1-2 years. Check for deprecation warnings. Prefer latest stable versions of any library/framework/tool. If older resources reference superseded tools (e.g. CRA → Vite, pip → uv), flag and use the current standard.
 
    STEP 1 — Research:
    - Read the main roadmap to understand how this topic fits: {ROADMAP}
@@ -369,9 +401,10 @@ task(category="unspecified-high", run_in_background=false, prompt="
 1. TASK: Create a focused micro-exercise that tests the user's understanding of '{concept}' in '{skill}'. The user is struggling with this concept during assignment '{assignment}' on topic '{topic}'.
 2. EXPECTED OUTCOME: A self-contained micro-exercise (5-15 min to solve) that isolates the specific concept and lets the user figure it out by coding.
 
-3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_query_docs, read, write
+3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_query-docs, read, write
 
 4. MUST DO:
+   - **CURRENT DATE: {CURRENT_DATE}** — ONLY research current information. Check for deprecation warnings. If a library/framework has a newer standard (e.g. CRA → Vite, pip → uv), reference the current approach.
    - Read the current assignment: {ASSIGNMENT_DIR}/question.md (to understand context without giving away the solution)
    - Research the concept online to find the MOST COMMON confusion points
    - Design a micro-exercise that:
@@ -444,6 +477,7 @@ task(category="writing", run_in_background=false, prompt="
 3. REQUIRED TOOLS: read, write
 
 4. MUST DO:
+   - **CURRENT DATE: {CURRENT_DATE}** — Use current, real-world examples. Avoid outdated patterns or deprecated APIs.
    - Read the current assignment to understand what's been covered
    - Create 2-3 smaller exercises that target the specific area the user is struggling with
    - Each should be solvable in 5-15 minutes
@@ -455,6 +489,8 @@ task(category="writing", run_in_background=false, prompt="
 ")
 ```
 
+```
+
 ### 3.2 Track All Interactions
 
 For each user interaction during the session:
@@ -499,9 +535,10 @@ task(category="unspecified-high", run_in_background=false, timeout=300000, promp
 1. TASK: Create the next assignment ({assignment-num}) for topic '{topic}' in skill '{skill}'.
 2. EXPECTED OUTCOME: Complete assignment with question.md, test script, scaffold, and solution-guide.md at the next difficulty level.
 
-3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_query_docs, read, write
+3. REQUIRED TOOLS: google_search, websearch_web_search_exa, context7_query-docs, read, write
 
 4. MUST DO:
+   - **CURRENT DATE: {CURRENT_DATE}** — ONLY use current, real-world scenarios. Avoid outdated APIs, deprecated libraries, or superseded best practices. Research what's current in the industry for this topic.
    - Read the topic-roadmap.md: {TOPICS_DIR}/{topic}/topic-roadmap.md
    - Read the previous assignment(s) to ensure progression: {ASSIGNMENT_DIR}
    - Read the user's learning preferences and history from {SKILL_PREFS}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omnilearn-workflow",
-  "version": "1.0.1",
+  "version": "1.0.3",
   "description": "OmniLearn — AI-powered adaptive learning workflow for OpenCode. Multi-agent orchestration that creates personalized roadmaps, hands-on assignments, and tracks progress across any skill.",
   "keywords": [
     "opencode",