common-constraints

What problem does it solve?

Universal guardrails to prevent catastrophic agent failures by enforcing evidence-driven completion, limiting scope creep, and preventing unsafe modifications. These constraints help avert rationalization loops, repeated failed attempts, and drift from agreed-upon goals.

Core Features & Use Cases

• Constraint 1: Evidence Requirement ensures that claims of completion are supported by concrete evidence such as command output, test results, or build logs.
• Constraint 2: Failure Escalation enforces a maximum of three attempts before surfacing next steps.
• Constraint 3: Read-First Discipline requires reading relevant files and context before any modification.
• Constraint 4: Convention Adherence enforces project conventions and local patterns.
• Constraint 5: Self-Review Gate prompts a quick self-review before reporting completion.
• Constraint 6: Scope Discipline keeps changes focused on the requested task and notes out-of-scope work.

Quick Start

Ask the agent to apply all six constraints before marking a task as done.