@soleri/forge 9.11.0 → 9.13.0

package/{dist/skills/discovery-phase → src/skills/soleri-discovery-phase}/SKILL.md

@@ -1,10 +1,9 @@
 ---
-name: discovery-phase
+name: soleri-discovery-phase
 description: >
-  Use for structured exploration before committing to a plan — "I don't know where to start",
-  "what are our options", "investigate", "research this", "explore options", "discovery". Ideal
-  when requirements are unclear, entering a new domain, or facing architectural decisions. Produces
-  a discovery document with options, tradeoffs, and a recommendation.
+  Use when the user says "I don't know where to start", "investigate",
+  "research this", "explore the problem", or "discovery". Structured exploration
+  before committing to a plan, producing options with tradeoffs.
 ---
 
 # Discovery Phase
@@ -19,12 +18,13 @@ Do NOT create a plan, write code, or take any implementation action until the di
 
 1. **Define the question** — restate what we're exploring as one specific, answerable sentence
 2. **Search vault for prior art** — `YOUR_AGENT_core op:search_intelligent params: { query: "<question>", mode: "scan" }`. Also `op:memory_search` with `crossProject: true`.
-3. **Explore codebase** — read relevant files, configs, architecture, recent commits
-4. **Identify constraints** — hard (must-haves) vs soft (nice-to-haves), unknowns that block a decision
-5. **Draft 2-4 options** — each with pros, cons, risk, and effort (S/M/L)
-6. **Recommend** — pick one, state the primary reason, note what would change the answer
-7. **Capture to vault** — persist the discovery finding
-8. **Transition** — hand off to brainstorming or writing-plans skill
+3. **Get brain recommendations** — `YOUR_AGENT_core op:brain_recommend params: { query: "<discovery topic>" }`. Get brain recommendations for similar past explorations.
+4. **Explore codebase** — read relevant files, configs, architecture, recent commits
+5. **Identify constraints** — hard (must-haves) vs soft (nice-to-haves), unknowns that block a decision
+6. **Draft 2-4 options** — each with pros, cons, risk, and effort (S/M/L)
+7. **Recommend** — pick one, state the primary reason, note what would change the answer
+8. **Capture to vault** — persist the discovery finding
+9. **Transition** — hand off to brainstorming or writing-plans skill
 
 ## Option Format
 
@@ -61,9 +61,10 @@ Save to `docs/discoveries/YYYY-MM-DD-<topic>.md` and commit. Then transition to
 
 ## Quick Reference
 
-| Op                   | When to Use                        |
-| -------------------- | ---------------------------------- |
-| `search_intelligent` | Search vault for prior art         |
-| `memory_search`      | Check session history and projects |
-| `capture_knowledge`  | Persist discovery finding          |
-| `route_intent`       | Classify what comes after          |
+| Op                   | When to Use                                         |
+| -------------------- | --------------------------------------------------- |
+| `search_intelligent` | Search vault for prior art                          |
+| `memory_search`      | Check session history and projects                  |
+| `brain_recommend`    | Brain recommendations for similar past explorations |
+| `capture_knowledge`  | Persist discovery finding                           |
+| `route_intent`       | Classify what comes after                           |

package/src/skills/soleri-dream/SKILL.md

