← All runbooks
roin-orca / simple

Fun Brainstorming

Invoke before any creative or architectural work — feature design, component creation, or behavioral changes. A streamlined brainstorming process optimi

agent claude-codemodel claude-sonnet-4-6snapshot python312-uveval programmatic9 stepsv1.0.0

Deploy Fun Brainstorming to your jetty.io

One-click installs this runbook into a collection on your Jetty account. You can run it from the Spot dashboard, schedule it, or pipe inputs in via the API.

Deploy on jetty.io →View source
The shape of the run

9 steps · start to finish.

  1. 1
    Step 1

    Environment Setup

    ▶

    Create the output directory and verify the task description is provided.

    echo "=== Simple Brainstorming Setup ==="
mkdir -p /app/results

# Verify task description is available
if [ -z "$TASK_DESCRIPTION" ]; then
  echo "ERROR: TASK_DESCRIPTION is not set. Provide a description of the task to brainstorm."
  exit 1
fi
echo "Task: $TASK_DESCRIPTION"
echo "Results dir: /app/results"
echo "Setup complete."
  2. 2
    Step 2

    Discover -- Understand the Task

    ▶

    Assess the project context: codebase conventions, existing patterns, and relevant constraints. Ask **at most 3 focused clarifying questions** (prefer multiple-choice). Batch related questions together in a single message. If the request is already clear, skip straight to Step 3.

  3. 3
    Step 3

    Propose -- Present Two Approaches

    ▶

    Present exactly **2 approaches** with trade-offs. Lead with your recommendation and explain why. Keep each option to a short paragraph. Scale detail to the task: a few sentences for simple work, more reasoning for complex decisions.

  4. 4
    Step 4

    Converge -- Get Explicit Approval (max 2 rounds)

    ▶

    Present the proposal and wait for explicit user approval. If rejected, revise and repropose. **max 2 revision rounds**. If still not aligned after 2 rounds, ask the user to state what they want directly.

  5. 5
    Step 5

    Capture -- Record the Chosen Direction

    ▶

    Write the approved direction to `/app/results/direction.md`:

  6. 6
    Step 6

    Implement -- Begin Building

    ▶

    Only after `/app/results/direction.md` has been written and the user has explicitly approved: begin implementation. Reference the direction document throughout to stay on track.

  7. 7
    Step 7

    Iterate on Errors (max 3 rounds)

    ▶

    If any validation check fails:

  8. 8
    Step 8

    Write Executive Summary

    ▶

    Write `/app/results/summary.md`:

  9. 9
    Step 9

    Final Checklist (MANDATORY -- do not skip)

    ▶

    echo "=== FINAL OUTPUT VERIFICATION ===" RESULTS_DIR="/app/results" for f in \ "$RESULTS_DIR/summary.md" \