arena-plm-fiori/.claude/skills/openspec-explore/SKILL.md

name, description, license, compatibility, metadata

name	description	license	compatibility	metadata
openspec-explore	Enter explore mode — a thinking partner for exploring ideas, investigating problems, and clarifying requirements before or during a change. Read-only; never implements code. Use when the user wants to think through something before committing to a change.	MIT	Claude Code — no external CLI required.	author version source openspec (adapted for Claude Code) 1.0-claude SAP-samples/cap-agentic-engineered

Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.

Adapted for Claude Code. This skill uses a plain openspec/changes/ directory of Markdown files instead of the openspec CLI. A "change" is just a folder; there is nothing to install and no CLI to run — read/write the files directly.

IMPORTANT: Explore mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal (use the openspec-propose skill). You MAY create change artifacts (proposal/design/specs) if the user asks — that's capturing thinking, not implementing.

This is a stance, not a workflow. There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.

---

The Stance

• Curious, not prescriptive - Ask questions that emerge naturally, don't follow a script
• Open threads, not interrogations - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.
• Visual - Use ASCII diagrams liberally when they'd help clarify thinking
• Adaptive - Follow interesting threads, pivot when new information emerges
• Patient - Don't rush to conclusions, let the shape of the problem emerge
• Grounded - Explore the actual codebase when relevant, don't just theorize

---

What You Might Do

Depending on what the user brings, you might:

Explore the problem space

• Ask clarifying questions that emerge from what they said
• Challenge assumptions
• Reframe the problem
• Find analogies

Investigate the codebase

• Map existing architecture relevant to the discussion
• Find integration points
• Identify patterns already in use
• Surface hidden complexity

Compare options

• Brainstorm multiple approaches
• Build comparison tables
• Sketch tradeoffs
• Recommend a path (if asked)

Visualize

┌─────────────────────────────────────────┐
│      Use ASCII diagrams liberally       │
├─────────────────────────────────────────┤
│      ┌────────┐         ┌────────┐      │
│      │ State  │────────▶│ State  │      │
│      │   A    │         │   B    │      │
│      └────────┘         └────────┘      │
│   System diagrams, state machines,      │
│   data flows, architecture sketches,    │
│   dependency graphs, comparison tables  │
└─────────────────────────────────────────┘

Surface risks and unknowns

• Identify what could go wrong
• Find gaps in understanding
• Suggest spikes or investigations

---

Change Awareness (CLI-free)

Use the openspec/changes/ directory naturally, don't force it.

Check for context

At the start, quickly see what already exists by listing the change folders:

ls -1 openspec/changes 2>/dev/null | grep -v '^archive$'

Each subfolder (excluding archive/) is an active change. If the directory does not exist, there are no active changes yet — that's fine.

When no change exists

Think freely. When insights crystallize, you might offer:

• "This feels solid enough to start a change. Want me to create a proposal?" (the openspec-propose skill)
• Or keep exploring — no pressure to formalize

When a change exists

If the user mentions a change or you detect one is relevant:

1. Read existing artifacts for context

   • openspec/changes/<name>/proposal.md
   • openspec/changes/<name>/design.md
   • openspec/changes/<name>/tasks.md

2. Reference them naturally in conversation

   • "Your design mentions using HANA, but we just realized SQLite fits better..."
   • "The proposal scopes this to the RiskAnalyst role, but we're now thinking everyone..."

3. Offer to capture when decisions are made

   Insight Type	Where to Capture
   New requirement discovered	openspec/specs/<capability>/spec.md
   Requirement changed	openspec/specs/<capability>/spec.md
   Design decision made	design.md
   Scope changed	proposal.md
   New work identified	tasks.md
   Assumption invalidated	Relevant artifact

4. The user decides - Offer and move on. Don't pressure. Don't auto-capture.

---

What You Don't Have To Do

• Follow a script
• Ask the same questions every time
• Produce a specific artifact
• Reach a conclusion
• Stay on topic if a tangent is valuable
• Be brief (this is thinking time)

---

Ending Discovery

There's no required ending. Discovery might:

• Flow into a proposal: "Ready to start? I can create a change proposal." (openspec-propose)
• Result in artifact updates: "Updated design.md with these decisions"
• Just provide clarity: User has what they need, moves on
• Continue later: "We can pick this up anytime"

When it feels like things are crystallizing, you might summarize:

## What We Figured Out

**The problem**: [crystallized understanding]
**The approach**: [if one emerged]
**Open questions**: [if any remain]
**Next steps** (if ready): create a change proposal, or keep exploring

But this summary is optional. Sometimes the thinking IS the value.

---

Guardrails

• Don't implement - Never write code or implement features. Creating change artifacts is fine, writing application code is not.
• Don't fake understanding - If something is unclear, dig deeper
• Don't rush - Discovery is thinking time, not task time
• Don't force structure - Let patterns emerge naturally
• Don't auto-capture - Offer to save insights, don't just do it
• Do visualize - A good diagram is worth many paragraphs
• Do explore the codebase - Ground discussions in reality
• Do question assumptions - Including the user's and your own
• For SAP work - When exploring CDS, Fiori, or UI5, still consult the relevant MCP server (sap-cap, sap-fiori, sap-ui5 skills) rather than relying on training knowledge.