@@ -0,0 +1,104 @@
+---
+name: soleri-dream
+description: >
+  Use when the user says "dream", "consolidate memory", "clean up memory",
+  "memory cleanup", or "dream status". Runs automatic memory consolidation
+  — dedup, archive stale entries, resolve contradictions.
+---
+
+# /dream — Automatic Memory Consolidation
+
+Runs a full "dream" pass over the vault: dedup, archive stale entries, resolve
+contradictions, and produce a summary report. Inspired by how REM sleep
+consolidates biological memory.
+
+**Announce at start:** "Running a dream pass — consolidating vault memory."
+
+## Quick Commands
+
+| Command         | What it does                                              |
+| --------------- | --------------------------------------------------------- |
+| `/dream`        | Run a full dream pass (forces, bypasses gate)             |
+| `/dream status` | Show dream state: last dream, sessions since, eligibility |
+
+## Orchestration
+
+### Step 1: Check Dream Status
+
+```
+YOUR_AGENT_dream op:dream_status
+```
+
+Report current state to user as a table:
+
+| Field                         | Value                    |
+| ----------------------------- | ------------------------ |
+| **Sessions since last dream** | {sessionsSinceLastDream} |
+| **Last dream**                | {lastDreamAt or "Never"} |
+| **Total dreams**              | {totalDreams}            |
+| **Gate eligible**             | {gateEligible}           |
+
+### Step 2: Run Dream
+
+If user explicitly asked to dream (manual `/dream`), force it:
+
+```
+YOUR_AGENT_dream op:dream_run
+  params: { force: true }
+```
+
+If auto-triggered (session start), respect the gate:
+
+```
+YOUR_AGENT_dream op:dream_run
+  params: { force: false }
+```
+
+If the response contains `skipped: true`, inform the user:
+"Dream skipped — {reason}. Use `/dream` to force a run."
+
+### Step 3: Present Dream Report
+
+Format the dream report as a table:
+
+| Metric                     | Value                 |
+| -------------------------- | --------------------- |
+| **Duration**               | {durationMs}ms        |
+| **Duplicates found**       | {duplicatesFound}     |
+| **Stale entries archived** | {staleArchived}       |
+| **Contradictions found**   | {contradictionsFound} |
+| **Total dreams**           | {totalDreams}         |
+| **Timestamp**              | {timestamp}           |
+
+### Step 4: Rebuild Brain Intelligence
+
+```
+YOUR_AGENT_core op:brain_build_intelligence
+```
+
+Rebuild brain intelligence with the freshly consolidated vault data.
+
+### Step 5: Capture to Memory
+
+```
+YOUR_AGENT_memory op:session_capture
+  params: {
+    summary: "Dream pass completed: {duplicatesFound} duplicates, {staleArchived} stale archived, {contradictionsFound} contradictions found"
+  }
+```
+
+## Gate Logic
+
+Auto-dream triggers automatically on session start when BOTH conditions are met:
+
+- **5+ sessions** since last dream
+- **24+ hours** since last dream
+
+Manual `/dream` always runs immediately (force=true).
+
+## Background
+
+Inspired by Claude Code's AutoDream feature and the neuroscience of REM sleep.
+During sleep, the brain consolidates short-term memories into long-term storage,
+prunes irrelevant connections, and resolves conflicts. The /dream skill does
+the same for the vault.

package/src/skills/{env-setup → soleri-env-setup}/SKILL.md

@@ -1,12 +1,9 @@
 ---
-name: env-setup
+name: soleri-env-setup
 description: >
-  Use when a developer needs to set up, fix, or restore a local development environment.
-  Triggers on post-clone setup, project onboarding, first-time running a repo, pulled changes
-  that broke the build, missing or misconfigured dependencies, MODULE_NOT_FOUND or Cannot find
-  module errors, gyp ERR or native module build failures, missing .env files or unknown required
-  environment variables, database setup, Docker compose issues, or connection refused during
-  local dev. Covers Node.js, Python, Rust, Go, Ruby, PHP, and Docker-based projects.
+  Use when the user says "setup environment", "post-clone setup", "broken build",
+  "missing dependencies", or "MODULE_NOT_FOUND". Detects what a project needs,
+  diagnoses what's missing, and produces an actionable setup checklist.
 ---
 
 # Environment Setup
@@ -26,6 +23,16 @@ Scan the project root for configuration files, detect the tech stack and depende
 - Docker/container environment not starting
 - Missing `.env` file or environment variables
 
+## Check Vault for Known Setup Patterns
+
+```
+YOUR_AGENT_core op:search_intelligent
+  params: { query: "<tech stack> setup gotchas" }
+
+YOUR_AGENT_core op:memory_search
+  params: { query: "environment setup <project>" }
+```
+
 ## Detection Phase
 
 Scan the project root and identify:
@@ -149,3 +156,20 @@ If monorepo detected (turbo.json, nx.json, pnpm-workspace.yaml):
 - **Missing runtime version** — subtle bugs from wrong Node/Python version.
 - **Docker not running** — cryptic "connection refused" errors.
 - **Stale dependencies** — after `git pull`, always re-install if lockfile changed.
+
+## Capture Setup Learnings
+
+If any non-obvious steps or workarounds were needed:
+
+```
+YOUR_AGENT_core op:capture_knowledge
+  params: { title: "<gotcha>", description: "<what happened and the fix>", type: "anti-pattern", tags: ["env-setup", "<tech-stack>"] }
+```
+
+## Agent Tools Reference
+
+| Op                   | When to Use                        |
+| -------------------- | ---------------------------------- |
+| `search_intelligent` | Check vault before starting        |
+| `memory_search`      | Find similar past experiences      |
+| `capture_knowledge`  | Persist patterns worth remembering |

