workflow

Route development tasks to specialized sub-workflows based on intent detection.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fernando-fernandez3/claude-code-resources --skill workflow-fernando-fernandez3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/fernando-fernandez3/claude-code-resources/tree/main/my-config/skills/workflow
Command: npx skills add https://github.com/fernando-fernandez3/claude-code-resources --skill workflow-fernando-fernandez3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Workflow Skill provides a unified entry point that automatically routes development tasks to the most appropriate sub-workflow based on intent detection, reducing manual triage and speeding up task resolution.

Core Features & Use Cases

  • Intent-based routing: Detects task intent and routes to the matching sub-skill such as /issue --quick, /feature, /debug, /analyze, or /tdd.
  • Extensibility: Supports additional sub-skills and plugins to cover more domains like frontend, review, or testing.
  • Use Case: For example, given a task like "Fix the typo in utils.py," it routes to the quickest applicable path; for more complex planning, it routes to /issue --plan.

Quick Start

Use /workflow <task description> to begin routing to the appropriate sub-workflow.

Frequently Asked Questions about workflow

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

FAQPage Schema
How do I automate routing for development tasks to the right sub-workflow?

Automating development task routing requires intent detection to map task descriptions to specialized sub-workflows. This skill evaluates keywords and complexity to direct issues, features, or debugging tasks to matching sub-skills like /debug or /feature automatically.

How does intent detection work for software engineering workflows?

Intent detection for software engineering workflows works by evaluating task descriptions against a decision table. It analyzes keywords and complexity to identify the task type, routing it to the appropriate sub-workflow such as /issue --quick or /tdd.

What is the best way to triage quick fixes versus complex feature requests?

Triage of quick fixes versus complex feature requests is managed by assessing task complexity. Simple tasks like typo fixes route to /issue --quick, while complex planning routes to /issue --plan, ensuring tasks reach the correct workflow.

Can I manually override the sub-workflow selected for a development task?

Manual override of the selected sub-workflow is supported. The routing logic includes user override guidance, allowing developers to bypass automatic intent detection and directly invoke a preferred sub-skill like /review or /analyze.

Does workflow routing support adding new sub-skills for code reviews and testing?

Workflow routing supports adding new sub-skills for code reviews and testing. The system is extensible, allowing additional plugins and sub-skills to cover more domains like frontend development and testing.