Quick Wins — find AI-friendly issues to knock out

Use this skill when the user wants to power through a batch of small issues. The goal is to identify issues where:

1. The spec is already done — root cause, file paths, or implementation hints are in the issue body
2. The blast radius is small — touches one logger / one command / one screen, not architecture
3. A human can verify in <2 minutes — clear "do X, see Y" check
4. Failure mode is obvious — if it breaks, you'll see it immediately (not a slow data corruption)

Workflow

Step 1 — list candidate issues

Pull all 2-todo issues with their size/complexity:

obsidian base:query vault=nvALT path="Simple History issues.base" format=json \
  | jq '[.[] | select(.status == "2-todo") | {name, prio, type, size, complexity}]'