skills.rest
ishibata91
ishibata91COMMUNITY
Explore all skills by this author →
GitHub

openspec-explore

Guide teams through non-implementation exploration of ideas and requirements.

Updated Feb 3, 2026
Search Tags:#codebase#requirements#problem-solving#exploration#openspec#explore#thinking-partner
One-click install
npx skills add https://github.com/ishibata91/ai-translation-engine-2 --skill openspec-explore-ishibata91
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/ishibata91/ai-translation-engine-2/tree/main/.agent/skills/openspec-explore
Command: npx skills add https://github.com/ishibata91/ai-translation-engine-2 --skill openspec-explore-ishibata91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a thinking partner to explore ideas, investigate problems, and clarify requirements without implementing changes, helping teams align on goals and approaches.

Core Features & Use Cases

  • Guided exploration: think aloud, visualize pathways, and surface assumptions without writing code.
  • Requirement clarification: structure questions to define scope, constraints, and success criteria.
  • Collaboration enablement: acts as a conversational co-pilot to map options and risks during early discovery.

Quick Start

Enter explore mode and think deeply to map exploration directions for the user's problem.

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

You can clarify requirements by using a guided exploration partner that enforces a non-implementation policy, letting teams think aloud, visualize pathways, and surface assumptions without writing code.

What is the best way to structure problem framing during early software discovery?▼

The best way to structure problem framing is through a structured exploration workflow that acts as a conversational co-pilot to map options and risks during early discovery across software projects.

Can I use this for requirement clarification and scope definition in team design discussions?▼

Yes, you can use it for requirement clarification in team design discussions to structure questions, define scope, map constraints, and establish success criteria.

Does the Skill enforce a non-implementation policy during codebase exploration?▼

Yes, the Skill enforces a strict non-implementation policy during codebase exploration, ensuring that teams focus on deep thinking and problem-solving rather than implementing changes.

When should I use a thinking partner for problem-solving instead of coding?▼

You should use a thinking partner for problem-solving during early discovery or design discussions when you need to investigate problems, clarify goals, and align on approaches before writing code.

Related Skills

Explore More Software Engineering Skills→
deandumdeandum
3

idea-refine

Refine vague ideas into actionable task statements with MVP scope and validation criteria.

Community
Advanced
Thiago-Cruz-engThiago-Cruz-eng

brainstorming

Convert unclear product ideas into approved design specs with guided validation.

Community
Intermediate
RayOfSteel-DHBWRayOfSteel-DHBW

list-phase-assumptions

Analyze and surface Copilot's phase assumptions with confidence indicators for review.

Community
Intermediate
jkitchinjkitchin
34

brainstorming

Facilitate structured brainstorming sessions using SCAMPER and Six Thinking Hats.

Community
Advanced