openspec-explore

To explore ideas and investigate problems in a codebase, you can use a thinking partner Skill to map architecture, find integration points, and surface complexity through natural language interaction without directly implementing changes.

The best way to clarify software requirements is to brainstorm approaches and sketch tradeoffs visually using ASCII diagrams, which helps you compare potential solutions and understand the problem space before committing to an implementation.

Yes, you can use this thinking partner to visualize codebase architecture and integration points, as it supports mapping architecture and surfacing complexity through natural language interaction and ASCII diagrams.

To think through the implications of adding a new feature, you describe what you want to explore, and the Skill facilitates a deep thinking process to investigate relevant code, clarify requirements, and compare options within your software development context.

No, this codebase investigation tool operates as a non-implementing partner, meaning it focuses entirely on discovery, understanding, and exploration without directly implementing any changes to your project files.

You should not use an exploration partner when you need direct code implementation or automated file modifications, as this Skill strictly focuses on discovery, requirements clarification, and visualizing options rather than writing or applying code changes.