Explore codebases and clarify requirements through read-only analysis.
npx skills add https://github.com/081595/mynode --skill openspec-explore-081595
Please help me install this Agent Skill. Skill: openspec-explore Source: https://github.com/081595/mynode/tree/main/myproject/.github/skills/openspec-explore Command: npx skills add https://github.com/081595/mynode --skill openspec-explore-081595
Explore mode helps teams and individuals think through ambiguous problems, clarify requirements, and investigate code or design options before any implementation work begins. It prevents premature commitment to solutions by enabling open-ended analysis and visual thinking grounded in repository context.
Use the openspec-explore skill to think through adding real-time collaboration to the project, map key tradeoffs, and list open questions and risks.
High-intent search queries and answers about installing and using this skill.
To brainstorm architectural tradeoffs safely, you need a read-only exploration process that maps integration points and surfaces hidden complexity from your codebase without making any code changes. This approach keeps analysis grounded in repository context.
Codebase investigation during requirements discovery involves reading and mapping relevant files to identify integration points and surface hidden complexity. This open-ended analysis prevents premature commitment to solutions by grounding the exploration in actual repository context.
Clarifying ambiguous product requirements requires conversational exploration where you ask open questions, surface tradeoffs, and reframe problems. This prevents premature commitment to solutions by enabling open-ended analysis before any implementation work begins.
Yes, you can generate visual diagrams to map design options by producing ASCII diagrams during your repository exploration. This visual thinking process is grounded in repository context and helps capture decisions before implementation.
No, exploratory thinking explicitly prohibits making code changes during investigation. It requires read-only access to repository files to ensure that open-ended analysis, brainstorming, and requirements discovery happen safely without altering the codebase.
To capture open questions and risks after brainstorming, you can list them during exploration and offer to create OpenSpec artifacts like proposals or designs when requested. This ensures decision capture follows the visual thinking and analysis phase.
JanuaryLabsExplore architecture and design options by reading repository files and OpenSpec artifacts without writing code.
luifertorresFacilitate structured exploration sessions with diagrams and OpenSpec artifacts.
Sharper-FlowMap codebase structure and identify high-risk hotspots with read-only analysis.
wtg42Explore repository ideas and clarify requirements without writing implementation code.
