hf.enforce-plan-and-explore

Warn on Python source edits without prior exploration or planning.

5|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/T-rav/hydraflow --skill hf-enforce-plan-and-explore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf.enforce-plan-and-explore
Source: https://github.com/T-rav/hydraflow/tree/main/.codex/skills/hf.enforce-plan-and-explore
Command: npx skills add https://github.com/T-rav/hydraflow --skill hf-enforce-plan-and-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, md5.

What problem does it solve?

This skill automatically warns when a code edit is attempted without prior exploration or a documented plan, helping teams enforce safe, deliberate changes.

Core Features & Use Cases

  • Enforces a pre-edit exploration check and a planned approach before edits are allowed to proceed.
  • Fires as a PreToolUse hook for Edit operations, specifically targeting Python source edits and skipping non-relevant files.
  • Maintains a session-based and time-window guard to avoid repeated interruptions within a 4-hour window.

Quick Start

Ensure exploration and planning have been completed before applying any code edits.

Frequently Asked Questions about hf.enforce-plan-and-explore

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

FAQPage Schema
How do I enforce planning before editing Python source code?

You can enforce planning before editing Python source code by using a PreToolUse hook that warns when edits are attempted without prior exploration or a documented plan. This guardrail ensures deliberate code changes.

What is a PreToolUse guardrail for code edits?

A PreToolUse guardrail for code edits is a hook that intercepts edit operations to check for prior exploration and planning. It specifically targets Python source edits while ignoring test and config files to maintain workflow discipline.

How do I stop repeated warnings for missing exploration during a coding session?

To stop repeated warnings for missing exploration during a coding session, the guardrail uses marker files and environment markers. It only warns once per session within a four-hour window to avoid interruptions.

Does the planning enforcement hook apply to test files and config files?

No, the planning enforcement hook does not apply to test files and config files. It specifically targets Python source edits and skips non-relevant files to focus on core code changes.

Do I need jq and md5 to run the code edit planning guardrail?

Yes, you need jq and md5 installed because the guardrail implements its exploration and planning checks via marker files and environment markers that rely on these dependencies.

When should I not use an automated planning guardrail for Python edits?

You should not use an automated planning guardrail for Python edits if your workflow requires rapid, undocumented changes outside the four-hour session window, as it enforces deliberate exploration before allowing source modifications.