skills.rest
unipds-engenharia-de-ia-aplicada
unipds-engenharia-de-ia-aplicadaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-explore

Investigate codebase behavior and clarify ambiguous technical problems before changes.

1.0k|514|Updated Jan 21, 2026
Search Tags:#architecture#troubleshooting#codebase#requirements#exploration#openspec
One-click install
npx skills add https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada --skill openspec-explore-unipds-engenharia-de-ia-aplicada
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada/tree/main/modulo05-ferramentas-de-IA-para-UI-UX/modulo-03/cfp-platform/.agent/skills/openspec-explore
Command: npx skills add https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada --skill openspec-explore-unipds-engenharia-de-ia-aplicada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you think through ambiguous technical problems, clarify requirements, and investigate codebase behavior before making changes.

Core Features & Use Cases

  • Requirements Exploration: Surface assumptions, constraints, and open questions during product or implementation planning.
  • Codebase Investigation: Read files, map architecture, and trace integration points to understand how a system works.
  • Tradeoff Analysis: Compare options, visualize flows, and identify risks when choosing an approach or debugging a tricky issue.
  • OpenSpec Awareness: Review existing proposals and specs so exploration stays aligned with active change context.

Quick Start

Ask the openspec-explore skill to investigate the current problem, map the relevant code paths, and help you reason about the best next step.

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 behavior to clarify requirements before implementing changes?▼

To investigate codebase behavior, you can use read-only file search and architecture tracing to map integration points, surface assumptions, and clarify technical requirements before writing any implementation code.

What is the best way to trace architecture and analyze tradeoffs when debugging an active repository?▼

Tracing architecture and analyzing tradeoffs involves mapping integration points and visualizing flows to compare options, identify risks, and understand system behavior during debugging conversations in an active repository.

When do I need to explore technical problems instead of immediately building a solution?▼

You need to explore technical problems when facing ambiguous requirements, conducting architecture tracing, or performing tradeoff analysis, ensuring you understand codebase behavior and constraints before committing to code changes.

Does this approach support diagrammatic reasoning for requirement exploration?▼

Yes, requirement exploration supports diagrammatic reasoning to visualize flows and compare options, helping you clarify constraints and surface open questions during product or implementation planning.

Can I use this to review existing specs and keep codebase exploration aligned with change context?▼

Yes, you can review existing proposals and specs through OpenSpec-aware context handling, ensuring your codebase investigation and requirement exploration stay aligned with the active change context.

Why does codebase investigation require read-only inspection without implementing code?▼

Codebase investigation requires read-only inspection to safely trace integration points and map architecture, ensuring you clarify technical problems and understand system behavior without the risk of altering active repository files.

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
BinyaminEdenBinyaminEden
26

brainstorming

Validate design specs and obtain user approval before coding.

Community
Advanced
gkganesh12gkganesh12
1

gk-review

Audit source code against documentation and test suites for architectural drift.

Community
Advanced
coolguy1771coolguy1771

architecture-diagrams

Generate system architecture diagrams using Mermaid and PlantUML code.

Community
Intermediate