explore

Orchestrate governance-driven codebase exploration and planning without edits.

9|9|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill explore-nullmastermind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/explore
Command: npx skills add https://github.com/nullmastermind/viber-router --skill explore-nullmastermind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines a disciplined, governance-driven approach to exploring and planning changes in a codebase. It provides a stance, guardrails, continuous verification mindset, and a clear subagent protocol to avoid unplanned edits or scope creep.

Core Features & Use Cases

  • Orchestrated exploration stance: defines who can explore, what can be accessed, and how to report findings without writing code.
  • Subagent protocol: communicates with specialized subagents (osf-analyze, osf-researcher, osf-proposal, osf-apply, osf-verify, osf-archive) to plan, implement, and verify work in foreground.
  • Guardrails and zero-fog discipline: enforces strict boundaries to prevent code changes during exploration and ensure decisions are explicit.
  • OpenSpec awareness: integrates with the OpenSpec workflow for proposals, changes, and archival in a compliant manner.

Quick Start

Review the repository to plan safe exploration tasks and outputs.

Frequently Asked Questions about explore

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

FAQPage Schema
How do I plan codebase changes without accidentally modifying files?

This Skill enforces safe codebase exploration by applying strict guardrails and a zero-fog discipline that scopes all activities to planning and analysis, preventing any unplanned edits during the review process.

What is a subagent workflow for codebase exploration and planning?

A subagent workflow for codebase exploration orchestrates specialized agents like osf-analyze, osf-researcher, and osf-proposal to handle distinct planning phases, ensuring decisions are explicit and auditable before implementation.

How do I use OpenSpec artifacts for codebase analysis and proposals?

You use OpenSpec artifacts for codebase analysis by integrating them into a formal subagent protocol, where agents manage proposals, changes, and archival in a compliant manner to maintain structured planning.

Can I scope codebase exploration to only analysis and verification tasks?

Yes, you can scope codebase exploration to only analysis and verification tasks by establishing strict guardrails that define who can explore, what can be accessed, and how findings are reported without writing code.

Best way to ensure codebase planning decisions are explicit and auditable?

The best way to ensure codebase planning decisions are explicit and auditable is to enforce a zero-fog verification discipline using a formal subagent workflow that requires verification at every exploration step.

Why do I need guardrails for safe codebase exploration?

You need guardrails for safe codebase exploration to prevent scope creep and avoid unplanned edits, ensuring that the activity remains strictly focused on planning, analysis, and verification.