brainstorming

Enrich creative code brainstorming with git-based technical debt and hotspot signals.

11|3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill brainstorming-artk0de
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude-plugin/dinopowers/skills/brainstorming
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill brainstorming-artk0de

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of AI agents brainstorming code changes based on superficial similarity, which often leads to ignoring technical debt, ownership silos, and bug-prone hotspots.

Core Features & Use Cases

  • Risk-Aware Exploration: Automatically enriches brainstorming sessions with git-based signals like churn, bug-fix rates, and authorship.
  • Contextual Prioritization: Identifies architectural hubs and legacy debt zones to ensure design proposals respect the codebase's structural integrity.
  • Use Case: When refactoring a complex authentication module, the skill highlights which files are high-churn hotspots and which developers are the primary owners, preventing the agent from suggesting changes that would destabilize the system.

Quick Start

Invoke the brainstorming skill to discuss a refactor of the user authentication module while incorporating tea-rags risk signals.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I incorporate git history into code refactoring brainstorming?

Code refactoring brainstorming incorporates git history by analyzing churn rates, bug-fix frequencies, and authorship data. This risk-aware approach identifies architectural hubs and legacy debt zones, ensuring design proposals respect structural integrity and prevent destabilizing changes.

What is git-based technical debt analysis for software design?

Git-based technical debt analysis for software design enriches brainstorming sessions with repository-specific risk metrics. It evaluates bug-prone hotspots and ownership silos, preventing AI agents from suggesting changes that ignore the codebase's accumulated structural issues.

Does this refactoring brainstorming approach work with complex monorepos?

Refactoring brainstorming with git signals works with complex monorepos by retrieving repository-specific risk metrics. It identifies high-churn hotspots and primary developer ownership within the monorepo, guiding architectural proposals to respect the codebase's structural integrity.

Do I need an MCP server to analyze code hotspots during feature planning?

Analyzing code hotspots during feature planning requires integration with the tea-rags MCP server. This server retrieves and analyzes repository-specific risk metrics like churn and bug-fix rates before generating architectural proposals.

Why does AI generated code design ignore technical debt and ownership silos?

AI generated code design often ignores technical debt and ownership silos because agents brainstorm based on superficial code similarity. Integrating git-based signals for churn and authorship grounds the creative process in real repository risk metrics.