package/src/skills/{executing-plans → soleri-executing-plans}/SKILL.md

@@ -1,10 +1,9 @@
 ---
-name: executing-plans
+name: soleri-executing-plans
 description: >
-  Use when the user says "execute my plan", "run the plan", "start executing", "implement the
-  plan step by step", or has a written plan to execute sequentially with review checkpoints.
-  Tasks run one at a time in order. If tasks are independent and can run in parallel, use
-  parallel-execute instead.
+  Use when the user says "execute my plan", "run the plan", "start executing",
+  or "implement the plan". Executes tasks sequentially with review checkpoints.
+  For parallel execution, use parallel-execute instead.
 ---
 
 # Executing Plans

package/{dist/skills/finishing-a-development-branch → src/skills/soleri-finishing-a-development-branch}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: finishing-a-development-branch
+name: soleri-finishing-a-development-branch
 description: >
-  Use when the user says "finish branch", "merge branch", "ready to merge", "PR ready",
-  "close branch", "submit PR", or wants to finalize a development branch for merge into
-  the base branch.
+  Use when the user says "finish branch", "ready to merge", "PR ready",
+  "submit PR", or "close branch". Handles pre-merge checks, PR creation,
+  merge strategy, and branch cleanup.
 ---
 
 # Finishing a Development Branch
@@ -12,6 +12,18 @@ Pre-merge checks, PR creation, merge strategy, and branch cleanup.
 
 **Announce at start:** "I'm using the finishing-a-development-branch skill to prepare this branch for merge."
 
+## Vault Context
+
+Search for merge patterns and known conflict areas:
+
+```
+YOUR_AGENT_core op:search_intelligent
+  params: { query: "merge patterns <branch domain>" }
+
+YOUR_AGENT_core op:memory_search
+  params: { query: "merge conflicts" }
+```
+
 ## Step 1: Pre-Merge Checklist
 
 Run all checks before creating a PR. Stop on any failure.
@@ -57,6 +69,15 @@ If the base branch has diverged:
 
 Never force-push a rebased branch that others are working on.
 
+### Capture Merge Learnings
+
+If tricky conflicts were resolved:
+
+```
+YOUR_AGENT_core op:capture_knowledge
+  params: { title: "<conflict pattern>", description: "<resolution strategy>", type: "pattern", tags: ["git", "merge", "conflict-resolution"] }
+```
+
 ## Step 5: Branch Cleanup
 
 After merge is confirmed:
@@ -65,6 +86,8 @@ After merge is confirmed:
 2. `git branch -d <branch>` — delete local branch
 3. If remote branch not auto-deleted: `git push origin --delete <branch>`
 
+**This step is mandatory, not optional.** Stale branches accumulate fast.
+
 ## Anti-Patterns
 
 - **Force-pushing to shared branches** — destroys others' history; only force-push personal branches
@@ -74,3 +97,11 @@ After merge is confirmed:
 - **Leaving stale branches** — delete after merge; stale branches create confusion
 
 **Related skills:** executing-plans, verification-before-completion
+
+## Agent Tools Reference
+
+| Op                   | When to Use                        |
+| -------------------- | ---------------------------------- |
+| `search_intelligent` | Check vault before starting        |
+| `memory_search`      | Find similar past experiences      |
+| `capture_knowledge`  | Persist patterns worth remembering |

package/src/skills/{fix-and-learn → soleri-fix-and-learn}/SKILL.md

@@ -1,10 +1,9 @@
 ---
-name: fix-and-learn
+name: soleri-fix-and-learn
 description: >
-  Use AFTER a root cause has been identified (typically via systematic-debugging) to execute
-  the fix and capture the learning in the vault. Triggers on "fix it", "apply the fix",
-  "patch this and remember". Do NOT use as the first response to a bug — use
-  systematic-debugging first to find root cause.
+  Use when the user says "fix it", "apply the fix", "patch this and remember",
+  or "fix and capture". Executes a fix AFTER root cause is identified and
+  captures the learning in the vault. Use systematic-debugging first.
 ---
 
 # Fix & Learn — Debug, Repair, Capture

