How do I install the Operating Discipline skill?

Run npx skillmds@latest add elevanaltd-hestai-mcp/operating-discipline in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Operating Discipline skill do?

===SKILL:OPERATING_DISCIPLINE=== It is listed under Coding & Dev Tools on SkillMD.

Is Operating Discipline safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Operating Discipline?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Operating Discipline free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Operating Discipline?

elevanaltd (@elevanaltd-hestai-mcp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Operating Discipline by elevanaltd-hestai-mcp

Name: Operating Discipline
Author: elevanaltd

File contents

===SKILL:OPERATING_DISCIPLINE=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Enforcement of system-wide operating discipline gates and boundaries"

§1::OPERATING_ESSENTIALS PHASE_GATES::"D1(NORTH-STAR)→D2(DESIGN)→D3(BLUEPRINT)→B0(VALIDATION)→B1(BUILD-PLAN+STOP)→B2(TDD)→B3(INTEGRATION)→B4(HANDOFF)" QUALITY_GATES::"TDD(failing_test_first)→TMG_CHECKPOINT(T2+:TMG_must_APPROVE)→CodeReview(every_change)→Tests(must_pass)→Security(scan_required)" RACI_CONSULTATIONS::"critical-engineer(tactical)→principal-engineer(strategic)→security-specialist(security)→requirements-steward(alignment)→test-methodology-guardian(discipline)"

§2::ENFORCEMENT_PROTOCOL BLOCKING_AUTHORITY::[ "Production risk exposure above organizational threshold", "System standard violations requiring intervention", "System coherence threats endangering overall stability", "Gap ownership abandonment creating accountability voids", "Quality gate bypassing attempts", "RACI consultation avoidance", "Phase progression with missing essential artifacts or failed quality gates" ]

§3::ESCALATION ESCALATION_CRITERIA::[ SYSTEM_STANDARD_BOUNDARY::"New principle conflicts, force reinterpretation, authority scope expansion, fundamental structure change → HUMAN", DUAL_KEY_GOVERNANCE::"Major scope changes, GO/NO-GO decisions, production deployment → critical-engineer(tactical) + principal-engineer(strategic) + requirements-steward (+ HUMAN)" ]

§5::ANCHOR_KERNEL TARGET::enforce_operating_discipline_gates_and_boundaries PHASE_GATES::D1→D2→D3→B0→B1→B2→B3→B4 QUALITY_GATES::TDD[failing_test_first]→TMG[T2+_TMG_must_APPROVE]→CodeReview[every_change]→Tests[must_pass]→Security[scan_required] RACI::[CE[tactical], PE[strategic], SecSpec[security], ReqSteward[alignment], TMG[discipline]] BLOCKING::[production_risk, system_standard_misalignment, coherence_threats, gap_abandonment, gate_bypass, RACI_avoidance, phase_progression_without_artifacts] ESCALATE_TO_HUMAN::[new_principle_conflicts, authority_scope_expansion, fundamental_structure_change] DUAL_KEY::[major_scope_changes, GO_NO_GO, production_deploy]→CE+PE+ReqSteward+HUMAN GATE::"Phase gate requirements met, quality gates passed, RACI consulted?" ===END===

---name: operating-disciplinedescription: ===SKILL:OPERATING_DISCIPLINE===---===SKILL:OPERATING_DISCIPLINE===META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Enforcement of system-wide operating discipline gates and boundaries"§1::OPERATING_ESSENTIALSPHASE_GATES::"D1(NORTH-STAR)→D2(DESIGN)→D3(BLUEPRINT)→B0(VALIDATION)→B1(BUILD-PLAN+STOP)→B2(TDD)→B3(INTEGRATION)→B4(HANDOFF)"QUALITY_GATES::"TDD(failing_test_first)→TMG_CHECKPOINT(T2+:TMG_must_APPROVE)→CodeReview(every_change)→Tests(must_pass)→Security(scan_required)"RACI_CONSULTATIONS::"critical-engineer(tactical)→principal-engineer(strategic)→security-specialist(security)→requirements-steward(alignment)→test-methodology-guardian(discipline)"§2::ENFORCEMENT_PROTOCOLBLOCKING_AUTHORITY::[ "Production risk exposure above organizational threshold", "System standard violations requiring intervention", "System coherence threats endangering overall stability", "Gap ownership abandonment creating accountability voids", "Quality gate bypassing attempts", "RACI consultation avoidance", "Phase progression with missing essential artifacts or failed quality gates"]§3::ESCALATIONESCALATION_CRITERIA::[ SYSTEM_STANDARD_BOUNDARY::"New principle conflicts, force reinterpretation, authority scope expansion, fundamental structure change → HUMAN", DUAL_KEY_GOVERNANCE::"Major scope changes, GO/NO-GO decisions, production deployment → critical-engineer(tactical) + principal-engineer(strategic) + requirements-steward (+ HUMAN)"]§5::ANCHOR_KERNELTARGET::enforce_operating_discipline_gates_and_boundariesPHASE_GATES::D1→D2→D3→B0→B1→B2→B3→B4QUALITY_GATES::TDD[failing_test_first]→TMG[T2+_TMG_must_APPROVE]→CodeReview[every_change]→Tests[must_pass]→Security[scan_required]RACI::[CE[tactical], PE[strategic], SecSpec[security], ReqSteward[alignment], TMG[discipline]]BLOCKING::[production_risk, system_standard_misalignment, coherence_threats, gap_abandonment, gate_bypass, RACI_avoidance, phase_progression_without_artifacts]ESCALATE_TO_HUMAN::[new_principle_conflicts, authority_scope_expansion, fundamental_structure_change]DUAL_KEY::[major_scope_changes, GO_NO_GO, production_deploy]→CE+PE+ReqSteward+HUMANGATE::"Phase gate requirements met, quality gates passed, RACI consulted?"===END===

Frequently asked questions

Operating Discipline