Skip to content

assess-ticket: Skip complexity assessment when progress is complete #372

Description

@williamthorsen

Problem

The assess-ticket skill always runs all four assessment dimensions (drift, relevance, progress, complexity) when mode is all. Complexity classification is forward-looking — it helps decide how to approach work. When progress is complete, the complexity assessment provides no actionable information and adds noise to the output.

Real-world example: assessing williamthorsen/node-monorepo-tools#10 produced a complexity rating that was immediately discarded when closing the ticket.

Expected behavior

When mode is all and the progress verdict is complete, skip the complexity investigation and omit the complexity section from the output.

This aligns with the existing skill design where complexity is investigated last specifically so it can benefit from prior context — it can also benefit from the knowledge that the work is already done by not running at all.

Accepted fields to change

The assess-ticket skill definition, specifically:

  • The process section for mode all should conditionally skip complexity when progress is complete.
  • The output template should omit the complexity section in that case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions