task-complexity-routinglisted

# Task complexity routing Classification heuristics and routing rules for the three complexity levels defined in the agile-project workflow. The `complexity` field itself, its presence in FEATURE.md, and the DoR gate are defined in the `agile-project` skill. This skill contains the decision-making heuristics for agents who classify or re-classify work. --- ## The three levels ### mechanical Transformation whose correct result is unique or quasi-unique. Nobody needs to give an opinion on the outcome — there is an identifiable right answer. Characteristics: - No design decision involved - No new contract introduced - No invariant modified - Result can be verified objectively by tests or type checks - A single agent can produce the correct output in one pass Examples: - Rename a local variable - Extract a private function from an existing function - Add a missing test on existing code (retroactive coverage) - Fix a typo in a comment, error message, or log line - Apply a linter suggestion - Regenerate a mock after an interface change already decided - Update a dependency without API impact - Run goimports, gofmt, standard formatters Pipeline: **single-agent task**. One Opus or Sonnet with go-surgeon access and direct prompt. No PM, no Architect, no Scaffolder, no red/green split. ### standard Clear implementation of a decision already made. Several ways to code it exist, but no major architectural decision is needed. The DoD can be written precisely upfront. Character