package/{dist/skills/health-check → src/skills/soleri-health-check}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: health-check
+name: soleri-health-check
 description: >
-  Use when the user asks "check health", "system status", "how healthy is the vault",
-  "knowledge quality", "run diagnostics", "vault health report", or wants a read-only health
-  assessment of the knowledge base — scoring, reporting, finding issues. Does NOT modify vault
-  entries. To actively clean, merge, or deduplicate, use vault-curate instead.
+  Use when the user says "system health", "agent health", "run diagnostics",
+  "system status", or "check health". Read-only health assessment of the
+  knowledge base — scoring, reporting, finding issues. For deep quality
+  analysis (contradictions, stale patterns, knowledge debt), use vault-smells instead.
 ---
 
 # Health Check — Knowledge Base Maintenance

package/{dist/skills/knowledge-harvest → src/skills/soleri-knowledge-harvest}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: knowledge-harvest
+name: soleri-knowledge-harvest
 description: >
-  Use to EXTRACT multiple patterns from a source — code, docs, PRs, articles. Triggers on
-  "learn from this", "harvest knowledge", "ingest this document", "extract patterns from".
-  The agent reads the source and identifies what to capture. For saving a single known item,
-  use vault-capture instead.
+  Use when the user says "learn from this", "harvest knowledge", "ingest this",
+  or "extract patterns from". Extracts multiple patterns from a source like
+  code, docs, PRs, or articles into the vault. For saving a single known
+  pattern, use vault-capture instead.
 ---
 
 # Knowledge Harvest — Extract Patterns From Anything

package/src/skills/{mcp-doctor → soleri-mcp-doctor}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: mcp-doctor
+name: soleri-mcp-doctor
 description: >
-  Use when MCP servers fail to connect, tools are missing, or the user says "check MCP",
-  "MCP not working", "server not connecting", "tools missing", "heal MCP", "fix MCP",
-  "mcp doctor", "mcp status". Diagnoses and repairs MCP server connectivity issues.
+  Use when the user says "MCP not working", "tools missing", "fix MCP",
+  "mcp doctor", or "server not connecting". Diagnoses and repairs MCP server
+  connectivity issues.
 ---
 
 # MCP Doctor — Diagnose and Heal MCP Connections

package/{dist/skills/onboard-me → src/skills/soleri-onboard-me}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: onboard-me
+name: soleri-onboard-me
 description: >
-  Use when someone is new to the PROJECT and needs orientation — "onboard me", "I'm new here",
-  "project overview", "what should I know about this codebase". Questions about the project's
-  patterns and conventions, not about the agent's capabilities (use agent-guide for that).
+  Use when the user says "onboard me", "I'm new here", "project overview",
+  or "what should I know about this codebase". Provides a structured tour
+  of everything the vault knows about this project.
 ---
 
 # Onboard Me — Instant Project Intelligence
@@ -101,6 +101,15 @@ YOUR_AGENT_core op:vault_age_report
 
 **Tip:** Use vault-navigator to search topics as you work. Use second-opinion before architectural decisions.
 
+### Record Onboarding
+
+```
+YOUR_AGENT_core op:capture_knowledge
+  params: { title: "Onboarding completed for <project>", description: "<key takeaways and knowledge gaps identified>", type: "workflow", tags: ["onboarding", "<project>"] }
+```
+
+Record what was covered and what gaps remain for future onboarding.
+
 ## Common Mistakes
 
 - Dumping all vault entries instead of curating the most important ones
@@ -119,3 +128,4 @@ YOUR_AGENT_core op:vault_age_report
 | `brain_strengths`                           | Proven patterns               |
 | `brain_global_patterns`                     | Cross-project patterns        |
 | `admin_search_insights`                     | Knowledge gaps                |
+| `capture_knowledge`                         | Record onboarding completion  |

package/{dist/skills/parallel-execute → src/skills/soleri-parallel-execute}/SKILL.md

@@ -1,10 +1,9 @@
 ---
-name: parallel-execute
+name: soleri-parallel-execute
 description: >
