do

Route user intent to orchestrators or skills via pattern and complexity checks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mferris77/SpringBoard --skill do-mferris77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do
Source: https://github.com/mferris77/SpringBoard/tree/main/vscode-citadel-harness/skills/do
Command: npx skills add https://github.com/mferris77/SpringBoard --skill do-mferris77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users often don't know which orchestrator or skill should handle a request and risk over- or under-allocating resources; this Skill automatically determines the cheapest capable path and routes intent to the correct handler so users can ask for work without knowing internal tooling.

Core Features & Use Cases

  • Multi-tier classification: Zero-cost pattern checks, active-state short-circuits, keyword skill matching, and an LLM complexity classifier decide routing from direct edits to fleet campaigns.
  • Registry discovery & proportionality: Lightweight skill registry checks, proportionality downgrades/upgrades, and trust-level gating ensure safe, minimal, and context-appropriate orchestration.
  • Operational safety & observability: Telemetry logging, explicit escape hatches for direct invocation, graceful handling of missing state or resources, and clear fallback rules (default to marshal) prevent failures and surprising behavior.

Quick Start

Ask the harness to handle a vague task by saying: /do fix the login bug in the authentication flow.

Frequently Asked Questions about do

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

FAQPage Schema
How does intent routing work for task orchestration?

Intent routing automatically classifies task complexity, scope, and persistence using pattern matching and LLM classifiers to direct requests to the most appropriate orchestrator or skill for execution.

What's the best way to automate routing requests to different orchestrators?

Automated routing evaluates active-state conditions, skill keyword lookups, and proportionality checks to select the cheapest capable execution path, defaulting to a safe fallback when targets fail.

How do I ensure safe skill discovery without over-allocating resources?

Safe skill discovery uses a lightweight registry lookup with trust-level gating and proportionality downgrades to ensure minimal, context-appropriate orchestration that prevents over-allocation.

Can I bypass automated classification and directly invoke a specific orchestrator?

Yes, the system provides explicit escape hatches allowing you to bypass automated intent routing and directly invoke a specific handler or orchestrator when needed.

What happens when intent routing fails to find a matching skill or resource?

When intent routing fails to find matching resources or targets fail, the system applies graceful handling rules and defaults to a safe fallback orchestrator to prevent execution failures.