openspec-explore

Explore ideas, requirements, and codebase context before software changes.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/tungnguyen10/iuh_department --skill openspec-explore-tungnguyen10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/tungnguyen10/iuh_department/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/tungnguyen10/iuh_department --skill openspec-explore-tungnguyen10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of rushing into software implementation without fully understanding the problem, requirements, or existing codebase context, which leads to wasted effort and poorly scoped changes.

Core Features & Use Cases

  • Idea Exploration: Acts as a curious, non-prescriptive thinking partner to unpack vague ideas, challenge assumptions, and reframe problems without following a fixed script.
  • Codebase Grounding: Investigates the actual project codebase to map relevant architecture, find integration points, and surface hidden complexity to keep discussions rooted in reality.
  • Option Analysis: Brainstorms multiple approaches, builds tradeoff comparisons, and uses ASCII diagrams to visualize systems, state flows, and decision matrices.
  • Use Case: For example, if you are considering adding real-time collaboration to your app, use this skill to explore the spectrum of collaboration features, assess your current codebase's compatibility, and identify risks before drafting a change proposal.

Quick Start

Use the openspec-explore skill to discuss your idea for adding a user notification system and investigate the current frontend component structure before creating a change proposal.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I explore requirements and analyze a codebase before starting development?

Pre-development exploration involves investigating the problem space, mapping architecture, and identifying technical tradeoffs to ground your software changes in actual project context before writing any code.

What is the best way to plan software changes without wasting implementation effort?

Change planning requires unpacking vague ideas, challenging assumptions, and mapping integration points in your existing codebase to surface hidden complexity and identify risks early.

How do I visualize system architecture and state flows during technical tradeoff analysis?

You can visualize complex systems, state flows, and decision matrices during technical tradeoff analysis by generating ASCII diagrams to map out multiple implementation approaches.

Can I use a thinking partner to investigate my codebase compatibility for new features?

Yes, a non-prescriptive thinking partner can investigate your actual project codebase to find integration points, assess compatibility for new features, and reframe problems without following a fixed script.

Does pre-change discovery prevent poorly scoped software updates?

Pre-change discovery prevents poorly scoped updates by enabling thorough option analysis, risk identification, and architecture mapping to eliminate wasted implementation effort before application code is written.

When should I not rush into software implementation?

You should not rush into software implementation when adding complex features like real-time collaboration, as skipping codebase grounding and risk identification leads to wasted effort and poorly scoped changes.