capture
capture — record a passing idea without derailing the current task
The point of this skill is low friction: a thought surfaces while the user
is doing something else, and they want it recorded and out of the way in one
step — not expanded, not planned, not turned into a conversation. Capture it
faithfully, confirm in one line, and return. Do not fire a "what next"
handoff menu in capture modes; derailing the current task is exactly what this
skill exists to avoid. Only --list is interactive.
Captured items live in GitHub issues, never in local files — same
invariant as new-raw and brainstorm. This skill never edits the working
tree and never commits.
Capture is the lightest rung of the capture ladder: capture (record a
thought) → new-raw (structured requirement capture) → brainstorm (think it
through) → plan (decide how to build). A captured item is a valid input to
new-raw/brainstorm/plan later, via --list triage.