planning-task-classifier

Determine the task type and what matters most for that type Reduce planning mistakes (e.g., planning a bug like a feature) Short task description Artifacts: logs/errors/AC/screenshots/incident links There is "expected vs actual" There is an error/crash/regression/incident There is a repro or conditions under which it occurs Confirm the repro Minimal fix Fast rollback </planning_focus> New functionality/behavior User value and acceptance criteria (AC) Clear AC and edge cases In/out-of-scope boundaries Rollout and monitoring </planning_focus> Goal: quality/maintainability/performance without changing external behavior There are metrics/pain/debt Preserve behavior Improvement metrics Incremental steps and regression coverage </planning_focus> Schema/data/contracts/infra change in a way that requires compatibility There is data volume/windows/dual-write/backfill Data integrity Backward compatibility Step-by-step migration and verification </planning_focus>

Task type + confidence

Why (signals)

Planning focus

Key unknowns

</output_format> Task type is justified by signals from the input If confidence is low, state it explicitly and list questions </quality_rules>