feature-dispatch

Routes non-trivial feature requests to the appropriate feature-storm or feature-design entry skill.

Updated May 26, 2026
One-click install
npx skills add https://github.com/cagriy/dev-skills --skill feature-dispatch-cagriy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-dispatch
Source: https://github.com/cagriy/dev-skills/tree/main/skills/feature-dispatch
Command: npx skills add https://github.com/cagriy/dev-skills --skill feature-dispatch-cagriy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a user describes a new feature in plain conversation, it is easy to jump straight into code without scoping or design, producing bloated or misaligned implementations. This Skill watches the user's latest message, detects feature-shaped work that plausibly exceeds ~75 lines of code, and recommends the right entry point into the feature development chain before any code is written. ## Core Features & Use Cases - Scope estimation: Silently estimates the implementation size of the request and skips dispatch for small fixes, renames, doc edits, or explicitly throwaway work. - Entry-point recommendation: Chooses between /feature-storm for vague, product-level requirements and /feature-design for clear requirements needing technical design. - Single-question routing: Presents one AskUserQuestion with the recommended skill, the alternative, and a continue-without-dispatch option, then hands over via the Skill tool. - Use Case: A user writes "Add reminders to the todo app." The Skill detects non-trivial feature work, recommends /feature-storm, and on acceptance invokes it with the original request. ## Quick Start Describe a new feature you want to build in a normal message, and the dispatcher will offer to route you into the right feature planning skill.

Frequently Asked Questions about feature-dispatch

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

FAQPage Schema
How do I route a feature request into a design workflow before coding?

Describe the feature in a normal message and the dispatcher evaluates whether it exceeds roughly 75 lines of first-cut code. If so, it asks once whether to run feature-storm for vague requirements or feature-design for clear ones, then hands over automatically.

What is the difference between feature-storm and feature-design?

feature-storm fits vague, high-level requirements that still need product-layer scoping such as goals, users, and success criteria. feature-design fits requests that are clear at the product layer but still need technical decisions like data models, interfaces, and failure modes.

When does the feature dispatcher skip a request silently?

It skips small work such as renames, one-line fixes, doc edits, dependency bumps, and config tweaks, plus anything the user framed as quick, throwaway, or a spike. It also skips when a feature or bug slash command was already typed or a chain is already in flight.

Can the dispatcher write code or modify files itself?

No. It is a pure router whose only side effects are one AskUserQuestion call and one Skill invocation. It never reads files, writes files, runs commands, or chains past the handover to the target skill.

What happens if I decline the dispatch recommendation?

Selecting continue without dispatch stops the skill silently and the parent conversation proceeds normally. The dispatcher never retries, re-frames, or follows up after a decline.