Results for “route-planning”

Routes legacy PWDEV Code command intents to their canonical PWDEV Flow skills, preserving history when adopting an existing .planning workspace.

Use this when planning or refining an Express or Express-style Node.js API with route groups, middleware boundaries, validation, auth, error handling, and service layering.

Turns complex business goals into navigable strategic maps, identifying milestones, resource nodes, risk points, bottlenecks, and route logic to clarify the path before execution.

Product orchestrator for Prodig Suites that guides product planning, routes work to specialists, and coordinates execution across the product lifecycle. Use when the user is shaping a digital product, deciding next steps, or needs help choosing the right Prodig specialist or workflow. Triggers: 'prodig', 'digital product', 'product idea', 'product planning', 'which product agent should I use', 'SaaS planning', 'course creation', 'template pack', 'productized service'.

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.

Plan tours with routing, logistics, and promotion. TRIGGERS - Use when user needs help with tour-plan related tasks.

Routes content creation requests to the appropriate specialist skill, directing writing and brand voice tasks to content-production and planning tasks to content-strategy.

Defines vehicle routing problem types (TSP, VRP, PDP) and the data requirements needed to formulate them, without covering any API or interface details.

Plan tours with routing, logistics, and promotion. TRIGGERS - Use when user needs help with tour-plan related tasks.

Route a task to the most fitting skill or agent. Parses user intent, checks installed-skill inventory, and picks the best match (single skill or chain).

Routes security testing tasks to the correct vulnerability category, guiding recon, validation, privilege escalation, and chain building for web application and API security assessments.

Use the model-recommender skill, Workflow B (Task Router), to route the following task to the optimal model + version + effort: $ARGUMENTS.

Select alternative execution paths when a plan step fails — branch on outcomes instead of blind retry. Load when a structured plan step fails, an unexpected observation arrives, or the user asks what to try next after an error. Also triggers on "try another approach", "route around this failure", "replan on failure", "if X fails try Y", or outcome-based branching during multi-step work. Pairs with structured-planning and debug-and-fix. Does not replace root-cause debugging — adds plan-level path selection.

Routes research queries to specialist skills or runs a fallback search-and-synthesize workflow, with deterministic classification and transparent routing decisions.

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

Recommends the optimal Claude model tier (Opus, Sonnet, or Haiku) for a given task by analyzing reasoning depth, blast radius, domain expertise, output length, and correctness cost, and suggests parallelization opportunities.

Route research prompts to evidence, retrieval, scraping, data, market, or scientific research skills. Use when prompts mention deep research, current facts, citations, Exa, iterative retrieval, search-first, scraping, data pipelines, PubMed, USPTO, gget, literature review, or scholar evaluation.

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Plans a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on the issue tracker, resolved one at a time. Use when the user has a large ambiguous goal and wants the route charted.

Complexity-based task routing with Q-Learning optimization, Agent Booster WASM fast-path, and Mixture-of-Experts model selection.

Provides Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.

Route a task description to the right processkit skill, project-specific process override, and MCP tool in a single deterministic call — use this at the start of every processkit domain task.

Routes qualified leads to the right team member or sequence based on score, segment, and source. Applies configurable routing rules to assign leads to founder direct, SDR sequences, or nurture campaigns.

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 ambiguous multi-stage UI work across research, concept, Figma, implementation, and QA. Do not use for a clear leaf task.

Guide product managers through strategic roadmap planning by orchestrating prioritization, epic definition, stakeholder alignment, and release sequencing into a structured process.

Run a bounded cross-platform landscape scan before planning or implementation. Use when the real job is researching what exists, how people work around it, which solutions repeat, or how platform/tooling patterns map before deciding what to build. Produce reusable `.survey/{slug}/` artifacts, validate the artifact contract, and route planning or execution outward only after the survey is done.

Routes UI implementation or redesign to the narrowest build workflow for pages, apps, dashboards, and styled frontends.

Plan a content strategy, topic clusters, editorial roadmap, and content mix for traffic, authority, and lead generation. Use when deciding what to publish, what topics to prioritize, or how to structure a content program.

Selects the optimal LLM model and provider for each task based on complexity, cost budget, and capability requirements. Routes cheap tasks to Haiku/GPT-4o-mini and complex tasks to Sonnet/Opus/o1. Use when deciding which model to call, optimizing LLM costs, or building multi-model agent systems. Activate on "which model", "model selection", "route to model", "LLM cost", "model routing", "cheap vs expensive model". NOT for prompt engineering (use prompt-engineer), model fine-tuning, or training custom models.