explore-plan

Drives a written Explore-Plan-Critique-Review-Verify workflow for non-trivial coding tasks.

64|11|Updated May 24, 2026
One-click install
npx skills add https://github.com/AlexanderMattTurner/agent-glovebox --skill explore-plan-alexandermattturner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore-plan
Source: https://github.com/AlexanderMattTurner/agent-glovebox/tree/main/.claude/skills/explore-plan
Command: npx skills add https://github.com/AlexanderMattTurner/agent-glovebox --skill explore-plan-alexandermattturner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-trivial coding tasks often fail because the agent dives into edits without understanding the codebase, invents duplicate definitions, or declares success without evidence. This Skill enforces a disciplined written-plan workflow so changes are grounded in real code, self-critiqued, peer-reviewed, and verified with actual output. ## Core Features & Use Cases - Read-only exploration: Trace relevant files and data models, cite real code paths, and give every discovered constraint a verdict (work around or delete toward). - Explicit written plans: Name the single owning definition for each fact, group steps into items with inputs, deliverables, and core/dispatch delegation labels, and start convergent setup work in the background. - Self-critique and peer review: Reread the draft as a hostile reviewer for up to three passes, then hand the plan and diff to a fresh code-reviewer subagent. - Evidence-based verification: Require real test runs, observed behavior, or captured output instead of accepting a success claim. - Use Case: When asked to plan adding rate limiting to an API, the Skill maps middleware read-only, writes a plan reusing the existing Redis client, critiques and reviews it, then verifies by hitting the endpoint until a 429 response appears. ## Quick Start Ask the agent to plan how to implement a multi-file feature, and it will explore the codebase, write and critique a plan, review it, and verify the result with real output.

Frequently Asked Questions about explore-plan

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

FAQPage Schema
How do I make an AI coding agent write a plan before editing code?

Activate this Skill on entry to plan mode or at the start of any non-trivial task. It forces read-only exploration, a written plan with named file ownership, self-critique, peer review, and evidence-based verification before execution.

When should I skip the explore-plan workflow?

Skip it for trivial edits such as typos or single-line changes, in any mode. The Skill activates only for non-trivial work: several files, an unfamiliar subsystem, or tasks spanning more than one PR.

How does the skill prevent duplicate logic across files?

Before listing files, the plan must name the one definition that owns each rule, threshold, or mapping the change touches. Other copies are collapsed onto that owner in the same change rather than bridged with parallel edits.

Can the agent start work before the plan is fully settled?

Yes, but only convergent setup work that no design outcome would discard, such as creating a branch, installing a tool, or launching an already-settled refactor. Anything a pending decision could invalidate is held back.

Why does the skill reject a verbal success claim after implementation?

Type-checks and green tests prove code correctness, not feature correctness. The Skill requires real evidence such as test runs, observed application behavior, screenshots for UI changes, or pasted command output before declaring done.