tasks-createlisted

# Creating tasks from findings Turn the findings already present in **this conversation** — a code review, a `/simplify` pass, an exploration, a design discussion — into well-formed `taskmgr` issues. This skill is the single source of truth for how a finding becomes a task: follow it, do not invent your own body shape. **Scope (optional):** anything passed after the command narrows which findings to file — read it together with step 2. $ARGUMENTS ## 1. Preconditions First, **load the `tasks` skill** for the CLI surface and the taskmgr gotchas (closure is not gated, `--description-file -`, `create --json` returns id-only) — this skill relies on them. Then confirm the tracker is usable before creating anything: run the availability check from that skill ("Is taskmgr available?") and follow its failure guidance — for a missing store, continue once `taskmgr init` has created one. ## 2. Gather the findings Collect the actionable findings from the current conversation. A finding is anything with a location, a problem, and an implied fix — a review finding, a failing check, a simplification opportunity, a flaw raised in discussion. **Honor the user's scope.** `/tasks-create` may carry an instruction ("only the critical findings", "just the auth bugs", "make chores for the cleanups"). Create tasks for exactly that subset. With no scope given, list the candidate findings and confirm which to file before writing anything. ## 3. Classify each finding by nature The *nature* of