openspec-explore

Name: openspec-explore
Availability: InStock
Author: kevinxo328

Explore codebases and ideas to map architecture and surface risks.

5|Updated Sep 17, 2022

Search Tags:#design #architecture #codebase #requirements #discovery #exploration #openspec

Ready to run

npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-explore-kevinxo328

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/kevinxo328/mercari-scraper/tree/main/.gemini/skills/openspec-explore
Command: npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-explore-kevinxo328

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables structured, creative exploration of ideas, requirements, and code without rushing to implementation, helping teams and individuals clarify goals, surface unknowns, and map potential approaches before committing to changes.

Core Features & Use Cases

Guided Discovery: Ask clarifying questions, reframe problems, and surface assumptions to sharpen scope and requirements.
Repository Investigation: Read and map codebase structure, identify integration points, and highlight areas of complexity or risk.
Idea Visualization: Produce ASCII diagrams, state machines, and comparison tables to compare options and reveal tradeoffs.
OpenSpec Integration: Reference and propose OpenSpec artifacts (proposals, designs, specs) without implementing code, useful for design spikes and planning sessions.

Quick Start

Ask the explore mode to review the repository and list design options, risks, and unanswered questions for the requested change.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore a codebase and map architecture before starting a design spike?▼

To explore a codebase before a design spike, use guided discovery to read repository files, map codebase structure, identify integration points, and surface risks without writing implementation code.

What is the best way to discover requirements and surface unknowns during early-stage design?▼

Requirement discovery during early-stage design involves asking clarifying questions, reframing problems, and surfacing assumptions to sharpen scope and reveal tradeoffs before committing to changes.

Can I generate design artifacts and diagrams during planning without implementing code?▼

Yes, you can generate design artifacts without implementing code by producing ASCII diagrams, state machines, and comparison tables to visualize ideas and reveal tradeoffs during planning sessions.

How do I sketch OpenSpec proposals and specs for a new feature?▼

Sketching OpenSpec proposals and specs involves referencing and proposing OpenSpec artifacts during design spikes, mapping integration points and complexity without rushing into actual code implementation.

Does guided discovery work for analyzing risks and integration points in an existing repository?▼

Guided discovery works for repository investigation by requiring read access to repository files and conversational prompts to map architecture, identify integration points, and highlight areas of complexity or risk.

When should I not use codebase exploration for project planning?▼

Codebase exploration should not be used when you are ready to commit to implementation, as this approach focuses on structured creative exploration, requirement discovery, and sketching approaches without writing code.