Verified:Website 𝕏@ehealthresearch GitHub

openspec-explore

Explores ideas and investigates codebases through adaptive dialogue and ASCII diagrams within OpenSpec systems.

133|23|Updated Mar 23, 2020

Search Tags:#design thinking #ideation #exploration #codebase investigation #thinking partner #requirements clarification

Ready to run

npx skills add https://github.com/aehrc/pathling --skill openspec-explore-aehrc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/aehrc/pathling/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/aehrc/pathling --skill openspec-explore-aehrc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Deep Exploration: Asks clarifying questions, challenges assumptions, and reframes problems.
Codebase Investigation: Maps architecture, finds integration points, and identifies patterns.
Option Comparison: Brainstorms approaches, sketches tradeoffs, and visualizes concepts with ASCII diagrams.
Risk Identification: Surfaces potential risks and unknowns in a project.
Use Case: A user is considering a new feature. This Skill helps them think through the implications, explore existing code related to the feature, and compare different implementation strategies before writing any code.

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 writing code?▼

To clarify requirements before writing code, use this AI thinking partner to challenge assumptions, ask clarifying questions, and reframe problems through adaptive dialogue without directly implementing code.

Can I map architecture and find integration points during codebase investigation?▼

Yes, you can investigate codebases by mapping architecture, finding integration points, and identifying patterns to understand existing structures before adding new features.

What is the best way to compare implementation options and sketch tradeoffs?▼

Comparing implementation options is done by brainstorming approaches, sketching tradeoffs, and visualizing concepts using ASCII diagrams to evaluate different strategies.

How does a thinking partner help identify risks in a software project?▼

A thinking partner helps identify risks by surfacing potential unknowns and implications in a project, allowing you to think through challenges before committing to development.

Do I need an existing codebase to use design thinking for feature exploration?▼

No, you do not need an existing codebase, but if present, the skill can reference existing changes and artifacts within the OpenSpec system to ground the design thinking process.

Why use non-implementation focused exploration for conceptualizing problems?▼

Non-implementation focused exploration keeps the dialogue adaptive and conceptual, preventing premature coding by prioritizing problem reframing, risk identification, and option comparison.