skills.rest
nebius
nebiusOFFICIAL
Explore all skills by this author →
WebsiteGitHub

brainstorm

Explores ideas in chat using source-ranked context before implementation begins.

7|5|Updated Jul 22, 2025
Search Tags:#brainstorming#architecture decisions#pre-implementation#tradeoff analysis#technical strategy#design exploration#source priority
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill brainstorm-nebius
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/brainstorm
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill brainstorm-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often jump into implementation before validating assumptions or gathering the right context, leading to rework and poor design decisions. This Skill structures pre-implementation discussions by gathering only decision-relevant evidence from the repository, internal sources, and vendor docs, then separating facts from hypotheses. ## Core Features & Use Cases - Source-ranked context gathering: Searches the current project first, then sibling folders, related skills, internal knowledge bases, and official vendor documentation, escalating only when a named gap remains. - Assumption challenging and option comparison: Separates facts from hypotheses, presents 2-4 options with tradeoffs, and lists open questions that would change the recommendation. - Advisory skill consultation: Consults design and system-design-rules skills for major architecture decisions, and uses bounded research only for unresolved recommendation-changing source conflicts. - Use Case: Before migrating a service to a new cloud provider, use this Skill to compare migration options against repo evidence and official vendor docs, surface risks, and decide whether the discussion is ready for a design or planning handoff. ## Quick Start Ask the agent to brainstorm whether migrating the authentication service to a managed identity provider is a good idea, gathering relevant repo and vendor context first.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I brainstorm a technical design before writing code?▼

Invoke the skill with your topic or question, and it restates the problem, builds a source plan, and gathers relevant context from your repo, internal docs, and vendor documentation. It returns options with tradeoffs, labeled assumptions, and open questions without editing any files.

What sources does an evidence-first brainstorming workflow check?▼

It checks sources in priority order: the current project folder, sibling project folders, related installed skills, internal knowledge like Confluence or Jira, and finally official vendor documentation. Each source is only opened when it can answer a specific question or close a named gap.

Can brainstorming skills edit code or create tickets during discussion?▼

No, this skill is strictly read-only and chat-only during brainstorming. If you pivot to implementation, documentation, tickets, or commits, it summarizes the discussion and hands off to the appropriate workflow skill first.

When should I use research instead of brainstorming?▼

Use research only when a source conflict materially changes the recommendation and source-priority rules cannot resolve it. Brainstorming handles option exploration and assumption challenging; research is a bounded follow-up for that exact conflict, not the default.

How are conflicting sources resolved during technical brainstorming?▼

Conflicts are resolved by preferring current project behavior for repo-specific contracts and official vendor docs for external product behavior. The skill states the conflict, what was preferred, and what remains uncertain, escalating to bounded research only if the conflict changes the recommendation.

Related Skills

Explore More Software Engineering Skills→
ryanallenryanallen

research

Crawl linked pages and organize findings into a structured README.

Community
Advanced
randoneeringrandoneering

writing-plans

Convert a spec into an executable implementation plan with tasks and tests.

Community
Advanced
michaelalbermichaelalber
2

architecture-review

Review software architectures against quality attributes using the CACR loop.

Community
Advanced
SoloXLabSoloXLab

exploration-logger

Document exploratory research spikes and experiments in a structured issue log.

Official
Intermediate