brainstorming

Explore ideas and clarify requirements by reading project context files.

3|Updated Apr 20, 2026

Search Tags:#brainstorming #codebase #requirements #exploration #diagrams #thinking-partner

Ready to run

npx skills add https://github.com/mor-duongmh/morkit-plugin --skill brainstorming-mor-duongmh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/mor-duongmh/morkit-plugin/tree/main/plugins/morkit/skills/brainstorming
Command: npx skills add https://github.com/mor-duongmh/morkit-plugin --skill brainstorming-mor-duongmh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode as a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Core Features & Use Cases

Provides a non-implementing exploration stance and helps surface questions, map problem spaces, and read project context files.
Visual, adaptive thinking guidance with ASCII diagrams to clarify ideas.
Supports following user-led threads, surfacing multiple directions.

Quick Start

Tell me to enter explore mode and begin thinking through a change proposal.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I explore ideas and clarify requirements before implementing code changes?▼

To explore ideas and clarify requirements before implementation, you need a thinking partner that reads your codebase and surfaces questions without writing features. This approach maps problem spaces and investigates changes adaptively before any code is deployed.

Can I generate diagrams to map problem spaces during project exploration?▼

Yes, you can generate diagrams to map problem spaces during project exploration. Visual guidance using ASCII diagrams clarifies ideas and structures complex technical relationships while you think through proposed changes.

What is the best way to investigate a codebase without modifying files?▼

The best way to investigate a codebase without modifying files is adopting a non-implementing exploration stance. This reads project context to surface questions and map problem spaces, ensuring no features are written or deployed during the investigation.

Does this requirements exploration approach support creating morkit artifacts?▼

Yes, this requirements exploration approach supports creating morkit artifacts. While acting as a thinking partner to investigate problems and follow user-led threads, it generates these artifacts upon request to document the exploration process.

When should I use a thinking partner for brainstorming instead of writing code?▼

You should use a thinking partner for brainstorming instead of writing code when you want to think through a change before or during implementation. It helps clarify requirements and surface multiple directions prior to committing to feature deployment.

How does a thinking partner help with clarifying project requirements?▼

A thinking partner helps with clarifying project requirements by reading context files and following user-led threads to surface relevant questions. It provides adaptive guidance to map the problem space and visualize ideas without writing any features.