octocode-brainstorming

Validates ideas through multi-surface evidence research, perspective review, and structured decision briefs.

921|75|Updated Jun 5, 2025
One-click install
npx skills add https://github.com/bgauryy/octocode-mcp --skill octocode-brainstorming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: octocode-brainstorming
Source: https://github.com/bgauryy/octocode-mcp/tree/main/skills/octocode-brainstorming
Command: npx skills add https://github.com/bgauryy/octocode-mcp --skill octocode-brainstorming

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Early-stage ideas are fragile: searching only the user's first wording misses better framings, jumping to enthusiasm creates roadmap debt, and listing prior art alone never answers what to do next. This Skill gives an agent a disciplined FRAME → DIVERGE → RESEARCH → CROSS-POLLINATE → STRESS-TEST → SYNTHESIZE → DECIDE workflow so fuzzy ideas are tested against evidence before anyone commits to building.

Core Features & Use Cases

  • Divergent framing and prior-art mapping: Generates 6-10 alternative angles, then maps existing solutions across local code, GitHub repositories, packages, and web sources with strong/moderate/weak confidence markers.
  • Multi-engine web research: Consolidates results from Tavily, Serper, and Exa (with DuckDuckGo fallback), deduplicating by canonical URL and cross-confirming claims across engines.
  • Perspective stress-testing and verdicts: Runs Critical Architect, Visionary Entrepreneur, and Product lenses, concedes weak evidence, and outputs a decision such as Build RFC, Prototype First, Narrow, Park, or Do Not Build.
  • Use Case: A user asks "Is it worth building a CLI that summarizes GitHub PR discussions?" The agent reframes the idea, checks existing tools and package momentum, stress-tests the thesis, and delivers a decision brief with cited sources and one concrete next step.

Quick Start

Ask the agent to validate whether your idea is worth building, requesting prior-art research across GitHub, packages, and the web with a final build-or-park recommendation.

Frequently Asked Questions about octocode-brainstorming

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

FAQPage Schema
How do I validate a product idea before building it?

Describe the idea and ask for validation. The skill generates alternative framings, researches prior art across web, GitHub, and package sources, stress-tests the thesis through three review lenses, and returns a verdict such as Build RFC, Prototype First, Narrow, Park, or Do Not Build.

How do I map existing solutions and competitors for an idea?

Use Map mode, which expands adjacent terms and landscapes existing solutions. Each prior-art entry is scored strong, moderate, or weak based on independent sources, direct code or package data, and activity signals rather than marketing claims.

Which web search APIs does the brainstorming workflow support?

It supports Tavily, Serper, and Exa, configured via TAVILY_API_KEY, SERPER_API_KEY, and EXA_API_KEY in the Octocode home .env file. Any one key is enough; when multiple validate, all engines are queried and results consolidated, with DuckDuckGo as a no-key fallback.

Can I use this skill without web search API keys?

Yes. Without keys it falls back to DuckDuckGo, which needs no credential but returns lower-quality results, and the skill reports this as a coverage limitation. Local code, GitHub, and package research through Octocode still works independently of web keys.

When should I not use idea validation and go straight to implementation?

Skip it when you have already decided to implement a specific plan, since the skill is designed for open questions like whether something is worth building. For a decided Build verdict, hand off to an RFC generator skill instead.