Results for “routes”

Routes documents in the psychological counseling domain to the appropriate family skill based on methodological terms and task goals.

Routes ambiguous or multi-domain engineering requests to the smallest ordered skill set. Do not use for clear single-skill work or same-task follow-ups.

Routes marketing questions to the right specialist skill, orchestrates multi-skill campaigns, and runs cross-functional marketing audits.

Routes requests to design, create, debug, update, or upgrade GitHub Agentic Workflows by loading the appropriate workflow prompt or skill file.

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows by loading the appropriate workflow prompt or skill file.

Routes general Convex requests to the appropriate project skill, installs official Convex AI guidance, and provides command preflight instructions for Convex CLI operations.

Routes trading and investing goals to the right workflow, skillset, API profile, and setup path without executing trades.

Routes operational tasks across analytics, finance, infrastructure, legal, studio production, and support sub-skills, applying behavioral science and governance gates.

Frames tasks with explicit goals, success evidence, stop conditions, and boundaries before execution, then routes work to the appropriate workflow.

Routes user requests to the most relevant skill or workflow in this repository, acting as a navigator over available skills.

Routes tasks to specialized agent offices and applies behavioral science frameworks to every output, with confidence tagging and session memory.

Routes engineering design, delivery, reliability, security, operations, and maintenance prompts to a router skill backed by specialist guidance for multiple AI coding agents.

Routes you to the right skill or flow for your situation, covering idea-to-ship, triage, codebase health, and cross-session handoffs.

Checks project progress, summarizes recent work and what's ahead, then routes to the next action by executing an existing plan or creating a new one.

Routes founder questions to the right advisor roles, coordinates multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions.

Routes user intents to the right operation for a persistent Markdown second brain, enforcing citation and discussion before any write, with read-only MCP tools for queries.

Use when deciding which cell-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for Cell (Cell Press). Routes — it does not replace — the specialized skills.

Routes Salesforce, Force.com, and Lightning Platform questions to the correct skill package from a library of over 1,000 domain-specific skills, covering Apex, SOQL, Flow, LWC, and more.

Use when deciding which jama-* sub-skill to invoke next, or when sequencing a clinical manuscript from scope check through revision for JAMA (Journal of the American Medical Association). Routes — does not replace — the specialized skills.

Use when deciding which nejm-* sub-skill to invoke next, or when sequencing a clinical manuscript from significance test through response to reviewers for The New England Journal of Medicine. Routes — it does not replace — the specialized skills.

Use when deciding which pnas-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for PNAS (Proceedings of the National Academy of Sciences). Routes — it does not replace — the specialized skills.

Routes Salesforce Flow Builder requests to the correct skill package among 63 available, covering record-triggered, screen, scheduled, and orchestration flows, bulkification, fault handling, limits, and testing.

Routes requests into the correct obsidian-mind mode: install, daily session loop, capture, review, maintenance, multi-agent wiring, or semantic search, using a ready-made Obsidian vault template for persistent agent memory.

This skill should be used when working with Obsidian files including .md notes with wikilinks/callouts/properties, .base database views with filters/formulas, or .canvas visual diagrams. Routes to specialized sub-skills based on file type and task context. Features self-iterative learning that improves with use.

Use when deciding which AER-skills sub-skill to use next, before choosing a specialized skill or after a user asks how to sequence manuscript work from topic selection through rebuttal for AER, AER:Insights, or AEJ journals. Routes — does not replace — the specialized skills.

Routes to 259 Salesforce admin skill packages for declarative configuration tasks like objects, fields, record types, page layouts, permission sets, reports, and record-access models. Use when the request mentions these topics to find and open the exact skill package.

Use as the entry point for any PMLA (Publications of the Modern Language Association) manuscript. Routes to the right PMLA sub-skill based on where you are in the lifecycle and which venue fits — a regular blind-reviewed article or a special feature (Theories and Methodologies, The Changing Profession, Criticism in Translation, Little-known Documents). It dispatches; it does not draft content.

Routes writing tasks to the correct voice playbook by reading a voice selection authority file fresh on every call, classifying the task into one of 22 content types, and returning a load list with crossover budget and phrasebook section.

Use as the entry point for any Mind (philosophy journal) article. Routes to the right Mind sub-skill based on where you are in the lifecycle and whether the piece is an article, discussion note, book review, or critical notice. Mind is analytic philosophy — argument, not data — so the router's first job is to confirm there is a sharp thesis and a sound argument. It dispatches; it does not draft content.

Decompose tasks into structured, outcome-defined process entries with complexity triage. Load when user says "decompose this", "break this down", "what steps do I need", "plan this out", "what's the process for", "how do I approach this", or when any complex task needs structured execution planning. Includes a problem-understanding pass before complexity triage. Routes to `problem-to-plan` when the user needs planning deliverables (spec + plan + TODO). Does NOT replace brainstorming — brainstorming is design approval (upstream), this is execution planning (downstream).