brainstorming

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.

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.

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.

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.

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.

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.