Does the Brainstorming skill write code?

No, this skill is strictly for advising, strategy, and architecture. It ensures you have a validated plan and documented consensus before moving to the implementation phase.

Can this skill analyze my existing database and code?

Yes, it leverages tools like psql and docs-manager to understand your current project constraints and data structures during the research phase.

How does 'Brutal Honesty' help my project?

By providing unfiltered feedback, the skill prevents over-engineering, unrealistic timelines, and costly architectural mistakes that might otherwise go unchallenged.

What principles does this skill use to evaluate ideas?

It operates on three core software engineering principles: YAGNI (You Aren't Gonna Need It), KISS (Keep It Simple, Stupid), and DRY (Don't Repeat Yourself).

Technical Brainstorming

Name: Technical Brainstorming
Author: hongbietcode

byhongbietcode

•

Collaboration Tools

Facilitates high-level architectural debates and principle-driven technical ideation to ensure scalable, maintainable software design.

About

The Brainstorming skill transforms Claude into a ruthless technical advisor that prioritizes long-term maintainability through the 'holy trinity' of software engineering: YAGNI, KISS, and DRY. It moves beyond simple suggestions by employing a multi-approach analysis, challenging user assumptions with brutal honesty, and evaluating multiple architectural paths using integrated research tools. By synthesizing data from existing documentation, database schemas, and industry best practices, it helps teams navigate complex trade-offs and feasibility assessments before a single line of code is written.

Key Features

Seamless transition to implementation planning via slash commands
Multi-agent debate logic for comparative solution analysis
Comprehensive discovery process using probing user questions
2 GitHub stars
Strict adherence to YAGNI, KISS, and DRY principles
Automatic generation of detailed markdown summary reports

Use Cases

Conducting feasibility assessments for complex new feature sets
Evaluating system architecture scalability and tech stack trade-offs
Identifying and mitigating technical debt through brutal honesty

About

Key Features

Seamless transition to implementation planning via slash commands
Multi-agent debate logic for comparative solution analysis
Comprehensive discovery process using probing user questions
2 GitHub stars
Strict adherence to YAGNI, KISS, and DRY principles
Automatic generation of detailed markdown summary reports

Use Cases

Conducting feasibility assessments for complex new feature sets
Evaluating system architecture scalability and tech stack trade-offs
Identifying and mitigating technical debt through brutal honesty