openspec-explore

Explore ideas and clarify requirements within the OpenSpec system.

9|1|Updated Jun 6, 2018
One-click install
npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-explore-edwardsnjd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/edwardsnjd/dot-files/tree/main/configuration/agents/.agents/skills/openspec-explore
Command: npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-explore-edwardsnjd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a thinking partner to help users explore ideas, investigate problems, and clarify requirements before or during a change, without implementing code.

Core Features & Use Cases

  • Deep Thinking: Engages in curious, adaptive, and visual exploration of user-provided topics.
  • Codebase Investigation: Can map architecture, find integration points, and identify patterns within the codebase.
  • Option Comparison: Helps brainstorm approaches, sketch tradeoffs, and visualize options.
  • Risk Identification: Surfaces potential risks and unknowns in a project or idea.
  • Use Case: A user wants to add a new feature but is unsure about the best approach. This Skill helps them think through the problem space, explore the codebase for relevant existing patterns, and compare different implementation strategies.

Quick Start

Use the openspec-explore skill to think through the implications of adding real-time collaboration to the platform.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I clarify requirements and explore ideas before implementing a new feature?

To clarify requirements and explore ideas before implementation, you can use a design thinking process to investigate problems, map architecture, and surface risks. This approach acts as an adaptive thinking partner to visualize options without writing code.

What is the best way to investigate a codebase to find integration points and existing patterns?

Codebase investigation involves mapping architecture and identifying integration points and patterns within the software. This helps you understand the existing structure and surface unknowns before making changes or adding new features to the project.

How do I compare implementation options and sketch tradeoffs for a new software feature?

Comparing implementation options requires brainstorming approaches and sketching tradeoffs to visualize different strategies. This helps surface potential risks and unknowns, allowing you to select the best path forward without committing to direct implementation.

Can I use design thinking to map architecture and surface risks for a software change?

Yes, design thinking facilitates deep, curious exploration of user-provided topics to map architecture and surface risks. It operates within the OpenSpec system to reference existing artifacts and changes during the software development process.

Does this requirements clarification process write or modify code directly?

No, this requirements clarification process does not write or modify code directly. It acts strictly as a visual and curious thinking partner to explore problems, compare options, and map architecture without engaging in direct implementation.