Skip to content

alessiomarcone/agent-fieldbook / plugins/knowledge-pack/skills/navigate

navigate

Verified

Routes ambiguous mechanism comparisons to the smallest appropriate agent mechanism and skill. Use when the user is unsure whether they need instructions, a prompt, skill, subagent, hook, scheduler, MCP, plugin, Claude workflow, or Codex workflow; if the artifact is already selected, its specialist skill wins.

Navigate

Route the request. Do not absorb specialist work that belongs to a narrower skill.

Reference

Read references/knowledge-base.md when the mechanism boundary or product branch is not obvious.

Routing table

IntentRoute
Improve or design a requestprompt
Fact-check or stress-test an outputverify
Decide, design, or configure delegated agentssubagent
Create or refine an agent skillskill
Package or distribute reusable capabilitiesplugin
Design a Cowork workflowcowork
Operate a Codex-specific surfacecodex
Build an official learning pathlearn
Distill source materialknowledge-card
Run work on a clock or recurring schedulecowork for Claude/Cowork, codex for Codex, or the host scheduler/API

If no specialist matches, select the smallest supported mechanism: normal chat/task, project knowledge, CLAUDE.md or AGENTS.md, skill, subagent, hook, scheduler/automation, MCP/connector, plugin, or API/SDK. Hooks are event-driven; they are not a substitute for clock-driven scheduling.

Output contract

Return three fields, plus an optional fourth:

  1. Route — one skill or mechanism.
  2. Why — one short paragraph.
  3. Invoke — the exact next invocation and minimum input.
  4. Freshness check — only when a product capability may have changed.

Use /knowledge-pack:<skill> for the Claude Code plugin and /<skill> for a standalone Claude skill. Use $knowledge-pack:<skill> for the Codex plugin and $<skill> for a standalone Codex skill.

Boundaries

  • Choose one adequate route, not a menu of equivalent options.
  • Own comparisons such as “custom agent or skill?”; once the user explicitly selects an artifact, its specialist skill wins.
  • Do not execute the specialist workflow unless routing alone would block progress.
  • Do not conflate a skill, subagent, hook, plugin, connector, or MCP server.
  • Answer in the user's language.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall