pac-openspec-explore

Explore ideas and clarify requirements through guided natural-language dialogue.

2|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/ladislas/mypac --skill pac-openspec-explore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pac-openspec-explore
Source: https://github.com/ladislas/mypac/tree/main/skills/pac-openspec-explore
Command: npx skills add https://github.com/ladislas/mypac --skill pac-openspec-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a thinking partner to help explore ideas, articulate requirements, and clarify problems before any change, reducing misalignment and rework.

Core Features & Use Cases

  • Guided exploration and problem framing to surface assumptions and constraints.
  • ASCII diagrams and structured prompts to map ideas, risks, and options.
  • Use Case: When starting a new feature, run a collaborative exploration session to surface questions and shape a high-level plan.

Quick Start

Tell me the idea you want to explore and I will help you think it through step by step.

Frequently Asked Questions about pac-openspec-explore

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

FAQPage Schema
How do I clarify requirements and frame problems before starting software development?

To clarify requirements and frame problems before development, use a guided thinking partner that surfaces assumptions and constraints through structured exploration. This approach maps ideas and risks using natural-language interaction and ASCII diagrams.

What is the best way to explore ideas and surface assumptions for a new software feature?

The best way to explore ideas for a new feature is running a collaborative exploration session that acts as a thinking partner. It helps you think through problems step by step to articulate high-level plans and reduce misalignment.

Can I use ASCII diagrams to map risks and options during early design exploration?

Yes, you can use ASCII diagrams to map risks and options during early design exploration. The thinking partner generates these structured visual prompts alongside natural language to help articulate constraints and shape your ideas.

Do I need any external tooling or dependencies to run a collaborative problem framing session?

No, you do not need any external tooling or dependencies to run a problem framing session. The guided thinking process requires only natural-language interaction and ASCII diagrams to explore ideas and clarify requirements.

When should I avoid using a thinking partner for requirements discovery?

You should avoid using a thinking partner for requirements discovery when you are ready for implementation. The tool enforces guardrails to explicitly avoid implementation details, focusing strictly on early problem framing and design exploration.