pal-e-docs

TODO: Document .claude-no-enforce in agent-workflow SOP

todo-document-claude-no-enforce Doc

open todo
Project

TODO: Document .claude-no-enforce in agent-workflow SOP

What

The .claude-no-enforce dotfile exists in check-issue.sh (line 74) as a repo-level opt-out from issue-driven development enforcement. It's undocumented in pal-e-docs — the agent-workflow SOP, betty-sue agent profile, and related conventions don't mention it.

Why

Frontend iteration with Lucas in the loop requires direct coding by the main session. The full agent spawn → issue → PR lifecycle is too heavy for "move this div, check on phone, tweak the color." The dotfile already exists in the hook system but needs to be documented as a first-class escape hatch.

Updates needed

  • agent-workflow — add exception to Rule 5: "Unless .claude-no-enforce is present in the repo root, which authorizes direct coding by the main session"
  • agent-betty-sue — update Code Tools and Constraints sections to reference the dotfile
  • betty-sue.md in claude-custom — same updates
  • Consider: create a convention note (convention-claude-no-enforce) documenting when/why to use it
  • Consider: should .claude-no-enforce be in a global .gitignore or per-repo?
  • check-issue.sh line 74 — the implementation
  • feedback_frontend_iteration — the principle behind it
  • sop-frontend-dev-overlay — the workflow this supports