openspec-explore

Name: openspec-explore
Availability: InStock
Author: cynkra

Investigate codebase architecture and draft OpenSpec artifacts without implementing code.

1|1|Updated May 5, 2026

Search Tags:#design thinking #openspec #guardrails #codebase investigation #workflow planning #requirements clarification #explore mode

Ready to run

npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-explore-cynkra

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you think through AI workflow changes—clarifying requirements, investigating the codebase, and comparing options—without jumping into implementation too early.

Core Features & Use Cases

Thinking-first “explore mode”: guide deep investigation and ideation for ambiguous or evolving requirements.
Codebase-grounded discovery: prompts you to read existing artifacts and map integration points before changing anything.
Safety guardrails: explicitly prevents implementation work while enabling OpenSpec thinking artifacts like proposals or specs when requested.

Quick Start

Use openspec-explore when you want to investigate a change idea and decide what to build next, without writing any code or implementing features.

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 investigate a codebase before starting implementation?▼

To clarify requirements and investigate a codebase before implementation, use a thinking-first explore mode that enforces safety guardrails against writing code while mapping integration points and comparing approaches.

What is the best way to explore software architecture and compare approaches without writing code?▼

Exploring software architecture without writing code involves using an exploration mode that prompts you to read existing artifacts, map integration points, and draft OpenSpec proposals while explicitly preventing any feature implementation.

Can I draft OpenSpec proposals and specs during the codebase investigation process?▼

Yes, you can draft OpenSpec proposals and specs during codebase investigation; the exploration mode supports optional artifact creation while maintaining guardrails that forbid actual code implementation.

How do I plan an AI workflow change by grounding discovery in existing codebase artifacts?▼

Planning an AI workflow change through grounded discovery requires reading existing codebase artifacts, mapping integration points, and comparing options while operating in a strict no-implementation stance.

Why should I not use implementation-focused tools when exploring ambiguous requirements?▼

You should not use implementation-focused tools for ambiguous requirements because they encourage premature coding; an exploration mode with safety guardrails prevents implementation while supporting deep ideation and grounded discovery.

Does openspec-explore prevent code implementation while planning workflow changes?▼

Yes, openspec-explore enforces a strict stance that prevents code implementation while facilitating workflow planning, requirements clarification, and the optional drafting of OpenSpec thinking artifacts.