workflow-selection

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.

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.

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.

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.

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.

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.