mcpField
O
openspec-explore

openspec-explore

github.com/partme-aiDevelopment48 installs
Repository

About openspec-explore

openspec-explore is a skill for investigating unclear requirements, comparing approaches, and exploring a codebase before formalizing a change. It keeps exploration conversational and creates no artifacts, then points to OpenSpec workflows for moving forward.

Key features

  1. 01Explore ideas with /opsx:explore
  2. 02Investigate codebases and problems
  3. 03Compare approaches and clarify requirements
  4. 04Create diagrams during exploration
  5. 05Transition to formal change planning

Use cases

  1. 01Clarify requirements before proposing a change
  2. 02Compare solutions before choosing an approach
  3. 03Find improvement opportunities in a codebase
  4. 04Brainstorm without creating planning artifacts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/partme-ai/openspec-skills --skill openspec-explore

After installing, type/openspec-explorein Claude Code to confirm it loaded.

Details

From the project README

OpenSpec Explore Skill

Use /opsx:explore to think through ideas, investigate problems, compare options, and clarify requirements — all without creating any artifacts or committing to a structure. When insights crystallize, transition to openspec-new or openspec-ff.

When to Use

  • Requirements are unclear and the user needs to investigate first.
  • Comparing multiple approaches before deciding on one.
  • The user wants to explore the codebase for improvement opportunities.
  • Brainstorming before a formal change proposal.

Prerequisites

  • OpenSpec initialized in the project (see openspec-initial).

Workflow

  1. Start exploration

    • Run /opsx:explore or /opsx:explore [topic].
    • The agent opens an exploratory conversation with no structure required.

  2. Investigate

    • Analyze the codebase, compare options, create diagrams, answer questions.
    • No artifacts are created during exploration — it is purely a thinking exercise.

  3. Transition when ready

    • When the user has clarity, suggest /opsx:new <change-name> to start a formal change.
    • Or /opsx:ff <change-name> if they want to create all planning artifacts at once.

Outputs

  • No artifacts or files are created. The output is the conversation itself — insights, options, recommendations.

Next Steps

  • When ready to act: use openspec-new to start a change, or openspec-ff to fast-forward through planning.

Troubleshooting

  • "Commands not recognized": Ensure OpenSpec is initialized (openspec init). See openspec-initial.

References

Comments

Markdown supported