raisedadead/adhoc-brainstorm

Ad-Hoc Brainstorm

Lightweight structured decision skill. Walks through a list of items one at a time, presenting context and options for each. No tracker state, no spec pipeline, no stage machine.

Step 1: Identify Items

If the user provided items in args or conversation → use them. Otherwise → ask: "What items do you want to brainstorm? Provide a list, a file path, or describe the topic."

Parse into a numbered list of discrete items to decide on.

Step 2: Walk Through One Item at a Time

For each item:

1. Present context — what is this item, why it matters, what the current state is. Keep it to 3-5 lines.
2. Present options via AskUserQuestion — typically: Keep / Relax / Modify / Remove. Add a recommendation with rationale.
3. Capture the decision — record the user's choice before moving to the next item.
4. Move on — do not revisit unless the user asks.

One item per message. Do not batch. Do not skip ahead.

Step 3: Summary

After all items are decided, present a decision summary table:

| # | Item | Decision | Notes | | --- | ---- | -------- | ----- |

Then ask: "All items decided. Want to act on these now, or save for later?"

Principles

• The user drives — you present, they decide
• One item at a time — no batching, no skipping
• No assumptions — if you're unsure about the recommendation, say so
• No pipeline — this is a conversation, not a stage machine
• No tracker state required — works in any project