Guide deep thinking and problem framing before code changes.
npx skills add https://github.com/moogah/emacs --skill opsx-explore-moogah
Please help me install this Agent Skill. Skill: opsx-explore Source: https://github.com/moogah/emacs/tree/main/.claude/skills/opsx-explore Command: npx skills add https://github.com/moogah/emacs --skill opsx-explore-moogah
Enter explore mode to think deeply, investigate problems, and clarify requirements before implementing changes.
Enter explore mode with your topic and let me think deeply, visualize ideas, and surface options without implementing anything.
High-intent search queries and answers about installing and using this skill.
To clarify requirements before coding, enter an explore mode that frames the problem space, surfaces multiple directions, and prohibits premature implementation. This approach uses deep thinking to map architecture and validate assumptions before committing changes.
Investigating a codebase for feature discovery involves mapping the architecture, finding integration points, and validating assumptions. A deep thinking exploration mode visualizes ideas with ASCII diagrams and surfaces risks without implementing code.
Yes, you can explore problem spaces and surface risks without modifying the codebase by using a mode that strictly prohibits coding. This allows you to investigate problems, visualize ideas, and surface insights for artifact creation safely.
To visualize architecture and integration points during requirements clarification, use deep thinking exploration that generates ASCII diagrams. This helps communicate ideas clearly and surfaces risks while investigating the codebase.
OpenSpec awareness helps with surfacing insights during codebase investigation by providing context for artifact creation. It ensures that deep thinking and problem framing are captured without committing code to the project.
You should avoid premature coding during product management tasks when entering feature discovery or requirements clarification. Using an exploration mode to think deeply, frame problems, and surface risks prevents premature implementation across teams and changes.
brandon-setegnExplore requirements, tradeoffs, and codebase context before implementation.
MetaCubeXVerify implementation alignment with delta specs and design artifacts.
dorrioExplore ideas, problems, and codebases through natural language and ASCII diagrams.
zonta99Transform requirements into reversible implementation plans with risk assessments.
