Explore codebases and clarify requirements without implementing changes.
npx skills add https://github.com/agoodway/goodday --skill openspec-explore-agoodway
Please help me install this Agent Skill. Skill: openspec-explore Source: https://github.com/agoodway/goodday/tree/main/.opencode/skills/openspec-explore Command: npx skills add https://github.com/agoodway/goodday --skill openspec-explore-agoodway
openspec-explore helps you think through ambiguous product or engineering problems, investigate the codebase, and clarify requirements without jumping into implementation too early.
Use case: You’re considering a change to how tasks sync or are stored, but you’re unsure whether the right move is refactoring, adjusting persistence strategy, or redesigning the user flow—use this Skill to explore the real architecture and requirements first.
Ask the AI to enter explore mode to investigate the problem space and clarify requirements without implementing changes.
High-intent search queries and answers about installing and using this skill.
To clarify ambiguous product requirements before implementation, you can use an exploration mode that investigates the codebase, maps architecture, and reframes options to surface tradeoffs without writing any application code. This keeps your team aligned on scope and guardrails early.
The best way to investigate codebase architecture during uncertain planning is to read and search existing code to map integration points and identify patterns. This thinking-only approach helps you understand the real architecture and constraints before locking in any decisions.
To compare refactoring versus redesigning a user flow without committing to code, generate multiple directions and surface tradeoffs to clarify what is at stake. This non-implementing guidance allows you to evaluate risks and unknowns while maintaining a thinking stance.
Yes, you can optionally create OpenSpec artifacts during requirement exploration without writing application code. This supports documenting design decisions and open threads while keeping the focus on clarifying scope and guardrails rather than building.
You should use exploration mode instead of directly implementing changes during ambiguous planning, mid-implementation uncertainty, or codebase investigation. It helps you identify risks, map integration points, and clarify requirements before decisions are locked.
Yes, requirement exploration supports identifying guardrails for engineering changes by surfacing risks and unknowns. It ensures you maintain the stance of thinking through the problem space and clarifying scope rather than prematurely building features.
jkitchinFacilitate structured brainstorming sessions using SCAMPER and Six Thinking Hats.
yeongjetGenerate implementation-ready proposal, design, and task artifacts in dependency order.
yukikmDocument technical architecture decisions, diagrams, and data models.
alexzhang1030Investigate codebases to clarify ambiguous product and engineering questions.
