prohibit-bad-habits

# Prohibit bad habits ## Contract | Field | Bound contract | |---|---| | Trigger | Human requests that specific agent behavior patterns be documented as prohibited in a structured project document or agent-rule file rather than in AGENTS.md. | | Authority | Reversible local: writes only the named local artifact; rollback is deleting the written file if it did not exist before and the human has not confirmed it. No remote mutation. | | Side effect | Local file write: creates or updates one structured project document or agent-rule file that enumerates prohibited agent behavior patterns. | | Done | A structured artifact exists at the agreed target path and contains at least one prohibited-habit entry with a non-empty name and description, verified by the human. | ## Inputs - Prohibited patterns: required. For each pattern, the human supplies a short name, a concrete description of the behavior to avoid, the negative consequence of that behavior, and optionally a category and a workaround or alternative. If the human cannot supply a concrete description, stop rather than invent one. - Target location: optional. The human may specify the exact file path. Default: `docs/prohibited-habits.md` for shared project docs; `agent-rules/prohibited-habits.yaml` for agent-rule locations. - Authority confirmation: the human confirms or revises the target path before the write occurs. ## Procedure 1. Gather prohibited patterns. Ask the human to list each pattern to prohibit. For each, c...