refusal-discipline

Generate structured REFUSAL.md documentation for unmet criteria and evidence gaps.

2|Updated Jul 13, 2025
One-click install
npx skills add https://github.com/krzemienski/shannon --skill refusal-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refusal-discipline
Source: https://github.com/krzemienski/shannon/tree/main/skills/refusal-discipline
Command: npx skills add https://github.com/krzemienski/shannon --skill refusal-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that when evidence is missing or a gate cannot be satisfied, a structured REFUSAL.md is created, providing a clear path for remediation and preventing incorrect task completions.

Core Features & Use Cases

  • Evidence Gap Handling: Generates a REFUSAL.md file when evidence is missing, guiding the next steps.
  • Gate Refusal: Refuses tasks based on unmet criteria, such as missing citations or unmet gates.
  • Structured Documentation: Ensures a standardized approach to refusal documentation for easy remediation.
  • Use Case: When a task's completion cannot be verified due to missing evidence, this Skill automatically creates a REFUSAL.md file, detailing the issues and providing a remediation plan.

Quick Start

Run the /shannon:refusal-discipline command when evidence is missing or a gate cannot be satisfied.

Frequently Asked Questions about refusal-discipline

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

FAQPage Schema
How do I document evidence gaps in a multi-step workflow to prevent incorrect task completion?

To document evidence gaps in a multi-step workflow, you generate a structured REFUSAL.md file detailing the unmet criteria and providing a clear remediation plan to prevent incorrect task completions.

What happens when task validation fails due to missing citations or unmet gates?

When task validation fails due to missing citations or unmet gates, a gate refusal occurs and a REFUSAL.md file is automatically generated to detail the issues and guide the next steps.

How do I automate the refusal process for unmet criteria in complex workflows?

You automate the refusal process for unmet criteria by running a dedicated command that generates standardized REFUSAL.md documentation, ensuring task integrity and easy remediation for complex workflows.

Is structured refusal documentation suitable for evidence-based decision-making in complex workflows?

Yes, structured refusal documentation is designed specifically for complex, multi-step workflows where evidence-based decision-making is critical, ensuring tasks are not completed without proper validation.

What is the best way to handle missing evidence and ensure task integrity during workflow execution?

The best way to handle missing evidence and ensure task integrity is to create a standardized REFUSAL.md file that blocks incorrect task completions and provides a clear path for remediation.