corgispec-explore

Clarify OpenSpec change requirements and explore solution directions without implementing code.

113|9|Updated Apr 30, 2026

Search Tags:#planning #architecture #specification #requirements #exploration #gitlab issues #worktree isolation

Ready to run

npx skills add https://github.com/ricoyudog/Coding_Corgi_flow --skill corgispec-explore

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: corgispec-explore
Source: https://github.com/ricoyudog/Coding_Corgi_flow/tree/main/.opencode/skills/molecules/corgispec-explore
Command: npx skills add https://github.com/ricoyudog/Coding_Corgi_flow --skill corgispec-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of making confident design and requirement decisions without accidentally implementing or drifting away from the real change artifacts.

Core Features & Use Cases

Explore-mode clarity: Promotes deep thinking to investigate problems, clarify requirements, and map where work should happen.
Worktree-aware context: Uses OpenSpec outputs and worktree discovery rules so exploration reflects the actual isolated change context when isolation.mode: worktree is enabled.
Process guardrails: Prevents implementation actions and encourages grounding in tracked artifacts and (when relevant) real GitLab issue status rather than assumptions.

Quick Start

Ask corgispec-explore to investigate the requirements and risks for a specific change, using the correct worktree context if isolation is enabled, without implementing code.

Frequently Asked Questions about corgispec-explore

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

FAQPage Schema

How do I clarify requirements for a change proposal without accidentally writing code?▼

Requirement exploration clarifies solution directions and investigates risks for a change without performing implementation work. It enforces process guardrails to prevent coding actions, ensuring design decisions are grounded in artifact discovery rather than premature development.

What is the best way to explore architecture and specification risks in an isolated git worktree?▼

Worktree-aware exploration uses OpenSpec outputs and worktree discovery rules to reflect the actual isolated change context. It ensures your pre-implementation thinking and requirement mapping align with the correct isolated environment when isolation mode is enabled.

How do I map out a pre-implementation investigation using tracked GitLab issues?▼

Pre-implementation investigation grounds your exploration in tracked artifacts and real GitLab issue status. It mandates reading actual issue status rather than relying on assumptions, ensuring requirement clarity reflects the true state of tracked changes.

Can I use this requirements exploration process if I only have a rough idea and no formal specification yet?▼

Yes, requirement exploration is designed for the proposal and investigation stages. It promotes deep thinking to map where work should happen and clarifies solution directions, making it suitable even when starting from a rough idea before formal specification.

Why should I use a dedicated exploration mode instead of directly planning the implementation?▼

A dedicated exploration mode prevents implementation drift by enforcing strict guardrails against coding. It ensures you make confident design decisions by mandating artifact grounding via OpenSpec lists and worktree discovery, avoiding accidental or premature implementation.

Does requirement exploration work with OpenSpec changes that are already tracked in GitLab?▼

Yes, requirement exploration explicitly supports OpenSpec changes tracked via GitLab. It requires correct handling of GitLab status only through real reads when needed, ensuring your investigation reflects accurate, up-to-date tracked change contexts.