skills.rest
alexzhang1030
alexzhang1030COMMUNITY
Explore all skills by this author →
𝕏@alexz_devGitHub

openspec-explore

Investigate codebases to clarify ambiguous product and engineering questions.

Updated Mar 17, 2026
Search Tags:#architecture#investigation#codebase#requirements#exploration#openspec#tradeoffs
One-click install
npx skills add https://github.com/alexzhang1030/platform-demo --skill openspec-explore-alexzhang1030
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/alexzhang1030/platform-demo/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/alexzhang1030/platform-demo --skill openspec-explore-alexzhang1030

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you think through ambiguous product or engineering questions, investigate the codebase, and clarify requirements before committing to a change.

Core Features & Use Cases

  • Requirement discovery: surface unknowns, assumptions, and open questions.
  • Architecture investigation: trace existing patterns, integration points, and dependencies in the repository.
  • Tradeoff analysis: compare options and visualize implications with diagrams or tables.
  • Use case: Use it when a feature request is unclear, a design feels risky, or you need a grounded discussion before creating a proposal.

Quick Start

Ask the openspec-explore skill to examine the relevant part of the codebase and help you reason about the problem 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 investigate codebase architecture before committing to code changes?▼

To explore a codebase before implementation, use a read-only investigation process that traces existing patterns and dependencies. This skill surfaces unknowns and clarifies requirements by synthesizing findings from files without writing application code.

What is the best way to analyze tradeoffs for a new software feature?▼

Analyzing tradeoffs involves comparing options and visualizing implications using diagrams or tables. This skill grounds the discussion by investigating the codebase to evaluate risks and clarify ambiguous product requirements before implementation.

How do I clarify unclear product requirements before starting development?▼

To clarify unclear product requirements, surface unknowns, assumptions, and open questions through early-stage discovery. This skill investigates the codebase to resolve ambiguities and ensure a feature request is fully understood before development.

Can I use codebase exploration to review design risks without modifying files?▼

Yes, codebase exploration can review design risks without modifying files by using a read-only investigation approach. This skill traces integration points and synthesizes findings to help you reason about problems safely before committing changes.

When should I do an architecture review instead of writing code immediately?▼

You should perform an architecture review when a feature request is unclear or a design feels risky. Investigating the codebase early clarifies requirements and compares options, providing a grounded discussion before creating an implementation proposal.

Related Skills

Explore More Software Engineering Skills→
JanuaryLabsJanuaryLabs
4

openspec-explore

Explore architecture and design options by reading repository files and OpenSpec artifacts without writing code.

Official
Intermediate
balajivisbalajivis
2

plan-eng-review

Review engineering implementation plans for architecture risks and missing quality requirements.

Community
Advanced
unipds-engenharia-de-ia-aplicadaunipds-engenharia-de-ia-aplicada
1.0k

openspec-explore

Investigate codebase behavior and clarify ambiguous technical problems before changes.

Official
Intermediate
Dragoon0xDragoon0x
4

map

Map JavaScript and TypeScript codebase architecture via import graph regex analysis.

Community
Intermediate