brainstorm

Guide rough ideas into a high-level feature specification document.

2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Conava/claude-devline --skill brainstorm-conava
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/Conava/claude-devline/tree/main/skills/brainstorm
Command: npx skills add https://github.com/Conava/claude-devline --skill brainstorm-conava

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides product teams from rough ideas to a clear, high-level feature specification. It keeps the focus on what to build and how it fits into the architecture, avoiding premature implementation details.

Core Features & Use Cases

  • Guided ideation: Helps identify scope, success criteria, and high-level architecture.
  • UX and architecture awareness: Flags UI touchpoints and system interactions to guide planning.
  • Artifact generation: Produces a .devline/brainstorm.md containing the project blueprint for planners and engineers.

Quick Start

Describe your rough idea and goals, and I will generate .devline/brainstorm.md with a high-level feature specification and architecture outline.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn a rough product idea into a clear feature specification?

Feature specification for new products requires identifying scope, architecture impact, and UI touchpoints early. By using structured questions to refine requirements, teams can document key decisions and define success criteria while avoiding premature implementation details.

What is the best way to document architecture impact and UI touchpoints during product discovery?

Product discovery documentation should capture architecture impact and UI touchpoints in a structured markdown file. This artifact serves as a project blueprint, outlining scope, system interactions, and key decisions to align planners and engineers before implementation begins.

Can I use structured questions to refine requirements for high-level architecture planning?

Yes, structured questions effectively refine requirements for high-level architecture planning by systematically identifying scope and success criteria. This interactive process ensures all UI touchpoints and system interactions are considered before finalizing the feature specification.

Does guided ideation help avoid premature implementation details during feature planning?

Guided ideation prevents premature implementation details by focusing product teams on high-level scope and architecture fit. It systematically flags UI touchpoints and system interactions, ensuring teams define key decisions and success criteria before any coding begins.

What sections should be included in a feature specification for new product features?

A feature specification should include What We're Building, Architecture Impact, UI Impact, Scope, and Key Decisions sections, with optional Phases. This structured format provides a comprehensive blueprint that aligns planners and engineers on the project scope.