verification-rules

Generate mandatory verification documents before chapter content is written.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yjang-git/HoneyPot --skill verification-rules-yjang-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-rules
Source: https://github.com/yjang-git/HoneyPot/tree/main/plugins/isd-generator/skills/verification-rules
Command: npx skills add https://github.com/yjang-git/HoneyPot --skill verification-rules-yjang-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that verification documents are created and validated before any chapter content is written, preventing incomplete or invalid chapter drafts and enforcing consistent verification across all chapter generator agents.

Core Features & Use Cases

  • Non-skippable Verification: Mandates creation of verification documents prior to drafting and halts progress if documents are missing.
  • Standardized Filenames & Locations: Defines expected filenames and storage paths for each chapter and figure to enable reliable orchestration and auditing.
  • Auto Mode Compatibility: Supports automated orchestrator runs by enforcing verification steps while allowing user-confirmation pauses to be skipped in auto mode.
  • Use Case: When running the ISD orchestration, the orchestrator will generate chapter2_research_verification.md in the verification folder before the chapter2 agent produces content.

Quick Start

Ask the orchestrator to generate the verification documents for the target chapter and ensure they are present in the output verification folder before proceeding.

Frequently Asked Questions about verification-rules

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

FAQPage Schema
How do I enforce mandatory verification documents before drafting research-plan chapters?

To enforce mandatory verification documents before drafting, you can apply rules to ISD research-plan chapter generators and orchestrators that halt progress if verification files are missing or created out of sequence.

What happens if verification documents are missing during automated orchestrator runs?

If verification documents are missing during automated orchestrator runs, the process halts immediately and raises an error, preventing incomplete or invalid chapter drafts from being generated in auto mode.

How do I standardize filenames and storage paths for chapter verification files?

You can standardize filenames and storage paths by defining expected locations such as generating chapter2_research_verification.md in a specific verification folder to enable reliable orchestration and auditing.

Can I skip user-confirmation pauses during automated web and figure generation phases?

Yes, you can skip user-confirmation pauses during automated web and figure generation phases in auto mode, but the underlying verification steps remain non-skippable and must be completed.

When do I need to generate verification documents in the ISD orchestration workflow?

You need to generate verification documents in the ISD orchestration workflow before any chapter content is written, ensuring the orchestrator outputs the verification file before the chapter agent produces content.