discuss-for-specs

This Skill facilitates structured discussions to clarify ideas and explore solutions before technical specification. It uses Socratic questioning and devil's advocate challenges to drive decision-making, operating with a strict discussion-first principle that prioritizes guided thinking over immediate output generation.

The best way to explore architectural trade-offs is through managed discussion state tracking that captures decisions and maintains context. By proactively challenging assumptions and presenting alternative viewpoints, this approach ensures no details are lost and reduces cognitive load during feature design.

Yes, you can use Socratic questioning to manage discussion state and track decisions. The process guides users to clarify their thoughts while capturing confirmed decisions and maintaining context, ensuring a structured progression from initial ideas to finalized specifications.

Facilitate collaborative problem solving by adopting a discussion-first principle that prioritizes guided thinking. Link concepts across different fields to enrich understanding and precipitate confirmed decisions through devil's advocate challenges, deliberately delaying immediate output generation.

You need a structured discussion process before technical specification when designing new software features or systems like a caching mechanism. It helps address cognitive load challenges by ensuring high-quality specifications through in-depth conversations that clarify ideas and explore solutions.