execution-discipline

Enforces ten execution rules preventing polling, thrashing, and gate bypassing in long agent sessions.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/ooooooooooooooooooop/personal-ai --skill execution-discipline-ooooooooooooooooooop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execution-discipline
Source: https://github.com/ooooooooooooooooooop/personal-ai/tree/main/skills/execution-discipline
Command: npx skills add https://github.com/ooooooooooooooooooop/personal-ai --skill execution-discipline-ooooooooooooooooooop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Long-running AI agent sessions repeatedly fall into the same failure patterns: polling without waiting, treating gate rejections as deliverables, stampeding external research channels, reading large files directly into context, and silently stalling on dispatched subagents. This Skill turns those recurring anti-patterns into hard, auditable execution rules backed by read-only gate scripts. ## Core Features & Use Cases - Ten Iron Rules: Zero-polling waits, gate results as diagnostic signals, probe-before-dispatch external research, subagent-based exploration with summary-only returns, progress-reporting protocols, zero-dangling round cleanup, context budgeting, takeover consistency gates, watchdog binding, and structured handoff for long tasks. - Executable Gates: flow_check.py validates nine-stage problem-solving flows, NASA AAR retrospectives, and repeated tool-call detection from session JSONL; takeover_check.py runs six read-only consistency checks (baseline lock, registry consistency, stale cache, privacy-tracked paths, oversized files, workspace hygiene) when taking over a project. - Use Case: When resuming a multi-hour task with background subagents and CLI requests, load this Skill to run the 10-second pre-round self-check, avoid re-reading the same files, and close out dangling supervisors before ending each round. ## Quick Start Use the execution-discipline skill to audit my current long-running session for polling, repeated tool calls, and dangling subagents before I continue.

Frequently Asked Questions about execution-discipline

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

FAQPage Schema
How do I stop an AI agent from polling in long sessions?

Dispatch the task, end the current round, and wait for the completion notification instead of repeated status queries. If confirmation is needed, query status at most once, then switch to a single long-poll call such as job_output with wait enabled.

How to validate a multi-step problem-solving flow before implementation?

Record the nine stages (baseline through measure) in a flow JSON file and run flow_check.py --check-flow. The gate fails if the decision-gate is unconfirmed, ordered after implement, or the borrow stage lacks a real source URL.

What should I check when taking over an existing project?

Run takeover_check.py against the project root for six read-only checks: test baseline lock, taskflow registry consistency, stale pytest cache, privacy-tracked paths, oversized tracked files, and workspace hygiene. Any FAIL is a diagnostic signal to fix before handoff.

Does this skill require external Python packages?

No. Both flow_check.py and takeover_check.py use only the Python standard library and never modify files. Each script also ships a --selftest mode that must exit 0 before the gate is considered trustworthy.

When should this skill not be used?

Skip it for single-round small edits and temporary Q&A that needs no persistence. The rules target long-horizon, multi-tool sessions where polling, repeated reads, and dangling executors cause real cost.