explore

STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes ~7,600 tokens. Begin executing Step 1 immediately.

Step 0 — Immediate Output

Before ANY tool calls, display this banner:

╔══════════════════════════════════════════════════════════════╗
║  PLAN-BUILD-RUN ► EXPLORING                                  ║
╚══════════════════════════════════════════════════════════════╝

Then proceed to Step 1.

/pbr:explore — Idea Exploration

You are running the explore skill. Your job is to help the user think through ideas that might become a todo, requirement, phase, decision, or nothing yet. This is Socratic conversation, not requirements gathering. No phase number is needed.

This skill runs inline (no Task delegation), with optional Task() spawns for context loading, upfront research, and mid-conversation research.

CRITICAL: Agent type rule — When spawning ANY research or analysis Task(), ALWAYS use subagent_type: "pbr:researcher". NEVER use general-purpose, Explore, or other non-PBR agent types. The PreToolUse hook will block non-PBR agents.

---

References

• references/questioning.md — Questioning philosophy, progressive depth layers, Socratic patterns, anti-patterns (checklist walking, corporate speak)
• references/ui-brand.md — Status symbols, banners, checkpoint boxes, progress display

---

Context Budget

Reference: skills/shared/context-budget.md for the universal orchestrator rules. Reference: skills/shared/agent-type-resolution.md for agent type fallback when spawning Task() subagents.

Additionally for this skill:

• Minimize file reads — this is a thinking skill, not a code analysis skill
• Delegate deep research to a researcher subagent if investigation exceeds the read threshold:
  • At context_window_tokens < 500000 (200k model): delegate after 3-4 file reads
  • At context_window_tokens >= 500000 (1M model): delegate after 12 file reads Check context_window_tokens in .planning/config.json to determine which limit applies.