vibe-brainstormlisted

Comprehensive brainstorming workflow for turning any app idea into a clear, validated, buildable brief. Two paths: personal project (8 steps) and client/business project (13 steps). Fast path for fully-formed ideas. Detects agentic/AI projects and routes to agent: before architect:. Pre-write quality check ensures BRIEF.md has specific users, measurable success criteria, explicit non-goals, and a clear v1 boundary before writing. Complexity sizing (S/M/L/XL) signals build effort to downstream skills. BRIEF.md is structurally consistent — architect:, new-app:, change-spec:, and review: all read known field names. Does not create code or project structure — thinking and brief only. Step 0 INGESTS an idea produced elsewhere (pasted text, or a dropped file — canonical BRIEF.md, an arbitrary idea doc, or an empty/sparse file) and normalizes it to a canonical BRIEF.md so it reaches parity and flows through the full downstream pipeline (architect → scaffold → design → build) instead of skipping steps. Triggers on "b
aakashdhar/vibe-skill · ★ 7 · AI & Automation · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe Brainstorm Skill v2 Turns a fuzzy idea into a clear, validated, buildable brief. Asks the right questions. Surfaces unknowns. Prevents mid-build surprises. Personal projects: 15-20 minutes. Client/business projects: 25-35 minutes. Every minute here prevents hours of rework later. **Always run in Plan Mode (Shift+Tab). No code. No project files.** > **Autonomous / headless mode.** At startup resolve the settings with > `python3 ~/.claude/skills/vibe-mode/scripts/vibe_state.py mode`. If `vibe_mode` is > `autonomous`, every "wait", "ask", "confirm" and approval step in this skill follows > vibe-mode's `references/HEADLESS.md` §2 instead: take the recommended option, accept your > own draft after one self-check, log each choice to `vibe/DECISIONS.md`, never ask the > user, and stop — writing `vibe/.run_state.json` — only when a person is genuinely required. --- ## The O'Reilly principle this serves Spec before code — and brief before spec. The brief is where the hardest thinking happens: what is the real problem, who has it, what does v1 genuinely need. Every question skipped here becomes a scope change mid-build. --- ## What's new in v2 - **BRIEF_MD.md template** — structurally consistent output that all downstream skills parse reliably - **Pre-write quality check** — catches weak user descriptions, unmeasurable criteria, missing non-goals before writing - **Non-goals as a first-class step** — not optional, always included - **Agentic detection** — detects AI/ag