TWISTEdBRACKETS

Skill

Brainstorming

Think through an idea with a trusted colleague before building. Writes design specs.

// workflow;

Behaviour

What it does

  • Scans project context and reflects back what it sees
  • Asks one focused question at a time
  • Flags oversized scope and suggests where to start
  • Surfaces hidden assumptions and runs a quick pre-mortem
  • Proposes 2–3 approaches with honest trade-offs
  • Presents the design in sections and revises until you agree
  • Saves an approved spec to docs/designs/
  • Hands off to technical-documentation when ready

When to use

Good fits

Starting a new feature, product, or project

Requirements feel fuzzy or keep shifting

You want to talk through options before committing

Before planning or coding anything non-trivial

Development harness

Step 1 of 8 · Design

Part of the design-to-ship pipeline: brainstorming → technical-documentation → conformance-check → reconciling-changes → planning → project-setup → executing-plans → shipping. Install the full set for structured feature work.

Test-Driven DevelopmentEnd-to-End TestingComponent DevelopmentComponent Testing
Technical Documentation

Install

Get this skill

Uses Agent Kit via npx; no global install required.

Quick install

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill brainstorming

Global (Cursor)

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill brainstorming --global --agent cursor

Global (Claude)

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill brainstorming --global --agent claude

Project install

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill brainstorming --project

Interactive install

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills

Uninstall

sh
npx @levi-putna/agent-kit@latest remove brainstorming

Example

Example prompt

Brainstorming

I want to add a notification system to my app. Help me think through it before we build anything.

Flow

How the skill works

  1. Get oriented in the project context
  2. Find the real goal: who has the problem and what success looks like
  3. Check scope and decompose if the idea is too large
  4. Surface assumptions and explore 2–3 genuine approaches
  5. Shape the design section by section until approved
  6. Run a quick pre-mortem before locking in
  7. Write the spec to docs/designs/ and hand off to technical-documentation