corgispec-explore

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.

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.

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.

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.

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.

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.