agent-operating-discipline

Enforce disciplined, evidence-based software engineering with minimal, traceable changes.

6|2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/paudley/coding-ethos --skill agent-operating-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-operating-discipline
Source: https://github.com/paudley/coding-ethos/tree/main/.gemini/extensions/coding-ethos/skills/agent-operating-discipline
Command: npx skills add https://github.com/paudley/coding-ethos --skill agent-operating-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides guidelines and principles for disciplined, evidence-based software development, review, and refactoring.

Core Features & Use Cases

  • Coding discipline: Enforces best practices like SOLID, YAGNI, and KISS in development workflows.
  • Code review & refactoring: Guides teams in making traceable, minimal, and verifiable code changes.
  • Use Case: Developers refactor complex modules, ensuring changes are justified with evidence and aligned with principles like testing-as-specification.

Quick Start

Use the agent-operating-discipline skill to review code changes for adherence to ETHOS principles.

Frequently Asked Questions about agent-operating-discipline

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

FAQPage Schema
What are evidence-based software engineering principles for code refactoring?

Evidence-based software engineering principles ensure code refactoring changes are minimal, traceable, and verifiable. They enforce best practices like SOLID, YAGNI, and KISS to guide developers in making justified, safe modifications to complex modules.

How do I enforce coding discipline during code review?

To enforce coding discipline during code review, apply ETHOS principles to verify that changes are traceable and minimal. Reviewers check adherence to best practices and ensure modifications are justified with evidence rather than arbitrary preference.

How do I make minimal and traceable code changes when adding features?

Make minimal and traceable code changes by adhering to disciplined software engineering practices. Verify each modification against principles like testing-as-specification, ensuring high-quality, safe outcomes when adding features or debugging.

Does this approach work for debugging complex software modules?

Yes, this approach works for debugging complex software modules by enforcing evidence-based verification. It targets developers handling complex refactoring, ensuring that debugging changes are justified, traceable, and aligned with established engineering principles.

When should I not use minimal change principles for software development?

Minimal change principles should not be used when large-scale architectural rewrites are necessary, as they prioritize traceable, verifiable modifications over sweeping changes. They are designed for focused refactoring, debugging, and feature addition rather than systemic overhauls.