ldraney/claude-custom

Fork 0

Document .claude-no-enforce in agent-workflow SOP #156

New issue

Closed

opened 2026-03-24 20:07:58 +00:00 by forgejo_admin · 3 comments

forgejo_admin commented

2026-03-24 20:07:58 +00:00

Contributor

Type

Feature

Lineage

Standalone -- discovered during frontend iteration sessions

Repo

forgejo_admin/claude-custom

User Story

As a developer doing frontend iteration
I want .claude-no-enforce documented as a first-class escape hatch
So that the team understands when and why to bypass issue-driven development enforcement

Context

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

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."

File Targets

Files to modify:

pal-e-docs notes (via MCP): agent-workflow, agent-betty-sue
agents/betty-sue.md in claude-custom -- same updates

Files to potentially create:

pal-e-docs note: convention-claude-no-enforce

Acceptance Criteria

agent-workflow SOP updated with .claude-no-enforce exception
agent-betty-sue profile updated
agents/betty-sue.md in claude-custom updated
Convention note created if appropriate

Test Expectations

Verify .claude-no-enforce works: create file in repo, confirm hook skips enforcement
Run command: touch .claude-no-enforce && bash hooks/check-issue.sh

Constraints

Do not change the hook behavior, only document existing behavior
Keep documentation concise and actionable

Checklist

PR opened
Tests pass
No unrelated changes

pal-e-agency -- parent project
feedback_frontend_iteration -- the principle behind this feature
sop-frontend-dev-overlay -- the workflow this supports

### Type Feature ### Lineage Standalone -- discovered during frontend iteration sessions ### Repo `forgejo_admin/claude-custom` ### User Story As a developer doing frontend iteration I want `.claude-no-enforce` documented as a first-class escape hatch So that the team understands when and why to bypass issue-driven development enforcement ### Context The `.claude-no-enforce` dotfile exists in `check-issue.sh` (line 74) as a repo-level opt-out from issue-driven development enforcement. It is undocumented in pal-e-docs -- the agent-workflow SOP, betty-sue agent profile, and related conventions do not mention it. 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." ### File Targets Files to modify: - pal-e-docs notes (via MCP): `agent-workflow`, `agent-betty-sue` - `agents/betty-sue.md` in claude-custom -- same updates Files to potentially create: - pal-e-docs note: `convention-claude-no-enforce` ### Acceptance Criteria - [ ] `agent-workflow` SOP updated with `.claude-no-enforce` exception - [ ] `agent-betty-sue` profile updated - [ ] `agents/betty-sue.md` in claude-custom updated - [ ] Convention note created if appropriate ### Test Expectations - [ ] Verify `.claude-no-enforce` works: create file in repo, confirm hook skips enforcement - Run command: `touch .claude-no-enforce && bash hooks/check-issue.sh` ### Constraints - Do not change the hook behavior, only document existing behavior - Keep documentation concise and actionable ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `pal-e-agency` -- parent project - `feedback_frontend_iteration` -- the principle behind this feature - `sop-frontend-dev-overlay` -- the workflow this supports

forgejo_admin commented

2026-03-27 21:08:08 +00:00

Author

Contributor

Scope Review: NEEDS_REFINEMENT

Review note: review-343-2026-03-27
Documentation-only ticket is well-structured but has three scoping issues that need fixing before it's ready for execution.

Wrong file path: betty-sue.md should be agents/betty-sue.md (file is in agents/ subdirectory, not repo root)
Wrong arch label: Board item has arch:ci-pipeline but this is a hooks/enforcement feature, not CI pipeline. Should be arch:hooks
Agent routing conflict: pal-e-docs note updates require MCP access, which dev agents don't have per agent-workflow rules. Consider changing ### Type to Task and routing to Dottie, or splitting into two tickets (repo file change for dev agent + pal-e-docs updates for Dottie)
Vague acceptance criterion: "Convention note created if appropriate" should be a definitive yes/no
Test command won't work: check-issue.sh reads JSON from stdin; bare bash hooks/check-issue.sh will fail without piped input

## Scope Review: NEEDS_REFINEMENT Review note: `review-343-2026-03-27` Documentation-only ticket is well-structured but has three scoping issues that need fixing before it's ready for execution. - **Wrong file path**: `betty-sue.md` should be `agents/betty-sue.md` (file is in agents/ subdirectory, not repo root) - **Wrong arch label**: Board item has `arch:ci-pipeline` but this is a hooks/enforcement feature, not CI pipeline. Should be `arch:hooks` - **Agent routing conflict**: pal-e-docs note updates require MCP access, which dev agents don't have per agent-workflow rules. Consider changing `### Type` to Task and routing to Dottie, or splitting into two tickets (repo file change for dev agent + pal-e-docs updates for Dottie) - **Vague acceptance criterion**: "Convention note created if appropriate" should be a definitive yes/no - **Test command won't work**: `check-issue.sh` reads JSON from stdin; bare `bash hooks/check-issue.sh` will fail without piped input

forgejo_admin commented

2026-03-27 21:25:03 +00:00

Author

Contributor

Scope Review Corrections Needed

From review-343-2026-03-27:

Fix 1: Wrong file path — betty-sue.md should be agents/betty-sue.md.

Fix 2: Wrong arch: label on board item — arch:ci-pipeline should be arch:hooks or arch:enforcement. .claude-no-enforce is a hook escape hatch, not a CI component.

Fix 3: Reclassify as Task, not Feature. This targets both repo files AND pal-e-docs notes. Per agent-workflow, dev agents are repo-only. Either:

(a) Route entirely to Dottie (if all changes are doc updates), or
(b) Split: repo file update → dev agent, pal-e-docs note update → Dottie

Fix 4: Test command bash hooks/check-issue.sh won't work — the hook reads JSON from stdin. Provide a real test invocation.

Once fixed → READY for next_up.

## Scope Review Corrections Needed From `review-343-2026-03-27`: **Fix 1:** Wrong file path — `betty-sue.md` should be `agents/betty-sue.md`. **Fix 2:** Wrong `arch:` label on board item — `arch:ci-pipeline` should be `arch:hooks` or `arch:enforcement`. `.claude-no-enforce` is a hook escape hatch, not a CI component. **Fix 3:** Reclassify as Task, not Feature. This targets both repo files AND pal-e-docs notes. Per agent-workflow, dev agents are repo-only. Either: - (a) Route entirely to Dottie (if all changes are doc updates), or - (b) Split: repo file update → dev agent, pal-e-docs note update → Dottie **Fix 4:** Test command `bash hooks/check-issue.sh` won't work — the hook reads JSON from stdin. Provide a real test invocation. Once fixed → READY for next_up.

forgejo_admin commented

2026-03-27 21:48:36 +00:00

Author

Contributor

Issue body updated per scope review corrections.