new-raw — capture a raw requirement into a GitHub issue

This skill turns a requirement the user just described in conversation (text plus any pasted screenshots or videos) into one GitHub issue labeled tunan:raw. That issue is the durable raw source of truth for the requirement: downstream skills (brainstorm, plan) read it as input. brainstorm writes the finished, normalized requirements back into it and promotes it from tunan:raw to tunan:req — at which point it is a normalized requirement the rest of the pipeline (plan, doc-review, status) recognizes. Requirements and their state live in GitHub issues, never in local files.

This skill only creates the issue. It does not expand the requirement into acceptance criteria, run research, or write a plan — that is brainstorm's and plan's job. Keep the capture faithful to what the user actually said; do not invent scope.

Boundary with brainstorm: if the user wants to think through a vague idea, route to brainstorm directly. Use this skill when the user wants to record a stated requirement first ("capture this", "save this as a requirement", "log a req"). The issue this skill produces is a valid input to brainstorm and plan.

Invocation

/tunan:new-raw                         # default: extract from the current conversation, fast path
/tunan:new-raw <slug>                  # explicit kebab-case slug for the title
/tunan:new-raw --kind=feature|bug|chore  # explicit kind; default auto-detected, else feature
/tunan:new-raw --priority=P0|P1|P2     # explicit priority; default P2
/tunan:new-raw --align                 # ask at every soft decision via align
/tunan:new-raw --dry-run               # print the title + body + asset list, create nothing