ask-red

Routes operator requests to the appropriate RedSkills workflow command.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill ask-red-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-red
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/engineering/ask-red
Command: npx skills add https://github.com/reddb-io/red-skills --skill ask-red-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? RedSkills ships dozens of slash commands across planning, execution, review, and operations, and remembering which one fits a given situation is hard. This Skill acts as a router: it classifies the current situation and returns the smallest useful flow of commands to run, in order. ## Core Features & Use Cases - Situation classification: Routes work by repository ownership and working mode (interactive, ADR-editing, spec-driven, ad-hoc) before naming a command. - On-ramp routing: Maps common situations — incoming bugs, parked human decisions, manual implementation slices, validation, daemon status, design uncertainty — to the right entry command such as /afk, /go, /triage, /hitl, or /diagnose. - Structured route answers: Returns a route in the form /first -> /second -> /final with the starting command, a one-sentence rationale, and the handoff condition for the next step. - Use Case: An operator asks "a reproducible bug just came in, what do I run?" and receives the route /diagnose -> /triage -> /afk with the condition that must hold before each handoff. ## Quick Start Ask which RedSkills flow fits your current situation, for example what command to run for a new bug report or a parked ticket.

Frequently Asked Questions about ask-red

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

FAQPage Schema
How do I know which RedSkills command to run?▼

Ask the router with your current situation. It classifies the work by working mode and on-ramp, then returns the smallest useful flow naming the first command, why it fits, and the handoff condition for the next command.

What is the difference between /afk and /go in RedSkills?▼

/afk is the spec-driven default lane for tracked work that is or should be a Ticket. /go dispatches one concrete ad-hoc demand that does not belong on the tracker, returning a Worker stamped current.kind=go.

How do I route a reproducible bug report?▼

A bug you can reproduce or diagnose now routes to /diagnose. If the user is only reporting a bug for later, the router sends it to /report-bug instead, and executable ticket readiness goes through /triage then /afk.

When should a parked ticket go to /hitl versus /retake?▼

A parked human decision routes to /hitl. If the blocker is already resolved and the Ticket only needs queue promotion back to ready-for-agent, /retake is the correct route instead.

Does the router cover skills from other plugins?▼

It covers every published dev skill and includes a cross-plugin route for corpus knowledge-graph requests, which belong to the memory plugin surfaces such as /memory:ingest and /memory:view. LLM Wiki routes also ship with memory, not dev.