workflowslisted

# Workflows for AI-assisted development ## Table of contents - [Complexity detection](#complexity-detection) - [LOW complexity (Quick Fix)](#low-complexity-quick-fix) - [MEDIUM complexity](#medium-complexity) - [HIGH complexity](#high-complexity) - [Problem type routing (Quick Reference)](#problem-type-routing-quick-reference) - [Branch strategy](#branch-strategy) - [Why this matters](#why-this-matters) - [Recommended procedure](#recommended-procedure) - [Tracking info in documentation](#tracking-info-in-documentation) - [The spec workflows](#the-spec-workflows) - [Summary](#summary) - [See also](#see-also) --- ## Complexity detection **Principle:** Match the scope of the documentation to the complexity of the task. **Grading rule:** The grade is the highest band Operation, Keywords or API impact reaches; Number of files is read last, as a signal, never a fourth vote, and never enough by itself to move a spec the other three read as LOW. Worked example: a wording fix replacing one string across an implementation file and its test — Operation is fix/replace (LOW), Keywords name the specific files (LOW), API impact is none (LOW). Touching four files sits inside the MEDIUM file-count range, but that range is not a vote, so the grade stays LOW. ### LOW complexity (Quick Fix) **Characteristics:** - The description mentions **one specific file** - Simple operations: "remove", "replace", "correct", "update", "fix" - Typically touches 1-5 files — the file itself,