workflow-selection

Name: workflow-selection
Availability: InStock
Author: Zate

Guide users to select Feature, Bug Fix, Refactor, or QA workflows via a decision tree.

9|2|Updated Dec 5, 2025

Search Tags:#workflow #task management #refactoring #bug fix #feature development #QA #development process #process optimization

Ready to run

npx skills add https://github.com/Zate/cc-plugins --skill workflow-selection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-selection
Source: https://github.com/Zate/cc-plugins/tree/main/plugins/devloop/skills/workflow-selection
Command: npx skills add https://github.com/Zate/cc-plugins --skill workflow-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Selecting the optimal development workflow for a given task can be ambiguous, leading to inefficient processes, wasted effort, and suboptimal outcomes. This Skill guides you to the most effective approach.

Core Features & Use Cases

Workflow Decision Tree: A clear guide to choose between Feature, Bug Fix, Refactor, or QA workflows.
Phase Breakdowns: Detailed phases for each workflow, including primary models and fallback strategies.
Task Classification Indicators: Keywords and questions to accurately classify tasks and avoid ambiguity.
Use Case: Determine if a task requires a full feature development workflow, a streamlined bug fix process, or a focused refactoring approach.

Quick Start

Help me choose the best development workflow for a task that involves improving existing code without changing its behavior.

Frequently Asked Questions about workflow-selection

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

FAQPage Schema

How do I choose the right development workflow for my task?▼

Choose a development workflow by classifying your task type: feature development for new functionality, bug fixes for existing issues, refactoring for code improvement without behavior change, or QA for testing. Use the workflow decision tree to map task characteristics to the optimal approach, then follow the identified phase sequence and indicators.

What's the difference between a bug fix workflow and a refactoring workflow?▼

A bug fix workflow addresses broken functionality with a streamlined process focused on root cause and verification. A refactoring workflow improves existing code structure and maintainability without changing behavior, using a more exploratory phase sequence optimized for code quality.

How do I know if a task is a feature, bug fix, refactor, or mixed workflow?▼

Task classification uses keywords and diagnostic questions: features add new behavior, bug fixes resolve defects, refactors restructure code without behavior change, and QA validates functionality. Mixed tasks combine multiple workflow types; use decision tree indicators to identify primary and secondary workflow components.

Can I apply multiple workflows to a single task?▼

Yes. Mixed tasks combine multiple workflow phases—for example, fixing a bug while refactoring surrounding code. The workflow decision tree identifies which workflows apply, their sequence, and integration points to optimize the overall development process.

What information do I need to select the right workflow?▼

Identify task characteristics: the problem statement, scope (new vs. existing code), acceptance criteria, and whether behavior should change. The skill applies classification indicators and phase breakdowns to map these inputs to feature, bug fix, refactor, or QA workflows with model strategies and fallback approaches.

When should I use a QA workflow instead of development workflows?▼

Use a QA workflow when the primary task is validation and quality assurance rather than code changes. QA workflows focus on testing, defect discovery, and verification phases, distinct from feature development, bug fixes, or refactoring workflows.