all-for-claudecode 2.11.0 → 2.12.0

package/.claude-plugin/marketplace.json

@@ -6,14 +6,14 @@
   },
   "metadata": {
     "description": "Automated pipeline for Claude Code — spec → plan → implement → review → clean",
-    "version": "2.11.0"
+    "version": "2.12.0"
   },
   "plugins": [
     {
       "name": "afc",
       "source": "./",
       "description": "Automated pipeline for Claude Code. Automates the full development cycle: spec → plan → implement → review → clean.",
-      "version": "2.11.0",
+      "version": "2.12.0",
       "category": "automation",
       "tags": ["pipeline", "automation", "spec", "plan", "implement", "review", "critic-loop"]
     }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "afc",
-  "version": "2.11.0",
+  "version": "2.12.0",
   "description": "Automated pipeline for Claude Code. Automates the full development cycle: spec → plan → implement → review → clean.",
   "author": { "name": "jhlee0409", "email": "relee6203@gmail.com" },
   "homepage": "https://github.com/jhlee0409/all-for-claudecode",

package/MIGRATION.md

@@ -20,7 +20,7 @@
 - If you previously used `/afc:analyze` for artifact consistency checking, use `/afc:validate` instead (or let the pipeline invoke it automatically).
 - Agent memory files (`.claude/agent-memory/afc-architect/MEMORY.md`, `.claude/agent-memory/afc-security/MEMORY.md`) exceeding 100 lines will be auto-pruned on next pipeline run.
 - Memory subdirectories exceeding rotation thresholds will be auto-pruned during the Clean phase.
-- Run `/afc:init` to update the `AFC:VERSION` tag in your CLAUDE.md.
+- Run `/afc:setup` to update the `AFC:VERSION` tag in your CLAUDE.md.
 
 ---
 
@@ -77,7 +77,7 @@ Replace the `SELFISH:START` / `SELFISH:END` block in your project's CLAUDE.md:
 - Change all `selfish:` command references → `afc:`
 - Change `selfish-architect` / `selfish-security` → `afc-architect` / `afc-security`
 
-Or simply run `/afc:init` to regenerate the block.
+Or simply run `/afc:setup` to regenerate the block.
 
 #### 4. Migrate state files (if pipeline was active)
 

package/README.md

@@ -28,7 +28,8 @@ npx all-for-claudecode
 Then:
 
 ```
-/afc:init                              # Detect your stack, generate config
+/afc:setup                             # Set up global routing in ~/.claude/CLAUDE.md
+/afc:init                              # Detect your stack, generate project config
 /afc:auto "Add user authentication"    # Run the full pipeline
 ```
 
@@ -115,7 +116,8 @@ Performance: ✓ no N+1 queries
 | `/afc:clean` | Pipeline artifact cleanup and codebase hygiene |
 | `/afc:research` | Technical research with persistent storage |
 | `/afc:debug` | Bug diagnosis and fix |
-| `/afc:init` | Project setup — detects stack and generates config |
+| `/afc:init` | Project setup — detects stack and generates project config |
+| `/afc:setup` | Global CLAUDE.md configuration — injects/updates AFC routing block |
 | `/afc:doctor` | Diagnose project health and plugin setup |
 | `/afc:architect` | Architecture analysis (persistent memory) |
 | `/afc:security` | Security scan (persistent memory, isolated worktree) |
@@ -248,10 +250,12 @@ Dependencies are tracked via DAG. CI gate + Mini-Review + Auto-Checkpoint run at
 ## Configuration
 
 ```
-/afc:init
+/afc:setup    # One-time: inject routing block into ~/.claude/CLAUDE.md
+/afc:init     # Per-project: detect stack and generate .claude/afc.config.md
 ```
 
-Auto-detects your tech stack (package manager, framework, architecture, testing, linting) and generates `.claude/afc.config.md` with CI commands, architecture rules, and code style conventions. No manual preset selection needed — the init command analyzes your project structure directly.
+- **`/afc:setup`** — Manages the AFC routing block in your global `~/.claude/CLAUDE.md`. Run once after install and again after plugin updates. Idempotent — skips if version matches.
+- **`/afc:init`** — Auto-detects your tech stack (package manager, framework, architecture, testing, linting) and generates project-local config files. No manual preset selection needed.
 
 ## FAQ
 

package/bin/cli.mjs

@@ -97,6 +97,7 @@ async function main() {
     console.log("  ✓ Installation complete!");
     console.log();
     console.log("  Next steps:");
+    console.log("    /afc:setup                   Set up global routing");
     console.log("    /afc:init                    Create project config");
     console.log('    /afc:auto "feature desc"      Run the pipeline');
     console.log();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "all-for-claudecode",
-  "version": "2.11.0",
+  "version": "2.12.0",
   "description": "Claude Code plugin that automates the full dev cycle — spec, plan, implement, review, clean.",
   "bin": {
     "all-for-claudecode": "bin/cli.mjs"

package/scripts/afc-consistency-check.sh

@@ -264,7 +264,7 @@ check_command_docs() {
   [ -d "$skills_dir" ] || return
 
   local readme="$PROJECT_DIR/README.md"
-  local init_skill="$skills_dir/init/SKILL.md"
+  local setup_skill="$skills_dir/setup/SKILL.md"
   local claude_md="$PROJECT_DIR/CLAUDE.md"
   local issues=0
 
@@ -281,12 +281,12 @@ check_command_docs() {
       fi
     fi
 
-    # Sub-check B: init/SKILL.md should mention afc:{name} for user-invocable skills
+    # Sub-check B: setup/SKILL.md should mention afc:{name} for user-invocable skills
     local invocable
     invocable=$(get_cmd_field "$skill_file" "user-invocable")
-    if [ "$invocable" != "false" ] && [ -f "$init_skill" ]; then
-      if ! grep -qE "afc:${cmd_name}([^a-z0-9-]|$)" "$init_skill" 2>/dev/null; then
-        warn "Skill '$cmd_name' missing from init/SKILL.md skill routing"
+    if [ "$invocable" != "false" ] && [ -f "$setup_skill" ]; then
+      if ! grep -qE "afc:${cmd_name}([^a-z0-9-]|$)" "$setup_skill" 2>/dev/null; then
+        warn "Skill '$cmd_name' missing from setup/SKILL.md skill routing"
         issues=$((issues + 1))
       fi
     fi
@@ -303,7 +303,7 @@ check_command_docs() {
   done
 
   if [ "$issues" -eq 0 ]; then
-    ok "Skill docs: all skills referenced in README.md, init/SKILL.md, CLAUDE.md"
+    ok "Skill docs: all skills referenced in README.md, setup/SKILL.md, CLAUDE.md"
   fi
 }
 

package/scripts/afc-doctor.sh

@@ -55,6 +55,20 @@ section() {
   printf '\n%s\n' "$1"
 }
 
+# --- Header: show which plugin version is running ---
+if [ -f "$PLUGIN_ROOT/package.json" ]; then
+  if command -v jq >/dev/null 2>&1; then
+    RUNNING_VERSION=$(jq -r '.version // "unknown"' "$PLUGIN_ROOT/package.json" 2>/dev/null || echo "unknown")
+  else
+    RUNNING_VERSION=$(grep -o '"version"[[:space:]]*:[[:space:]]*"[^"]*"' "$PLUGIN_ROOT/package.json" 2>/dev/null | head -1 | sed 's/.*: *"//;s/"//' || echo "unknown")
+  fi
+  printf 'all-for-claudecode Doctor (v%s)\n' "$RUNNING_VERSION"
+  printf 'Plugin root: %s\n' "$PLUGIN_ROOT"
+else
+  printf 'all-for-claudecode Doctor (version unknown)\n'
+  printf 'Plugin root: %s\n' "$PLUGIN_ROOT"
+fi
+
 # --- Category 1: Environment ---
 section "Environment"
 
@@ -160,15 +174,15 @@ if [ -f "$GLOBAL_CLAUDE" ]; then
         if [ "$BLOCK_VERSION" = "$PLUGIN_VERSION" ]; then
           pass "Block version matches plugin ($PLUGIN_VERSION)"
         else
-          warn "all-for-claudecode block outdated (block: $BLOCK_VERSION, plugin: $PLUGIN_VERSION)" "run /afc:init to update"
+          warn "all-for-claudecode block outdated (block: $BLOCK_VERSION, plugin: $PLUGIN_VERSION)" "run /afc:setup to update"
         fi
       fi
     fi
   else
-    fail "all-for-claudecode block not found" "run /afc:init to inject all-for-claudecode block"
+    fail "all-for-claudecode block not found" "run /afc:setup to inject all-for-claudecode block"
   fi
 else
-  warn "No global ~/.claude/CLAUDE.md" "run /afc:init"
+  warn "No global ~/.claude/CLAUDE.md" "run /afc:setup"
 fi
 
 # --- Category 4: Legacy Migration ---
@@ -179,7 +193,7 @@ LEGACY_FOUND=false
 # Legacy CLAUDE.md block
 if [ -f "$GLOBAL_CLAUDE" ] && grep -q '<!-- SELFISH:START -->' "$GLOBAL_CLAUDE" 2>/dev/null; then
   LEGACY_FOUND=true
-  warn "Legacy SELFISH:START block in ~/.claude/CLAUDE.md" "run /afc:init (will replace)"
+  warn "Legacy SELFISH:START block in ~/.claude/CLAUDE.md" "run /afc:setup (will replace)"
 fi
 
 # Legacy config

package/scripts/session-start-context.sh

@@ -73,7 +73,7 @@ if [ -f "$PLUGIN_ROOT/package.json" ]; then
     if [ -f "$GLOBAL_CLAUDE" ]; then
       BLOCK_VERSION=$(grep -o 'AFC:VERSION:[0-9][0-9.]*' "$GLOBAL_CLAUDE" 2>/dev/null | head -1 | sed 's/AFC:VERSION://' || true)
       if [ -n "${BLOCK_VERSION:-}" ] && [ "$BLOCK_VERSION" != "$PLUGIN_VERSION" ]; then
-        OUTPUT="${OUTPUT:+$OUTPUT | }[AFC VERSION MISMATCH] v$PLUGIN_VERSION installed but CLAUDE.md block is v$BLOCK_VERSION. Run /afc:init to update."
+        OUTPUT="${OUTPUT:+$OUTPUT | }[AFC VERSION MISMATCH] v$PLUGIN_VERSION installed but CLAUDE.md block is v$BLOCK_VERSION. Run /afc:setup to update."
       fi
     fi
   fi

package/skills/architect/SKILL.md

@@ -99,7 +99,7 @@ Structure analysis results and **print to console**:
 
 ### 4. Critic Loop
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 
 Run the critic loop until convergence. Safety cap: 5 passes.
 

package/skills/auto/SKILL.md

@@ -88,7 +88,7 @@ Route based on **what expertise the feature actually needs**, not keyword presen
 
 ## Critic Loop Rules (common to all phases)
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 > Core: minimum 1 concern per criterion + mandatory Adversarial failure scenario each pass + quantitative evidence required. "PASS" as a single word is prohibited. Uses convergence-based termination with 4 verdicts (PASS/FAIL/ESCALATE/DEFER). On ESCALATE: pause and present options to user even in auto mode.
 
 ---
@@ -102,18 +102,18 @@ Route based on **what expertise the feature actually needs**, not keyword presen
 3. Determine feature name (2-3 keywords → kebab-case)
 3.5. **Preflight Check**:
    ```bash
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-preflight-check.sh"
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-preflight-check.sh"
    ```
    - If exit 1 (hard failure) → print error and **abort**
    - If warnings only (exit 0) → print warnings and continue
 4. **Activate Pipeline Flag** (hook integration):
    ```bash
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" start {feature}
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" start {feature}
    ```
    - Safety Snapshot created automatically (`afc/pre-auto` git tag)
    - Stop Gate Hook activated (blocks response termination on CI failure)
    - File change tracking started
-   - Timeline log: `"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" log pipeline-start "Auto pipeline: {feature}"`
+   - Timeline log: `"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" log pipeline-start "Auto pipeline: {feature}"`
 5. Create `.claude/afc/specs/{feature}/` directory → **record path as `PIPELINE_ARTIFACT_DIR`** (for Clean scope)
 6. **Initialize Skill Advisor**: `ADVISOR_COUNT = 0`, `ADVISOR_TRANSFORM_USED = false`. Persist to pipeline state for context-loss resilience:
    ```bash
@@ -134,7 +134,7 @@ Before investing pipeline resources, evaluate whether the request warrants execu
 1. **Necessity check**: Explore codebase for existing implementations related to `$ARGUMENTS`.
    - If the feature substantially exists → ask user via AskUserQuestion:
      - "This feature appears to already exist at {path}. (1) Enhance existing (2) Replace entirely (3) Abort"
-   - If user chooses abort → release pipeline flag (`"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" end`), end with: `"Pipeline aborted — feature already exists."`
+   - If user chooses abort → release pipeline flag (`"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" end`), end with: `"Pipeline aborted — feature already exists."`
 
 2. **Scope check**: Estimate the scope of `$ARGUMENTS`:
    - If description implies 10+ files or multiple unrelated concerns → warn:
@@ -171,8 +171,8 @@ If all checks pass, proceed to Phase 0.8.
 3. If change touches > 2 files OR modifies any `.sh` script: **rollback fast-path changes** (`git reset --hard afc/pre-auto`), then restart with full pipeline
 4. **Checkpoint**:
    ```bash
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase fast-path
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" ci-pass
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase fast-path
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" ci-pass
    ```
 5. Run `/afc:review` logic inline (mini-review only — single Critic pass)
 6. Run Phase 5 Clean logic (artifact cleanup, CI gate, pipeline flag release)
@@ -187,7 +187,7 @@ If all checks pass, proceed to Phase 0.8.
 
 ### Phase 0.5: Auto-Clarify Gate (conditional)
 
-`"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase clarify`
+`"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase clarify`
 
 **Trigger condition**: Score `$ARGUMENTS` on 5 ambiguity signals. If score >= 3, trigger clarification.
 
@@ -274,7 +274,7 @@ If all checks pass, proceed to Phase 0.8.
 
 ### Phase 1: Spec (1/5)
 
-`"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase spec`
+`"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase spec`
 
 Execute `/afc:spec` logic inline:
 
@@ -381,7 +381,7 @@ Execute `/afc:spec` logic inline:
 
 ### Phase 2: Plan (2/5)
 
-`"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase plan`
+`"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase plan`
 
 Execute `/afc:plan` logic inline:
 
@@ -523,7 +523,7 @@ Execute `/afc:plan` logic inline:
 
 ### Phase 3: Implement (3/5)
 
-`"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase implement`
+`"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase implement`
 
 **Session context reload**: At implement start, read `.claude/afc/specs/{feature}/context.md` if it exists. This restores key decisions and constraints from Plan phase (resilient to context compaction).
 
@@ -576,14 +576,14 @@ Execute `/afc:implement` logic inline — **follow all orchestration rules defin
 
 #### Step 3.2: TDD Pre-Generation (conditional)
 
-`"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase test-pre-gen`
+`"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase test-pre-gen`
 
 **Trigger condition**: tasks.md contains at least 1 task targeting a `.sh` file in `scripts/`.
 
 **If triggered**:
 1. Run the test pre-generation script:
    ```bash
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-test-pre-gen.sh" ".claude/afc/specs/{feature}/tasks.md" "spec/"
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-test-pre-gen.sh" ".claude/afc/specs/{feature}/tasks.md" "spec/"
    ```
 2. Review generated skeleton files — verify they are parseable:
    ```bash
@@ -598,14 +598,14 @@ Execute `/afc:implement` logic inline — **follow all orchestration rules defin
 
 #### Step 3.3: Blast Radius Analysis (conditional)
 
-`"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase blast-radius`
+`"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase blast-radius`
 
 **Trigger condition**: plan.md File Change Map lists >= 3 files to change.
 
 **If triggered**:
 1. Run the blast radius analysis:
    ```bash
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-blast-radius.sh" ".claude/afc/specs/{feature}/plan.md" "${CLAUDE_PROJECT_DIR}"
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-blast-radius.sh" ".claude/afc/specs/{feature}/plan.md" "${CLAUDE_PROJECT_DIR}"
    ```
 2. If exit 1 (cycle detected): **ESCALATE** — present the cycle to user with options:
    - Option 1: Refactor plan to break the cycle
@@ -621,11 +621,11 @@ Execute `/afc:implement` logic inline — **follow all orchestration rules defin
 0. **Baseline test** (follows implement.md Step 1, item 5): if `{config.test}` is non-empty, run `{config.test}` before starting task execution. On failure, report pre-existing test failures to user and ask: "(1) Proceed anyway (2) Fix first (3) Abort". On pass or empty config, continue.
 1. Execute tasks phase by phase using implement.md orchestration rules (sequential/batch/swarm based on [P] count)
 2. **Implementation Context injection**: Every sub-agent prompt includes the `## Implementation Context` section from plan.md **and relevant FR/AC items from spec.md** (ensures spec intent propagates to workers)
-3. Perform **3-4 step gate** on each Implementation Phase completion — **always** read `${CLAUDE_PLUGIN_ROOT}/docs/phase-gate-protocol.md` first. Cannot advance to next phase without passing the gate.
-   - On gate pass: create phase rollback point `"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase-tag {phase_number}`
+3. Perform **3-4 step gate** on each Implementation Phase completion — **always** read `${CLAUDE_SKILL_DIR}/../../docs/phase-gate-protocol.md` first. Cannot advance to next phase without passing the gate.
+   - On gate pass: create phase rollback point `"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase-tag {phase_number}`
 4. Real-time `[x]` updates in tasks.md
 5. After full completion, run `{config.ci}` final verification
-   - On pass: `"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" ci-pass` (releases Stop Gate)
+   - On pass: `"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" ci-pass` (releases Stop Gate)
    - **On fail: Debug-based RCA** (replaces blind retry):
      1. Execute `/afc:debug` logic inline with the CI error output as input
      2. Debug performs RCA: error trace → data flow → hypothesis → targeted fix
@@ -656,7 +656,7 @@ Execute `/afc:implement` logic inline — **follow all orchestration rules defin
 
 #### Step 3.6: Implement Critic Loop
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 
 **Critic Loop until convergence** (safety cap: 5, follow Critic Loop rules):
 - **SCOPE_ADHERENCE**: Compare `git diff` changed files against plan.md File Change Map. Flag any file modified that is NOT in the plan. Flag any planned file NOT modified. Provide "M of N files match" count.
@@ -750,7 +750,7 @@ Execute `/afc:implement` logic inline — **follow all orchestration rules defin
 
 ### Phase 4: Review (4/5)
 
-`"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase review`
+`"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase review`
 
 Execute `/afc:review` logic inline — **follow all review perspectives defined in `skills/review/SKILL.md`** (A through H). The review skill is the single source of truth for review criteria.
 
@@ -902,7 +902,7 @@ If Checkpoint D produced outputs, inject them into the review context:
 
 #### Step 4.9: Critic Loop
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 
 **Critic Loop until convergence** (safety cap: 5, follow Critic Loop rules):
 - COMPLETENESS: were all changed files reviewed across all 8 perspectives (A-H)?
@@ -1005,7 +1005,7 @@ Persist the review results for memory:
 
 ### Phase 5: Clean (5/5)
 
-`"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase clean`
+`"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase clean`
 
 Artifact cleanup and codebase hygiene check after implementation and review:
 
@@ -1078,11 +1078,11 @@ Artifact cleanup and codebase hygiene check after implementation and review:
    - Clear `.claude/afc/memory/checkpoint.md` **and** `~/.claude/projects/{ENCODED_PATH}/memory/checkpoint.md` (pipeline complete = session goal achieved, dual-delete prevents stale checkpoint in either location; `ENCODED_PATH` = project path with `/` replaced by `-`)
 7. **Timeline finalize**:
    ```bash
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" log pipeline-end "Pipeline complete: {feature}"
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" log pipeline-end "Pipeline complete: {feature}"
    ```
 8. **Release Pipeline Flag** (hook integration):
    ```bash
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" end
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" end
    ```
    - Stop Gate Hook deactivated
    - Change tracking log deleted

package/skills/clean/SKILL.md

@@ -24,7 +24,7 @@ model: sonnet
 ### 1. Resolve Feature
 
 ```bash
-"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase clean
+"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase clean
 ```
 
 - If pipeline is active: read feature from state
@@ -98,13 +98,13 @@ Clear `.claude/afc/memory/checkpoint.md` **and** `~/.claude/projects/{ENCODED_PA
 ### 8. Timeline Finalize
 
 ```bash
-"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" log pipeline-end "Pipeline complete: {feature}"
+"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" log pipeline-end "Pipeline complete: {feature}"
 ```
 
 ### 9. Release Pipeline Flag
 
 ```bash
-"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" end
+"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" end
 ```
 
 - Stop Gate Hook deactivated

package/skills/debug/SKILL.md

@@ -86,7 +86,7 @@ If hypothesis 0 is rejected: verify remaining hypotheses starting from highest p
 
 ### 5. Critic Loop
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 
 Run the critic loop until convergence. Safety cap: 5 passes.
 

package/skills/doctor/SKILL.md

@@ -16,7 +16,7 @@ model: sonnet
 > Like `brew doctor` or `flutter doctor` — verifies the **tool's setup**, NOT the project's code quality.
 > Read-only — never modifies files. Reports issues with actionable fix commands.
 >
-> **IMPORTANT: Do NOT analyze project source code, architecture, or code quality. Only check afc plugin configuration, hooks, state, and environment as defined in the check tables below.**
+> **IMPORTANT: Do NOT analyze project source code, architecture, or code quality. Only check afc plugin configuration, hooks, state, and environment. All checks are handled by the bash script — just run it and print the output.**
 
 ## Arguments
 
@@ -39,7 +39,7 @@ Each failing check includes a **Fix:** line with the exact command to resolve it
 
 1. Run the health check script (covers ALL categories — no manual checks needed):
    ```
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-doctor.sh" $ARGUMENTS
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-doctor.sh" $ARGUMENTS
    ```
 
 2. Print the script's stdout output as-is. Do not reformat, summarize, or interpret.
@@ -54,8 +54,8 @@ Each failing check includes a **Fix:** line with the exact command to resolve it
 ## Example Output
 
 ```
-all-for-claudecode Doctor
-=======================
+all-for-claudecode Doctor (v2.11.0)
+Plugin root: /path/to/plugin
 
 Environment
   ✓ git installed (2.43.0)
@@ -64,34 +64,38 @@ Environment
 
 Project Config
   ✓ .claude/afc.config.md exists
-  ✓ Required sections: ci, gate, architecture, code_style
-  ✓ CI command runnable
-  ✓ Gate command runnable
+  ✓ Required sections present
+  ✓ Gate command defined
 
 CLAUDE.md Integration
   ✓ Global ~/.claude/CLAUDE.md exists
   ✓ all-for-claudecode block present
-  ⚠ all-for-claudecode block version outdated (1.0.0 → 1.1.0)
-    Fix: /afc:init
-  ✓ No conflicting routing
+  ⚠ all-for-claudecode block outdated (block: 1.0.0, plugin: 1.1.0)
+    Fix: run /afc:setup to update
+
+Legacy Migration
+  ✓ No legacy artifacts found
 
 Pipeline State
-  ✓ No stale pipeline flag
+  ✓ No stale pipeline state
   ✓ No orphaned artifacts
-  ✓ No lingering safety tags
-  ✓ No stale checkpoint
+
+Memory Health
 
 Hook Health
   ✓ hooks.json valid
-  ✓ All scripts exist
+  ✓ All hook scripts exist
   ✓ All scripts executable
 
+Learner Health
+  ✓ Learner not enabled (opt-in via /afc:learner enable)
+
 Version Sync (dev)
-  ✓ Version triple match
+  ✓ Version triple match (1.1.0)
   ✓ Cache in sync
 
-Command Definitions (dev)
-  ✓ Frontmatter exists (25 files)
+Skill Definitions (dev)
+  ✓ Frontmatter exists (29 files)
   ✓ Required fields present
   ✓ Name-filename match
   ✓ Fork-agent references valid
@@ -108,7 +112,7 @@ Doc References (dev)
   ✓ Domain adapters exist (3 files)
 
 ─────────────────────────
-Results: 28 passed, 2 warnings, 0 failures
+Results: 26 passed, 2 warnings, 0 failures
 2 warnings found. Non-blocking but review recommended.
 ```
 
@@ -119,4 +123,4 @@ Results: 28 passed, 2 warnings, 0 failures
 - **Always run all checks**: do not stop on first failure. The full picture is the value.
 - **Actionable fixes**: every non-pass result must include a Fix line. Never report a problem without a solution.
 - **Fast execution**: skip CI/gate command checks if `--fast` is in arguments (these are the slowest checks).
-- **Development checks**: Categories 8–11 (Version Sync, Command Definitions, Agent Definitions, Doc References) only run when inside the all-for-claudecode source repo.
+- **Development checks**: Version Sync, Skill Definitions, Agent Definitions, Doc References only run when inside the all-for-claudecode source repo.

package/skills/implement/SKILL.md

@@ -43,8 +43,8 @@ git tag -f afc/pre-implement
 **Standalone safety activation** (skip if inside `/afc:auto`):
 If no active pipeline state exists, activate it for the duration of this command:
 ```bash
-"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" start {feature-name-from-plan.md}
-"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase implement
+"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" start {feature-name-from-plan.md}
+"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase implement
 ```
 This enables Stop Gate and CI Gate hooks during standalone implementation. Release on completion (Step 7) or failure rollback.
 
@@ -81,8 +81,8 @@ If `.claude/afc/specs/{feature}/tasks.md` does not exist, generate it from plan.
      - Constraint → tasks (every spec Constraint is addressed by at least one task)
 3. **Validate** (script-based, no critic loop):
    ```bash
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-dag-validate.sh" .claude/afc/specs/{feature}/tasks.md
-   "${CLAUDE_PLUGIN_ROOT}/scripts/afc-parallel-validate.sh" .claude/afc/specs/{feature}/tasks.md
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-dag-validate.sh" .claude/afc/specs/{feature}/tasks.md
+   "${CLAUDE_SKILL_DIR}/../../scripts/afc-parallel-validate.sh" .claude/afc/specs/{feature}/tasks.md
    ```
 4. If validation fails → fix tasks.md and re-validate (max 2 attempts)
 5. Save to `.claude/afc/specs/{feature}/tasks.md`
@@ -312,12 +312,12 @@ When a worker agent returns an error:
 
 #### Phase Completion Gate (3 steps)
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/phase-gate-protocol.md` first and perform the 3–4 steps (CI gate → Mini-Review → Integration/E2E Gate (conditional) → Auto-Checkpoint) in order.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/phase-gate-protocol.md` first and perform the 3–4 steps (CI gate → Mini-Review → Integration/E2E Gate (conditional) → Auto-Checkpoint) in order.
 > Cannot advance to the next phase without passing the gate. Abort and report to user after 3 consecutive CI failures.
 
 After passing the gate, create a phase rollback point:
 ```bash
-"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" phase-tag {phase_number}
+"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" phase-tag {phase_number}
 ```
 This enables granular rollback: `git reset --hard afc/phase-{N}` restores state after Phase N completed.
 
@@ -359,7 +359,7 @@ After all tasks are complete:
 
 After CI passes, run a convergence-based Critic Loop to verify design alignment before reporting completion.
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 
 **Critic Loop until convergence** (safety cap: 5):
 
@@ -378,7 +378,7 @@ After CI passes, run a convergence-based Critic Loop to verify design alignment
 
 **Standalone cleanup** (if pipeline was activated in Step 0):
 ```bash
-"${CLAUDE_PLUGIN_ROOT}/scripts/afc-pipeline-manage.sh" end
+"${CLAUDE_SKILL_DIR}/../../scripts/afc-pipeline-manage.sh" end
 ```
 
 ```

package/skills/init/SKILL.md

@@ -12,8 +12,16 @@ model: sonnet
 
 # /afc:init — Project Initial Setup
 
-> Creates a `.claude/afc.config.md` configuration file in the current project,
-> and injects afc intent-based routing rules into `~/.claude/CLAUDE.md`.
+> Creates project-local configuration files for the all-for-claudecode plugin.
+> Analyzes the project structure and generates config, rules, and profile.
+> This is a **project-local** operation — it only creates files under `.claude/`.
+> For global `~/.claude/CLAUDE.md` setup, use `/afc:setup` instead.
+
+## Important
+
+This skill is a **prompt-only skill** — there is NO `afc-init.sh` script.
+All steps below are instructions for the LLM to execute directly using its allowed tools (Read, Write, Bash, Glob).
+Do NOT attempt to run a shell script for this skill.
 
 ## Arguments
 
@@ -124,7 +132,7 @@ Generate `.claude/afc.config.md` in **free-form markdown** format:
 3. **Code Style** section: describe detected language, strictness, naming conventions, lint rules in free-form prose/lists
 4. **Project Context** section: describe framework, state management, styling, testing, DB/ORM, risks, and any other relevant project characteristics in free-form prose/lists
 
-Reference `${CLAUDE_PLUGIN_ROOT}/templates/afc.config.template.md` for the section structure.
+Reference `${CLAUDE_SKILL_DIR}/../../templates/afc.config.template.md` for the section structure.
 Write sections as natural descriptions — **no YAML code blocks** except for CI Commands.
 For items that cannot be inferred: note `TODO: Adjust for your project` inline.
 Save to `.claude/afc.config.md`.
@@ -137,7 +145,7 @@ Generate `.claude/rules/afc-project.md` — a concise summary of project rules t
 2. If `.claude/rules/afc-project.md` already exists:
    - If it contains `<!-- afc:auto-generated` marker: overwrite silently (auto-generated file, safe to regenerate)
    - If it does NOT contain the marker: ask user "Project rules file exists (user-managed). Overwrite with auto-generated version?" — skip if declined
-3. Reference `${CLAUDE_PLUGIN_ROOT}/templates/afc-project.template.md` for section structure
+3. Reference `${CLAUDE_SKILL_DIR}/../../templates/afc-project.template.md` for section structure
 4. Fill in from the analysis performed in Step 3:
    - **Architecture**: pattern, key layers, import rules, path alias — concise bullet points
    - **Code Style**: language, naming conventions, lint rules — concise bullet points
@@ -153,195 +161,30 @@ Generate `.claude/afc/project-profile.md` for expert consultation agents:
 
 1. Create `.claude/afc/` directory if it does not exist
 2. If `.claude/afc/project-profile.md` already exists: skip (do not overwrite)
-3. If not exists: generate from the detected project information using `${CLAUDE_PLUGIN_ROOT}/templates/project-profile.template.md` as the structure
+3. If not exists: generate from the detected project information using `${CLAUDE_SKILL_DIR}/../../templates/project-profile.template.md` as the structure
    - Fill in Stack, Architecture, and Domain fields from the analysis in Step 3
    - Leave Team, Scale, and Constraints as template placeholders for user to fill
 4. Print: `Project profile: .claude/afc/project-profile.md (review and adjust team/scale/domain fields)`
 
-### 5. Scan Global CLAUDE.md and Detect Conflicts
-
-Read `~/.claude/CLAUDE.md` and analyze in the following order.
-
-#### Step 1. Check for Existing all-for-claudecode or Legacy SELFISH Block
-
-Check for presence of `<!-- AFC:START -->` or `<!-- SELFISH:START -->` marker.
-- If `<!-- AFC:START -->` found: replace with latest version (proceed to Step 3)
-- If `<!-- SELFISH:START -->` found (legacy v1.x): remove the entire `SELFISH:START` ~ `SELFISH:END` block, then proceed to inject new all-for-claudecode block at Step 4. Print: `Migrated: SELFISH block → all-for-claudecode block in ~/.claude/CLAUDE.md`
-- If neither found: proceed to Step 2
-
-#### Step 2. Conflict Pattern Scan
-
-Search CLAUDE.md for the patterns below. **IMPORTANT: EXCLUDE content inside any marker blocks (`<!-- *:START -->` ~ `<!-- *:END -->`). Only scan unguarded content outside marker blocks.** Other tools (OMC, etc.) manage their own blocks — their internal agent names are not conflicts.
-
-**A. Marker Block Detection**
-- Regex: `<!-- ([A-Z0-9_-]+):START -->` ~ `<!-- \1:END -->`
-- Record all found block names and line ranges
-- **Strip these ranges from the scan target** — only scan lines NOT inside any marker block
-
-**B. Agent Routing Conflict Detection**
-In the **unguarded** (non-marker-block) content only, find directives containing these keywords:
-- `executor`, `deep-executor` — conflicts with afc:implement
-- `code-reviewer`, `quality-reviewer`, `style-reviewer`, `api-reviewer`, `security-reviewer`, `performance-reviewer` — conflicts with afc:review
-- `debugger` (in agent routing context) — conflicts with afc:debug
-- `planner` (in agent routing context) — conflicts with afc:plan
-- `analyst`, `verifier` — conflicts with afc:validate
-- `test-engineer` — conflicts with afc:test
-
-**C. Skill Routing Conflict Detection**
-In the **unguarded** content only, find these patterns:
-- Another tool's skill trigger table (e.g., tables like `| situation | skill |`)
-- `delegate to`, `route to`, `always use` + agent name combinations
-- Directives related to `auto-trigger`, `intent detection`, `intent-based routing`
-
-**D. Legacy Block Detection**
-Previous versions without markers or with old branding:
-- `## all-for-claudecode Auto-Trigger Rules`
-- `## all-for-claudecode Integration`
-- `<!-- SELFISH:START -->` ~ `<!-- SELFISH:END -->` (v1.x block — should have been caught in Step 1, but double-check here)
-- `<selfish-pipeline>` / `</selfish-pipeline>` XML tags
-
-#### Step 3. Report Conflicts and User Choice
-
-**No conflicts found** → proceed directly to Step 4
-
-**Conflicts found** → report to user and present options:
-
-```
-📋 CLAUDE.md Scan Results
-├─ Tool blocks found: {block name list} (lines {range})
-├─ Agent routing conflicts: {conflict count}
-│   e.g., "executor" (line XX) ↔ afc:implement
-│   e.g., "code-reviewer" (line XX) ↔ afc:review
-└─ Skill routing conflicts: {conflict count}
-```
-
-Ask user:
-
-> "Directives overlapping with afc were found. How would you like to proceed?"
->
-> 1. **afc-exclusive mode** — Adds afc override comments to conflicting agent routing directives.
->    Does not modify other tools' marker block contents; covers them with override rules in the all-for-claudecode block.
-> 2. **coexistence mode** — Ignores conflicts and adds only the afc block.
->    Since it's at the end of the file, afc directives will likely take priority, but may be non-deterministic on conflict.
-> 3. **manual cleanup** — Shows only the current conflict list and stops.
->    User manually cleans up CLAUDE.md then runs init again.
-
-Based on choice:
-- **Option 1**: all-for-claudecode block includes explicit override rules (activates `<conflict-overrides>` section from base template)
-- **Option 2**: all-for-claudecode block added without overrides (base template as-is)
-- **Option 3**: Print conflict list only and abort without modifying CLAUDE.md
-
-#### Step 4. Inject all-for-claudecode Block
-
-**Version resolution**: Read `${CLAUDE_PLUGIN_ROOT}/package.json` and extract the `"version"` field. Use this value as `{PLUGIN_VERSION}` in the template below.
-
-Add the following block at the **very end** of the file (later-positioned directives have higher priority).
-
-Replace existing all-for-claudecode block if present, otherwise append.
-If legacy block (`## all-for-claudecode Auto-Trigger Rules` etc.) exists, remove it then append.
-
-```markdown
-<!-- AFC:START -->
-<!-- AFC:VERSION:{PLUGIN_VERSION} -->
-<afc-pipeline>
-IMPORTANT: For requests matching the afc skill routing table below, always invoke the corresponding skill via the Skill tool. Do not substitute with other agents or tools.
-
-## Skill Routing
-
-Classify the user's intent and route to the matching skill. Use semantic understanding — not keyword matching.
-
-| User Intent | Skill | Route When |
-|-------------|-------|------------|
-| Full lifecycle | `afc:auto` | User wants end-to-end feature development, or the request is a non-trivial new feature without an existing plan |
-| Specification | `afc:spec` | User wants to define or write requirements, acceptance criteria, or success conditions |
-| Design/Plan | `afc:plan` | User wants to plan HOW to implement before coding — approach, architecture decisions, design |
-| Implement | `afc:implement` | User wants specific code changes with a clear scope: add feature, refactor, modify. Requires existing plan or precise instructions |
-| Review | `afc:review` | User wants code review, PR review, or quality check on existing/changed code |
-| Debug/Fix | `afc:debug` | User reports a bug, error, or broken behavior and wants diagnosis and fix |
-| Test | `afc:test` | User wants to write tests, improve coverage, or verify behavior |
-| Validate | `afc:validate` | User wants to check consistency or validate existing pipeline artifacts |
-| Analyze | `afc:analyze` | User wants to understand, explore, or audit existing code without modifying it |
-| QA Audit | `afc:qa` | User wants project quality audit, test confidence check, or runtime quality gaps |
-| Research | `afc:research` | User wants deep investigation of external tools, libraries, APIs, or technical concepts |
-| Ideate | `afc:ideate` | User wants to brainstorm ideas, explore possibilities, or draft a product brief |
-| Consult | `afc:consult` | User wants expert advice on a decision: library choice, architecture direction, legal/security/infra guidance |
-| Launch | `afc:launch` | User wants to prepare a release — generate changelog, release notes, version bump, or tag |
-| Tasks | `afc:tasks` | User explicitly wants to decompose work into a task breakdown |
-| Ambiguous | `afc:clarify` | User's request is too vague or underspecified to route confidently |
-
-### Routing Rules
-
-1. **Auto vs Implement**: A new feature request without an existing plan routes to `afc:auto`. Only use `afc:implement` when the user has a clear, scoped task or an existing plan/spec.
-2. **Compound intents**: Route to the primary intent. The pipeline handles sequencing internally.
-3. **Design-first**: When scope is non-trivial (multiple files, architectural decisions needed), prefer `afc:auto` or `afc:plan` over direct `afc:implement`.
-
-User-only (not auto-triggered — when user invokes directly via `/afc:X`, execute the skill immediately):
-- `afc:doctor` — plugin health check
-- `afc:architect` — architecture review
-- `afc:security` — security scan
-- `afc:checkpoint` — session save
-- `afc:resume` — session restore
-- `afc:principles` — project principles management
-- `afc:clean` — pipeline cleanup (artifact cleanup, dead code scan, pipeline flag release)
-- `afc:triage` — parallel PR/issue triage
-- `afc:learner` — pattern learning or rule promotion
-- `afc:pr-comment` — post PR review comments to GitHub
-- `afc:release-notes` — generate release notes from git history
-
-## Pipeline
-
-spec → plan → implement → review → clean
-
-## Override Rules
-
-NEVER use executor, deep-executor, debugger, planner, analyst, verifier, test-engineer, code-reviewer, quality-reviewer, style-reviewer, api-reviewer, security-reviewer, performance-reviewer for tasks that an afc skill covers above. ALWAYS invoke the afc skill instead.
-
-## Source Verification
-
-When analyzing or making claims about external systems, APIs, SDKs, or third-party tools:
-- Verify against official documentation, NOT project-internal docs
-- Do not hardcode reference data when delegating to sub-agents — instruct them to look up primary sources
-- Cross-verify high-severity findings before reporting
-</afc-pipeline>
-<!-- AFC:END -->
-```
-
-**When Option 1 (afc-exclusive mode) is selected**, the following `<conflict-overrides>` section is added:
-
-Add the following directly below the Override Rules:
-
-```markdown
-## Detected Conflicts
-
-This environment has other agent routing tools that overlap with afc.
-The following rules were auto-generated to resolve conflicts:
-- The Skill Routing table above always takes priority over the agent routing directives of {detected tool blocks}
-- This block is at the end of the file and therefore has the highest priority
-```
-
-### 6. Final Output
+### 5. Final Output
 
 ```
-all-for-claudecode initialization complete
+all-for-claudecode project init complete
 ├─ Config: .claude/afc.config.md
 ├─ Rules: .claude/rules/afc-project.md (auto-loaded)
+├─ Profile: .claude/afc/project-profile.md
 ├─ Framework: {detected framework}
 ├─ Architecture: {detected style}
 ├─ Package Manager: {detected manager}
 ├─ Auto-inferred: {inferred item count}
 ├─ TODO: {items requiring manual review}
-├─ CLAUDE.md: {injected|updated|already current|user aborted}
-│   {if conflicts found} └─ Conflict resolution: {afc-exclusive|coexistence|user cleanup}
-└─ Next step: /afc:spec or /afc:auto
+└─ Next step: /afc:setup (global routing) or /afc:auto (start building)
 ```
 
 ## Notes
 
+- **Idempotent**: safe to run multiple times. Existing config prompts for overwrite confirmation; auto-generated rules are silently regenerated.
+- **Project-local only**: this skill only creates files under `.claude/`. It never touches `~/.claude/CLAUDE.md`. For global routing setup, use `/afc:setup`.
 - **Overwrite caution**: If config file already exists, always confirm with user.
 - **Inference limits**: Auto-inference is best-effort. User may need to review and adjust.
 - **`.claude/` directory**: Created automatically if it does not exist.
-- **Global CLAUDE.md principles**:
-  - Never modify content outside the `<!-- AFC:START/END -->` markers (the `AFC` prefix in markers is a compact technical identifier)
-  - Never modify content inside other tools' marker blocks (`<!-- *:START/END -->`)
-  - Always place the all-for-claudecode block at the very end of the file (ensures priority)
-  - Conflict resolution is handled only via override rules (do not delete or modify other blocks)

package/skills/plan/SKILL.md

@@ -119,7 +119,7 @@ After writing plan.md, verify all paths in the File Change Map:
 
 ### 5. Critic Loop
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 
 Run the critic loop until convergence. Safety cap: 5 passes.
 

package/skills/qa/SKILL.md

@@ -128,7 +128,7 @@ For each active category:
 
 ### 5. Critic Loop
 
-**Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it. Safety cap: **5 passes**.
+**Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it. Safety cap: **5 passes**.
 
 Focus the critic on:
 - Are the findings actionable or just noise?

package/skills/review/SKILL.md

@@ -276,7 +276,7 @@ If `.claude/afc/memory/retrospectives/` directory exists, load the **most recent
 
 ### 6. Critic Loop
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 
 Run the critic loop until convergence. Safety cap: 5 passes.
 

package/skills/setup/SKILL.md

@@ -0,0 +1,217 @@
+---
+name: afc:setup
+description: "Global CLAUDE.md configuration — use when the user asks to set up afc routing in their global config, update the AFC block version, or resolve routing conflicts"
+argument-hint: "[--force]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+model: sonnet
+---
+
+# /afc:setup — Global CLAUDE.md Configuration
+
+> Manages the all-for-claudecode routing block in `~/.claude/CLAUDE.md`.
+> Handles injection, updates, conflict detection, and legacy migration of the AFC block.
+> This is a **global config** operation — it modifies `~/.claude/CLAUDE.md`, NOT project files.
+> For project-local setup (config, rules, profile), use `/afc:init` instead.
+
+This skill is a **prompt-only skill** — there is no bash script.
+All steps below are instructions for the LLM to execute directly using its allowed tools.
+
+## Arguments
+
+- `$ARGUMENTS` — (optional) flags:
+  - `--force` — skip conflict prompts and use coexistence mode
+
+## Execution Steps
+
+### 1. Version Resolution
+
+Read `${CLAUDE_SKILL_DIR}/../../package.json` and extract the `"version"` field. Use this value as `{PLUGIN_VERSION}` throughout.
+
+### 2. Check Current State
+
+Read `~/.claude/CLAUDE.md`. If file does not exist, create it with an empty body and proceed to Step 5.
+
+Check for:
+- `<!-- AFC:START -->` marker → existing AFC block found
+- `<!-- SELFISH:START -->` marker → legacy v1.x block found
+- Neither → fresh install
+
+**If existing AFC block found:**
+- Extract version from `<!-- AFC:VERSION:X.Y.Z -->`
+- If version matches `{PLUGIN_VERSION}`: print `AFC block already up to date (v{PLUGIN_VERSION})` and **stop**
+- If version differs: proceed to Step 3 (will replace)
+
+**If legacy SELFISH block found:**
+- Remove entire `<!-- SELFISH:START -->` ~ `<!-- SELFISH:END -->` block
+- Print: `Removed legacy SELFISH block`
+- Proceed to Step 3
+
+### 3. Conflict Pattern Scan
+
+Search `~/.claude/CLAUDE.md` for routing conflicts. **IMPORTANT: EXCLUDE content inside any marker blocks (`<!-- *:START -->` ~ `<!-- *:END -->`). Only scan unguarded content outside marker blocks.** Other tools (OMC, etc.) manage their own blocks — their internal agent names are not conflicts.
+
+**A. Marker Block Detection**
+- Regex: `<!-- ([A-Z0-9_-]+):START -->` ~ `<!-- \1:END -->`
+- Record all found block names and line ranges
+- **Strip these ranges from the scan target** — only scan lines NOT inside any marker block
+
+**B. Agent Routing Conflict Detection**
+In the **unguarded** (non-marker-block) content only, find directives containing these keywords:
+- `executor`, `deep-executor` — conflicts with afc:implement
+- `code-reviewer`, `quality-reviewer`, `style-reviewer`, `api-reviewer`, `security-reviewer`, `performance-reviewer` — conflicts with afc:review
+- `debugger` (in agent routing context) — conflicts with afc:debug
+- `planner` (in agent routing context) — conflicts with afc:plan
+- `analyst`, `verifier` — conflicts with afc:validate
+- `test-engineer` — conflicts with afc:test
+
+**C. Skill Routing Conflict Detection**
+In the **unguarded** content only, find these patterns:
+- Another tool's skill trigger table (e.g., tables like `| situation | skill |`)
+- `delegate to`, `route to`, `always use` + agent name combinations
+- Directives related to `auto-trigger`, `intent detection`, `intent-based routing`
+
+**D. Legacy Block Detection**
+Previous versions without markers or with old branding:
+- `## all-for-claudecode Auto-Trigger Rules`
+- `## all-for-claudecode Integration`
+- `<selfish-pipeline>` / `</selfish-pipeline>` XML tags
+
+### 4. Report Conflicts and User Choice
+
+**No conflicts found** → proceed directly to Step 5
+
+**Conflicts found** (skip if `--force` flag present — default to coexistence):
+
+```
+CLAUDE.md Scan Results
+├─ Tool blocks found: {block name list} (lines {range})
+├─ Agent routing conflicts: {conflict count}
+│   e.g., "executor" (line XX) ↔ afc:implement
+│   e.g., "code-reviewer" (line XX) ↔ afc:review
+└─ Skill routing conflicts: {conflict count}
+```
+
+Ask user:
+
+> "Directives overlapping with afc were found. How would you like to proceed?"
+>
+> 1. **afc-exclusive mode** — Adds override rules in the AFC block to cover conflicting directives.
+>    Does not modify other tools' marker block contents.
+> 2. **coexistence mode** — Adds only the AFC block without overrides.
+>    Since it's at the end of the file, afc directives will likely take priority.
+> 3. **manual cleanup** — Shows the conflict list only and stops.
+
+Based on choice:
+- **Option 1**: AFC block includes explicit override rules (see conflict-overrides section below)
+- **Option 2**: AFC block added without overrides (base template as-is)
+- **Option 3**: Print conflict list only and abort without modifying CLAUDE.md
+
+### 5. Inject AFC Block
+
+Add the following block at the **very end** of `~/.claude/CLAUDE.md` (later-positioned directives have higher priority).
+
+Replace existing AFC block if present, otherwise append.
+If legacy block (`## all-for-claudecode Auto-Trigger Rules` etc.) exists, remove it then append.
+
+```markdown
+<!-- AFC:START -->
+<!-- AFC:VERSION:{PLUGIN_VERSION} -->
+<afc-pipeline>
+IMPORTANT: For requests matching the afc skill routing table below, always invoke the corresponding skill via the Skill tool. Do not substitute with other agents or tools.
+
+## Skill Routing
+
+Classify the user's intent and route to the matching skill. Use semantic understanding — not keyword matching.
+
+| User Intent | Skill | Route When |
+|-------------|-------|------------|
+| Full lifecycle | `afc:auto` | User wants end-to-end feature development, or the request is a non-trivial new feature without an existing plan |
+| Specification | `afc:spec` | User wants to define or write requirements, acceptance criteria, or success conditions |
+| Design/Plan | `afc:plan` | User wants to plan HOW to implement before coding — approach, architecture decisions, design |
+| Implement | `afc:implement` | User wants specific code changes with a clear scope: add feature, refactor, modify. Requires existing plan or precise instructions |
+| Review | `afc:review` | User wants code review, PR review, or quality check on existing/changed code |
+| Debug/Fix | `afc:debug` | User reports a bug, error, or broken behavior and wants diagnosis and fix |
+| Test | `afc:test` | User wants to write tests, improve coverage, or verify behavior |
+| Validate | `afc:validate` | User wants to check consistency or validate existing pipeline artifacts |
+| Analyze | `afc:analyze` | User wants to understand, explore, or audit existing code without modifying it |
+| QA Audit | `afc:qa` | User wants project quality audit, test confidence check, or runtime quality gaps |
+| Research | `afc:research` | User wants deep investigation of external tools, libraries, APIs, or technical concepts |
+| Ideate | `afc:ideate` | User wants to brainstorm ideas, explore possibilities, or draft a product brief |
+| Consult | `afc:consult` | User wants expert advice on a decision: library choice, architecture direction, legal/security/infra guidance |
+| Launch | `afc:launch` | User wants to prepare a release — generate changelog, release notes, version bump, or tag |
+| Tasks | `afc:tasks` | User explicitly wants to decompose work into a task breakdown |
+| Ambiguous | `afc:clarify` | User's request is too vague or underspecified to route confidently |
+
+### Routing Rules
+
+1. **Auto vs Implement**: A new feature request without an existing plan routes to `afc:auto`. Only use `afc:implement` when the user has a clear, scoped task or an existing plan/spec.
+2. **Compound intents**: Route to the primary intent. The pipeline handles sequencing internally.
+3. **Design-first**: When scope is non-trivial (multiple files, architectural decisions needed), prefer `afc:auto` or `afc:plan` over direct `afc:implement`.
+
+User-only (not auto-triggered — when user invokes directly via `/afc:X`, execute the skill immediately):
+- `afc:doctor` — plugin health check
+- `afc:setup` — global CLAUDE.md configuration
+- `afc:init` — project-local setup
+- `afc:architect` — architecture review
+- `afc:security` — security scan
+- `afc:checkpoint` — session save
+- `afc:resume` — session restore
+- `afc:principles` — project principles management
+- `afc:clean` — pipeline cleanup (artifact cleanup, dead code scan, pipeline flag release)
+- `afc:triage` — parallel PR/issue triage
+- `afc:learner` — pattern learning or rule promotion
+- `afc:pr-comment` — post PR review comments to GitHub
+- `afc:release-notes` — generate release notes from git history
+
+## Pipeline
+
+spec → plan → implement → review → clean
+
+## Override Rules
+
+NEVER use executor, deep-executor, debugger, planner, analyst, verifier, test-engineer, code-reviewer, quality-reviewer, style-reviewer, api-reviewer, security-reviewer, performance-reviewer for tasks that an afc skill covers above. ALWAYS invoke the afc skill instead.
+
+## Source Verification
+
+When analyzing or making claims about external systems, APIs, SDKs, or third-party tools:
+- Verify against official documentation, NOT project-internal docs
+- Do not hardcode reference data when delegating to sub-agents — instruct them to look up primary sources
+- Cross-verify high-severity findings before reporting
+</afc-pipeline>
+<!-- AFC:END -->
+```
+
+**When Option 1 (afc-exclusive mode) is selected**, add the following directly below the Override Rules:
+
+```markdown
+## Detected Conflicts
+
+This environment has other agent routing tools that overlap with afc.
+The following rules were auto-generated to resolve conflicts:
+- The Skill Routing table above always takes priority over the agent routing directives of {detected tool blocks}
+- This block is at the end of the file and therefore has the highest priority
+```
+
+### 6. Final Output
+
+```
+all-for-claudecode setup complete
+├─ CLAUDE.md: {injected|updated|already current|user aborted}
+├─ Version: {PLUGIN_VERSION}
+│   {if conflicts found} └─ Conflict resolution: {afc-exclusive|coexistence|user cleanup}
+└─ Next step: /afc:init (project setup) or /afc:auto (start building)
+```
+
+## Notes
+
+- **Idempotent**: safe to run multiple times. If version matches, it's a no-op.
+- **Global only**: this skill only touches `~/.claude/CLAUDE.md`. For project config, use `/afc:init`.
+- **Global CLAUDE.md principles**:
+  - Never modify content outside the `<!-- AFC:START/END -->` markers
+  - Never modify content inside other tools' marker blocks (`<!-- *:START/END -->`)
+  - Always place the AFC block at the very end of the file (ensures priority)
+  - Conflict resolution is handled only via override rules (do not delete or modify other blocks)

package/skills/spec/SKILL.md

@@ -98,7 +98,7 @@ If `.claude/afc/memory/retrospectives/` directory exists, load the **most recent
 
 ### 5. Critic Loop
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 
 Run the critic loop until convergence. Safety cap: 5 passes.
 

package/skills/tasks/SKILL.md

@@ -80,8 +80,8 @@ Decompose tasks per Phase defined in plan.md.
 1. **1 task = 1 file** principle (where possible)
 2. **Same file = sequential**, **different files = [P] candidate**
 3. **Explicit dependencies**: Use `depends: [T001, T002]` to declare blocking dependencies. Tasks without `depends:` and with [P] marker are immediately parallelizable.
-4. **[P] physical validation**: Before finalizing tasks.md, run `"${CLAUDE_PLUGIN_ROOT}/scripts/afc-parallel-validate.sh" .claude/afc/specs/{feature}/tasks.md` to verify no file path overlaps exist among [P] tasks within the same phase. Fix any conflicts before proceeding.
-5. **Dependency graph must be a DAG**: no circular dependencies allowed. **Mandatory validation**: run `"${CLAUDE_PLUGIN_ROOT}/scripts/afc-dag-validate.sh" .claude/afc/specs/{feature}/tasks.md` before output. Abort if cycle detected.
+4. **[P] physical validation**: Before finalizing tasks.md, run `"${CLAUDE_SKILL_DIR}/../../scripts/afc-parallel-validate.sh" .claude/afc/specs/{feature}/tasks.md` to verify no file path overlaps exist among [P] tasks within the same phase. Fix any conflicts before proceeding.
+5. **Dependency graph must be a DAG**: no circular dependencies allowed. **Mandatory validation**: run `"${CLAUDE_SKILL_DIR}/../../scripts/afc-dag-validate.sh" .claude/afc/specs/{feature}/tasks.md` before output. Abort if cycle detected.
 6. **Test tasks**: Include a verification task for each testable unit
 7. **Phase gate**: Add a `{config.gate}` validation task at the end of each Phase
 
@@ -93,14 +93,14 @@ If `.claude/afc/memory/retrospectives/` directory exists, load the **most recent
 
 ### 4. Critic Loop
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 
 Run the critic loop until convergence. Safety cap: 5 passes.
 
 | Criterion | Validation |
 |-----------|------------|
 | **COVERAGE** | Are all files in plan.md's File Change Map included in tasks? Are all FR-* in spec.md covered? |
-| **DEPENDENCIES** | Is the dependency graph a valid DAG? Do [P] tasks within the same phase have no file overlaps? Are all `depends:` targets valid task IDs? For physical validation of [P] file overlaps, reference the validation script: `"${CLAUDE_PLUGIN_ROOT}/scripts/afc-parallel-validate.sh"` can be called with the tasks.md path to verify no conflicts exist. |
+| **DEPENDENCIES** | Is the dependency graph a valid DAG? Do [P] tasks within the same phase have no file overlaps? Are all `depends:` targets valid task IDs? For physical validation of [P] file overlaps, reference the validation script: `"${CLAUDE_SKILL_DIR}/../../scripts/afc-parallel-validate.sh"` can be called with the tasks.md path to verify no conflicts exist. |
 
 **On FAIL**: auto-fix and continue to next pass.
 **On ESCALATE**: pause, present options to user, apply choice, resume.

package/skills/test/SKILL.md

@@ -93,7 +93,7 @@ Confirm strategy with user before proceeding.
 
 ### 4. Critic Loop
 
-> **Always** read `${CLAUDE_PLUGIN_ROOT}/docs/critic-loop-rules.md` first and follow it.
+> **Always** read `${CLAUDE_SKILL_DIR}/../../docs/critic-loop-rules.md` first and follow it.
 
 Run the critic loop until convergence. Safety cap: 5 passes.
 

package/skills/triage/SKILL.md

@@ -33,7 +33,7 @@ model: sonnet
 Run the metadata collection script:
 
 ```bash
-"${CLAUDE_PLUGIN_ROOT}/scripts/afc-triage.sh" "$ARGUMENTS"
+"${CLAUDE_SKILL_DIR}/../../scripts/afc-triage.sh" "$ARGUMENTS"
 ```
 
 This returns JSON with PR/issue metadata. If the script is not available, fall back to direct `gh` commands: