Add plan compliance pre-check before RLCR loop startup (v1.13.0)

Introduce a Sonnet-based sub-agent that validates plan files before
entering the RLCR loop. The check catches two categories of issues:

- Relevance: rejects plans clearly unrelated to the current repository
- Branch-switch detection: rejects plans that require switching branches,
  which violates the RLCR invariant of a constant working branch

The pre-check runs in the command layer before setup-rlcr-loop.sh and
is skipped for --skip-impl mode. Follows the same architectural pattern
as gen-plan's draft-relevance-checker.

Author: SihaoLiu

.claude-plugin/marketplace.json

@@ -8,7 +8,7 @@
       "name": "humanize",
       "source": "./",
       "description": "Humanize - An iterative development plugin that uses Codex to review Claude's work. Creates a feedback loop where Claude implements plans and Codex independently reviews progress, ensuring quality through continuous refinement.",
-      "version": "1.12.3"
+      "version": "1.13.0"
     }
   ]
 }

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "humanize",
   "description": "Humanize - An iterative development plugin that uses Codex to review Claude's work. Creates a feedback loop where Claude implements plans and Codex independently reviews progress, ensuring quality through continuous refinement.",
-  "version": "1.12.3",
+  "version": "1.13.0",
   "author": {
     "name": "humania-org"
   },

README.md

@@ -1,6 +1,6 @@
 # Humanize
 
-**Current Version: 1.12.3**
+**Current Version: 1.13.0**
 
 > Derived from the [GAAC (GitHub-as-a-Context)](https://github.com/SihaoLiu/gaac) project.
 

agents/plan-compliance-checker.md

@@ -0,0 +1,76 @@
+---
+name: plan-compliance-checker
+description: Checks plan relevance and compliance before RLCR loop. Use when validating plan files for start-rlcr-loop command.
+model: sonnet
+tools: Read, Glob, Grep
+---
+
+# Plan Compliance Checker
+
+You are a specialized agent that validates an implementation plan before it enters an RLCR (iterative development) loop. You perform two checks and return a single verdict.
+
+## Your Task
+
+When invoked, you will be given the content of a plan file. You need to perform two checks:
+
+### Check A: Repository Relevance
+
+1. **Quickly explore the repository** to understand what it does:
+   - Check README.md, CLAUDE.md, or other documentation files
+   - Look at the directory structure
+   - Identify the main technologies, languages, and purpose
+
+2. **Analyze the plan content** to determine if it relates to this repository:
+   - Does the plan mention concepts, technologies, or components in this repo?
+   - Is the plan about modifying, extending, or using this codebase?
+   - Does the plan reference file paths, functions, or features that exist here?
+   - Does the plan have substantive content (not empty or near-empty)?
+
+3. **Be lenient** - only reject plans that are clearly unrelated to the repository (e.g., a cooking recipe plan for a software project). If the plan could reasonably be connected, it passes.
+
+### Check B: Branch-Switch Detection
+
+1. **Read the entire plan** and look for instructions that require switching, checking out, or creating git branches during implementation. Look for patterns such as:
+   - "switch to branch X", "checkout branch Y", "create branch Z"
+   - "work on branch X", "move to branch X"
+   - `git checkout -b`, `git switch`, `git branch`, `gh pr checkout`
+   - Worktree creation instructions
+   - Any instruction implying the implementer should change branches mid-work
+
+2. **Disambiguate safe patterns** - the following are NOT branch switches and should NOT trigger a failure:
+   - `git checkout -- <file>` (file restore, not branch switch)
+   - Negated instructions like "do not switch branches" or "stay on the current branch"
+   - References to branches in a descriptive context (e.g., "this feature was branched from main")
+   - `--base-branch` configuration (this is a review parameter, not a branch switch)
+
+3. **Why this matters**: RLCR requires the working branch to remain constant across all rounds of the loop. Plans that mandate branch switching are incompatible with the RLCR workflow.
+
+## Return Your Verdict
+
+You MUST output exactly one of these three verdicts on its own line:
+
+- `PASS: <brief summary of what the plan is about>`
+- `FAIL_RELEVANCE: <reason why the plan is not related to this repository>`
+- `FAIL_BRANCH_SWITCH: <quote the specific instruction from the plan that requires branch switching>`
+
+## Important Notes
+
+- Always output exactly one verdict - never output zero or multiple verdicts
+- If in doubt on relevance, lean toward PASS (same lenient approach as other validators)
+- If in doubt on branch-switch detection, lean toward PASS (avoid false positives)
+- The plan may be written in any language - that is okay
+- Focus on the substance, not the format of the plan
+
+## Example Outputs
+
+```
+PASS: Plan describes adding a new validation check to the RLCR setup script, which is part of this plugin.
+```
+
+```
+FAIL_RELEVANCE: Plan describes designing a restaurant menu system, which has no connection to this Claude Code plugin repository.
+```
+
+```
+FAIL_BRANCH_SWITCH: Plan states "checkout the feature-auth branch before starting implementation", which requires switching branches during the RLCR loop.
+```

commands/start-rlcr-loop.md

@@ -1,13 +1,65 @@
 ---
 description: "Start iterative loop with Codex review"
 argument-hint: "[path/to/plan.md | --plan-file path/to/plan.md] [--max N] [--codex-model MODEL:EFFORT] [--codex-timeout SECONDS] [--track-plan-file] [--push-every-round] [--base-branch BRANCH] [--full-review-round N] [--skip-impl] [--claude-answer-codex] [--agent-teams]"
-allowed-tools: ["Bash(${CLAUDE_PLUGIN_ROOT}/scripts/setup-rlcr-loop.sh:*)"]
+allowed-tools:
+  - "Bash(${CLAUDE_PLUGIN_ROOT}/scripts/setup-rlcr-loop.sh:*)"
+  - "Read"
+  - "Task"
 hide-from-slash-command-tool: "true"
 ---
 
 # Start RLCR Loop
 
-Execute the setup script to initialize the loop:
+## Plan Compliance Pre-Check
+
+Before running the setup script, validate the plan file for compliance. This is a fool-proofing mechanism that catches obviously wrong plan files early.
+
+**Skip this entire pre-check if** any of these conditions are true:
+- `$ARGUMENTS` contains `--skip-impl` (no plan file to validate)
+- `$ARGUMENTS` contains `-h` or `--help` (just showing help)
+
+### Extract the plan file path from arguments
+
+Parse `$ARGUMENTS` to find the plan file path:
+- If `--plan-file <path>` is present, use `<path>`
+- Otherwise, use the first positional argument (the first argument that does not start with `--` and is not a value following a known flag like `--max`, `--codex-model`, `--codex-timeout`, `--base-branch`, `--full-review-round`, `--plan-file`)
+- If no plan file path can be determined, skip the pre-check and let the setup script handle the error
+
+### Basic path safety gate
+
+Only proceed with the pre-check if the extracted path meets ALL of these conditions:
+- Is a relative path (does not start with `/`)
+- Does not contain `..` path components
+- Does not contain shell metacharacters (`;`, `&`, `|`, `$`, backtick, `<`, `>`, `(`, `)`, `{`, `}`, `!`, `#`, `~`, `*`, `?`, `\`)
+
+If any condition fails, skip the pre-check and let the setup script handle path validation.
+
+### Read and validate plan content
+
+1. Use the Read tool to read the plan file. If the file does not exist or cannot be read, skip the pre-check and let the setup script handle the error.
+
+2. Use the Task tool to invoke the `humanize:plan-compliance-checker` agent (sonnet model):
+   ```
+   Task tool parameters:
+   - model: "sonnet"
+   - prompt: Include the plan file content and ask the agent to:
+     1. Explore the repository structure (README, CLAUDE.md, main files)
+     2. Check if the plan content relates to this repository
+     3. Check if the plan contains branch-switching instructions
+     4. Return exactly one of: `PASS: <summary>`, `FAIL_RELEVANCE: <reason>`, or `FAIL_BRANCH_SWITCH: <details>`
+   ```
+
+3. **Parse the result** (fail-closed):
+   - If output contains `PASS`: continue to setup script below
+   - If output contains `FAIL_RELEVANCE`: report "Plan compliance check failed: the plan does not appear to be related to this repository." Show the reason. **Stop the command.**
+   - If output contains `FAIL_BRANCH_SWITCH`: report "Plan compliance check failed: the plan contains branch-switching instructions, which are incompatible with RLCR. The RLCR loop requires the working branch to remain constant across all rounds." Show the details. **Stop the command.**
+   - If output contains none of the above (malformed): report "Plan compliance check produced unexpected output. Cannot proceed." **Stop the command.**
+
+---
+
+## Setup
+
+If the pre-check passed (or was skipped), execute the setup script to initialize the loop:
 
 ```bash
 "${CLAUDE_PLUGIN_ROOT}/scripts/setup-rlcr-loop.sh" $ARGUMENTS