oracle

To plan task complexity before coding, perform a 60-second intake to score complexity 1–10 across 8 dimensions, select an optimal skill chain, and assign a model tier. This prevents starting cold on non-trivial tasks.

The best way to classify coding tasks for architecture decisions is to score complexity across 8 dimensions and select a tailored execution chain like debug, feature, refactor, architecture, or research.

You can search memory for relevant past patterns during task intake by invoking an automated planning skill that retrieves historical strategies to inform your current execution approach.

Yes, you can route work to appropriate model tiers automatically before a feature design by evaluating task complexity, assigning the correct tier, and gating with SPARC where needed.

You should not use pre-task complexity scoring for bug investigation if the issue is trivial, as this automated intake process is designed specifically to prevent starting cold on non-trivial tasks.