vibe-brainstorm

Surface diverse vibe directions and grounded convention checklists before implementation.

Updated Mar 1, 2026

Search Tags:#ideation #governance #conventions #handoff #vibe #brainstorm #mode

Ready to run

npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-brainstorm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibe-brainstorm
Source: https://github.com/adhi-jp/agent-skills/tree/main/skills/vibe-brainstorm
Command: npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams surface implicit expected behavior for vibe-enabled features, surface creative directions, and ground them in conventions before committing to implementation.

Core Features & Use Cases

Surface diverse vibe directions (Practical, Unconventional, Challenging) for a given task and capture their tradeoffs.
Provide a grounded convention checklist and gating mechanism to ensure alignment with domain rules, UX expectations, and safety boundaries.
Facilitate a clear hand-off boundary by producing a recommended direction and checklist before implementation.

Quick Start

Provide a set of divergent vibe directions and a grounded checklist for evaluation before moving to implementation.

Frequently Asked Questions about vibe-brainstorm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I brainstorm creative directions for a feature before starting implementation?▼

Brainstorming creative directions involves surfacing diverse vibe ideas—Practical, Unconventional, and Challenging—alongside their tradeoffs. This ideation process captures various behavioral directions for evaluation prior to development.

What is a convention checklist for feature ideation and when do I need it?▼

A convention checklist for feature ideation is a grounding mechanism ensuring alignment with domain rules, UX expectations, and safety boundaries. You need it when selecting a vibe direction to enforce structured governance before development.

How do I enforce a clear handoff boundary after exploring vibe directions?▼

Enforcing a clear handoff boundary after exploring vibe directions requires generating a recommended direction and a grounded convention checklist. This structured output acts as a mode-based gate defining the explicit boundary prior to implementation.

Can I use mode-based gates to check governance rules during brainstorming?▼

Yes, you can use mode-based gates to check governance rules during brainstorming. This mechanism enforces structured output and validates that creative directions align with explicit domain conventions before committing to implementation.

Does this ideation process work for exploring behavior and direction selection?▼

Yes, this ideation process works for exploring behavior and direction selection. It applies to tasks requiring exploration of behavior, capturing diverse vibe directions, and selecting a recommended path before implementation begins.