skills.rest
KingSharkG
KingSharkGCOMMUNITY
Explore all skills by this author →
GitHub

orchestrator-intake

Classify incoming task descriptions into five intake paths for governance routing.

Updated Apr 17, 2026
Search Tags:#workflow#governance#orchestrator#ai-automation#classify#intake#task-routing
One-click install
npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill orchestrator-intake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrator-intake
Source: https://github.com/KingSharkG/ai-agents-workflow/tree/main/skills/orchestrator-intake
Command: npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill orchestrator-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify incoming task descriptions into one of five intake paths to determine the correct governance workflow.

Core Features & Use Cases

  • Exact path classification: direct-answer, plan-only, execution-trivial, execution-simple, and execution-full to drive downstream orchestration.
  • Gate-based routing: applies stepwise governance, records decisions, and supports auditing and retries across orchestrator components.
  • Flexible use cases: suitable for AI-assisted teams needing consistent task routing, artifact creation, and escalation handling in complex projects.

Quick Start

Classify the incoming task description into one of five paths and route it through the appropriate intake workflow.

Frequently Asked Questions about orchestrator-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does AI task routing work for governance workflows?▼

AI task routing classifies incoming task descriptions into specific intake paths to apply stepwise governance, record decisions, and support auditing across orchestrator components.

What are the intake paths for classifying AI-assisted project tasks?▼

The five intake paths for classifying tasks are direct-answer, plan-only, execution-trivial, execution-simple, and execution-full, which drive downstream orchestration strategies.

How do I route incoming task descriptions to the correct execution strategy?▼

You route task descriptions by classifying them into one of five intake paths, which determines the appropriate governance workflow from direct-answer to full execution.

Can I use intake classification for complex AI automation projects requiring auditing?▼

Yes, intake classification applies across AI-assisted teams needing consistent task routing, artifact creation, and escalation handling in complex projects requiring auditing and retries.

How is orchestration state persisted during task routing?▼

Orchestration state is persisted by recording decisions and metadata in orchestration-state.json and task-data.md files during the discrete intake classification step.

When do I need path-based gating for AI automation workflows?▼

You need path-based gating when your AI-assisted projects require directive routing to specific execution strategies and discrete intake classification to ensure proper governance.

Related Skills

Explore More Product & Management Skills→
bandofaibandofai
3

Query Classification Skill

Classify customer support queries into types with urgency and routing.

Community
Intermediate
KingSharkGKingSharkG

task-packet

Automates creation of structured task packets from raw user requests.

Community
Intermediate
provenimpactprovenimpact

needs-adr

Record and manage Architecture Decision Records with lifecycle and index.

Official
Advanced
app-vitalsapp-vitals
9

entropy-fix

Queues entropy scan violations as deduplicated tasks in Shipwright's task store without opening pull requests.

Official
Advanced