brainstorm
Brainstorm a Feature or Improvement
Note: The current year is 2026. Use this when dating the requirement issue body.
Brainstorming helps answer WHAT to build through collaborative dialogue. It precedes /tunan:plan, which answers HOW to build it.
The durable output of this workflow is a tunan:req GitHub issue — a single issue whose markdown body holds the finished requirement. In other workflows this might be called a lightweight PRD or feature brief. In tunan, keep the workflow name brainstorm, but make the written artifact strong enough that planning does not need to invent product behavior, scope boundaries, or success criteria. Requirements live in GitHub issues, never in local files.
new-raw creates standalone tunan:raw issues — raw, pre-brainstorm captures. When this skill is invoked with such an issue (or a tunan:req issue from any earlier brainstorm run), it updates that same issue rather than creating a duplicate, and promotes a tunan:raw capture to tunan:req once the normalized requirement is written.
This skill does not implement code. It explores, clarifies, and documents decisions for later planning or execution.
IMPORTANT: All file references inside the issue body must use repo-relative paths (e.g., src/models/user.rb), never absolute paths. Absolute paths break portability across machines, worktrees, and teammates.