skills.rest
evandrodevbr
evandrodevbrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-explore

Explore and clarify software development problems before implementation.

1|Updated Apr 22, 2026
Search Tags:#architecture#requirements#codebase analysis#exploration#openspec#software planning
One-click install
npx skills add https://github.com/evandrodevbr/GeminiNexus --skill openspec-explore-evandrodevbr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/evandrodevbr/GeminiNexus/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/evandrodevbr/GeminiNexus --skill openspec-explore-evandrodevbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users clarify ideas, investigate software problems, and reason through potential changes before implementation by providing an adaptive exploration partner.

Core Features & Use Cases

  • Problem Exploration: Helps analyze vague ideas, challenge assumptions, and uncover requirements through guided discussion.
  • Codebase Investigation: Supports architectural exploration, dependency discovery, and identification of integration points without modifying code.
  • Decision Support: Compares approaches, visualizes tradeoffs, and captures OpenSpec-related thinking for software planning scenarios.

Quick Start

Use the openspec-explore skill to help me investigate a proposed software change and identify possible approaches before implementation.

Frequently Asked Questions about openspec-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a codebase before implementing new software changes?▼

Codebase analysis before implementation involves investigating dependencies, identifying integration points, and evaluating technical approaches. Structured exploration clarifies vague requirements and uncovers architectural impacts without modifying existing code.

What is structured problem exploration in software architecture planning?▼

Structured problem exploration is an adaptive investigation process that challenges assumptions and guides requirement discovery through reasoning. It applies to architecture discussions and evaluating technical approaches during change planning.

How do I discover software requirements through guided discussion?▼

Requirement discovery through guided discussion analyzes vague ideas and challenges assumptions to uncover hidden needs. This adaptive exploration partner captures thinking artifacts to clarify software planning scenarios.

Can I compare technical approaches and visualize tradeoffs before writing code?▼

You can compare technical approaches and visualize tradeoffs during change planning through structured decision support. This reasoning process evaluates architectural options and captures planning artifacts without enforcing implementation workflows.

When should I not use non-implementation exploration workflows for software planning?▼

Non-implementation exploration workflows should not be used when direct code modification or immediate execution is required. This approach focuses strictly on reasoning, dependency discovery, and architectural evaluation before actual development begins.

Related Skills

Explore More Software Engineering Skills→
balic-AI-ML-R-D-Resourcesbalic-AI-ML-R-D-Resources

security-audit-context-building

Map architecture, trust boundaries, and data flows for security audit scoping.

Official
Advanced
royhenengelroyhenengel

notion-spec-to-implementation

Transform product and technical specifications into actionable Notion implementation plans and tasks.

Community
Advanced
haposofthaposoft
54

hapo:brainstorm

Transforms raw ideas into validated, spec-ready designs for software architecture.

Official
Advanced
libertininicklibertininick

maintainability

Evaluate code maintainability using structured criteria during code reviews.

Community
Basic