-  Use when executing a plan where independent tasks can run concurrently. Triggers on "run in
-  parallel", "parallelize", "fan out", "concurrent execution", "run simultaneously", "at the
-  same time", "dispatch subagents", "batch execute", or when a plan has 3+ tasks with no
-  dependency overlap. For sequential task-by-task execution, use executing-plans instead.
+  Use when the user says "run in parallel", "fan out", "concurrent execution",
+  "batch execute", or "dispatch subagents". Executes independent plan tasks
+  concurrently via subagents. For sequential execution, use executing-plans.
 ---
 
 # Parallel Execute — Subagent-Driven Plan Execution
@@ -165,7 +164,7 @@ As subagents complete, collect their results. For each completed task:
 | Pass | Critical issues   | Dispatch targeted fix subagent (max 2 retries)              |
 | Pass | Minor issues only | Mark completed, note issues for later                       |
 
-6. **Mark completed:**
+1. **Mark completed:**
    ```
    YOUR_AGENT_core op:update_task params:{ planId: "<id>", taskIndex: <n>, status: "completed" }
    ```
@@ -234,7 +233,13 @@ YOUR_AGENT_core op:session_capture params:{
 | Tasks touch files in the same package        | Use `isolation: "worktree"`               |
 | Tasks modify the same file                   | **Do NOT parallelize** — run sequentially |
 
-When using worktree isolation, the controller must merge worktree changes back after review passes.
+When using worktree isolation, the controller must merge worktree changes back after review passes, then **immediately delete the local branch**:
+
+```bash
+git branch -D <subagent/taskId>
+```
+
+Worktree branches are local-only — never push them to remote. Branch cleanup is mandatory after every merge.
 
 ## Failure Handling
 

package/src/skills/soleri-research-scout/SKILL.md

@@ -0,0 +1,225 @@
+---
+name: soleri-research-scout
+description: >
+  Use when the user says "scout", "research scout", "find new info",
+  "what's new", or "scan the web". Discovers new information that challenges
+  or updates existing vault knowledge via web search.
+---
+
+# /research-scout — Knowledge Discovery via Vault Branching
+
+Finds new information that challenges or updates existing vault knowledge.
+Searches web, Reddit, HN, and Quora for strategies, tools, announcements,
+and workflow changes relevant to vault domains.
+
+Findings go to a **scout branch** — never the main vault. Weekly review
+promotes the good ones, discards the rest.
+
+**Announce at start:** "Scouting for new intelligence — findings go to the scout branch, not the main vault."
+
+## Two Modes
+
+| Command                  | What it does                                     |
+| ------------------------ | ------------------------------------------------ |
+| `/research-scout`        | Run a scout pass — search web, capture to branch |
+| `/research-scout review` | Review branch findings, promote or discard       |
+
+---
+
+## Mode 1: Scout Pass
+
+### Step 1: Ensure Scout Branch Exists
+
+```
+YOUR_AGENT_branching op:vault_branch_list
+```
+
+If no branch named `scout-findings` exists, create it:
+
+```
+YOUR_AGENT_branching op:vault_branch
+  params: { name: "scout-findings" }
+```
+
+### Step 2: Identify What to Scout
+
+Pull active domains and recent topics from the vault:
+
+```
+YOUR_AGENT_vault op:vault_domains
+YOUR_AGENT_vault op:vault_recent params:{ limit: 15 }
+YOUR_AGENT_brain op:brain_strengths params:{ limit: 10 }
+```
+
+From these, build 3-5 focused search queries based on:
+
+- Active vault domains (e.g., "typescript", "react", "testing")
+- Strong brain patterns (what the user works on most)
+- Recent capture topics (what's top of mind)
+
+### Step 3: Web Search
+
+For each query, search with year context:
+
+```
+WebSearch: "{topic} new tools breaking changes 2026"
+WebSearch: "{topic} best practices updated site:reddit.com OR site:news.ycombinator.com"
+```
+
+Focus on:
+
+- New tool releases or deprecations
+- Breaking changes in dependencies
+- Updated best practices that contradict vault patterns
+- Workflow patterns gaining traction
+
+### Step 4: Cross-Reference Against Main Vault
+
+For each finding, check if the main vault already knows:
+
+```
+YOUR_AGENT_vault op:search_intelligent
+  params: { query: "{finding summary}" }
+```
+
+Classify:
+
+- **NEW** — vault has nothing on this topic. Worth capturing.
+- **UPDATE** — vault has related entry but info is outdated. Capture with link.
+- **CONTRADICTS** — finding conflicts with existing vault pattern. High value. Capture with contradiction link.
+- **REDUNDANT** — vault already has this. Skip entirely.
+
+**Only keep NEW, UPDATE, and CONTRADICTS.** Discard REDUNDANT.
+
+### Step 5: Validate Before Capture
+
+For each non-redundant finding:
+
+- Verify from at least 2 independent sources
+- Check the date — reject anything older than 3 months
+- Assess relevance — does this matter for active projects?
+
+**If a finding can't be verified from 2 sources, skip it.**
+
+### Step 6: Capture to Scout Branch
+
+Switch to scout branch, capture, switch back:
+
+```
+YOUR_AGENT_branching op:vault_branch_add
+  params: {
+    branch: "scout-findings",
+    entry: {
+      title: "{concise finding title}",
+      type: "pattern",
+      domain: "{relevant domain}",
+      description: "{what changed and why it matters}",
+      why: "Scout [{date}]: {source URL}. {what it changes or adds}",
+      severity: "suggestion",
+      tags: ["research-scout", "{domain}", "{source-type}"]
+    }
+  }
+```
+
+If the finding CONTRADICTS an existing main vault entry, note the
+contradicted entry ID in the description so the reviewer can link them
+during promotion.
+
+### Step 7: Scout Report
+
+Present results:
+
+| #   | Finding | Type        | Domain   | Source | Status                            |
+| --- | ------- | ----------- | -------- | ------ | --------------------------------- |
+| 1   | {title} | NEW         | {domain} | {url}  | Captured to branch                |
+| 2   | {title} | CONTRADICTS | {domain} | {url}  | Captured — contradicts {entry_id} |
+| 3   | {title} | REDUNDANT   | {domain} | —      | Skipped                           |
+
+**Summary:** {N} sources searched, {found} findings, {captured} captured to scout branch, {skipped} skipped as redundant.
+
+### Step 8: Session Capture
+
+```
+YOUR_AGENT_memory op:session_capture
+  params: {
+    summary: "Research scout: searched {N} topics, {captured} findings staged to scout-findings branch, {contradictions} contradictions flagged",
+    topics: ["{domains searched}"],
+    intent: "research"
+  }
+```
+
+---
+
+## Mode 2: Scout Review (Weekly)
+
+### Step 1: Load Branch Findings
+
+```
+YOUR_AGENT_branching op:vault_branch_list
+```
+
+List all entries on the `scout-findings` branch.
+
+### Step 2: Triage Each Finding
+
+For each entry on the branch, present to the user:
+
+| Field           | Value                          |
+| --------------- | ------------------------------ |
+| **Title**       | {title}                        |
+| **Domain**      | {domain}                       |
+| **Source**      | {from why field}               |
+| **Age**         | {days since capture}           |
+| **Contradicts** | {entry ID if noted, or "none"} |
+
+Ask: **Promote, Archive, or Skip?**
+
+- **Promote** — merge into main vault via `vault_merge_branch` or manual `capture_knowledge`. If it contradicts an entry, create a `link_entries` with type `contradicts`.
+- **Archive** — remove from branch, don't add to main vault.
+- **Skip** — leave on branch for next review.
+
+### Step 3: Clean Up Branch
+
+After review, delete the branch and recreate fresh:
+
+```
+YOUR_AGENT_branching op:vault_delete_branch
+  params: { name: "scout-findings" }
+YOUR_AGENT_branching op:vault_branch
+  params: { name: "scout-findings" }
+```
+
+### Step 4: Report
+
+| Metric       | Value      |
+| ------------ | ---------- |
+| **Reviewed** | {total}    |
+| **Promoted** | {promoted} |
+| **Archived** | {archived} |
+| **Skipped**  | {skipped}  |
+
+---
+
+## Scheduling
+
+### Nightly scout (3x)
+
+```
+/schedule create --name "research-scout-nightly" --cron "0 2,4,6 * * *" --prompt "/research-scout"
+```
+
+### Weekly review (Monday 9am)
+
+```
+/schedule create --name "research-scout-review" --cron "0 9 * * 1" --prompt "/research-scout review"
+```
+
+---
+
+## Quality Gates
+
+- **Max 5 captures per scout run** — if you find more, pick the 5 most impactful
+- **2-source minimum** — never capture from a single unverified source
+- **3-month freshness** — reject findings older than 90 days
+- **Domain relevance** — only scout domains the user actively works in
+- **No opinions** — capture facts, tools, and changes, not hot takes