discipline

Enforces 15 failure-prevention rules for agent sessions covering fabrication, verification, scoping, and retry discipline.

201|9|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/av/facts --skill discipline-av
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discipline
Source: https://github.com/av/facts/tree/main/skills/discipline
Command: npx skills add https://github.com/av/facts --skill discipline-av

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents repeatedly fail in predictable ways: fabricating URLs and commands, ignoring user constraints, claiming work is done without verifying it, retrying blindly, and drifting out of scope. This Skill loads an operating protocol of 15 rules distilled from 120+ real sessions to prevent those failure modes before they happen. ## Core Features & Use Cases - Failure-Prevention Rules: 15 concrete rules covering fabrication, constraint tracking, verification, investigation, scoping, retry discipline, evidence-based claims, and writing style. - Pre-Flight and Post-Flight Checklists: Mental checklists to run before every action and before declaring work done, including git status checks and output verification. - Session Failure Escalation: Named failure states (fabrication spiral, retry loop, constraint drift, scope creep, blame mode) with explicit stop conditions. - Use Case: Load the protocol at the start of any coding or investigation task so the agent verifies claims with evidence, respects stated technology choices, commits changes, and never invents commands or file contents. ## Quick Start Ask your agent to load the discipline protocol before starting the next task so it follows the 15 failure-prevention rules throughout the session.

Frequently Asked Questions about discipline

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

FAQPage Schema
How do I stop an AI agent from making up commands and URLs?▼

Load an operating protocol that forbids fabrication, such as this 15-rule skill. It requires the agent to treat anything not read, fetched, or verified in the current session as nonexistent, and to look up real values from the codebase instead of guessing.

How to make an AI coding agent verify its work before reporting done?▼

Use a verification rule requiring the agent to run code, render visual output, or confirm files exist with ls or git status before claiming success. The post-flight checklist in this skill enforces exactly that behavior.

What rules prevent AI agents from ignoring user constraints?▼

Constraint-tracking rules require the agent to restate user constraints before acting, treat corrections as permanent for the session, and never repeat rejected suggestions. This skill includes a checklist covering platform, technologies, and rejected approaches.

Can this protocol be used with any AI coding assistant?▼

Yes. The rules are tool-agnostic behavioral instructions loaded as a skill, so they apply to any agent that supports skill or instruction loading, regardless of the underlying model or platform.

When should the discipline protocol not override default behavior?▼

The protocol is designed to load before any task and override defaults wherever they conflict, so there is no intended exception case. It targets failure prevention broadly rather than a specific task type.