@wooojin/forgen 0.4.3 → 0.4.5

package/dist/store/compound-usage-store.d.ts

@@ -0,0 +1,28 @@
+/**
+ * Forgen — compound usage signal store (Pathfinder D11 fix, MVP).
+ *
+ * 배경 (Deep Interview 2026-04-30 Round 5):
+ *   verified compound 23개, candidate 8개 — 그러나 mature 0. retro 회고에서
+ *   "활용률 측정 불가 — compound-search 호출 카운터 미수집" 확인. 즉 사용자가
+ *   compound 를 reuse 했다는 신호 자체가 잡히지 않아서 mature 승격 입력이 없음.
+ *
+ *   원칙(user-mirror, Round 4 Contrarian): forgen 자기 학습이 아니라 *사용자
+ *   reuse* 가 mature 의 권위 종착점. 따라서 compound-read 호출이 있을 때마다
+ *   "이 패턴이 사용됐다" 신호를 한 줄 기록.
+ *
+ * MVP 스코프: 신호 *수집*만. 승격 정책(예: 5회 reuse → mature) 은 다음 사이클.
+ *   기록만 잘 쌓이면 임계 설정·승격 로직은 위에 얹기 쉬움.
+ *
+ * 데이터: append-only JSONL at ~/.forgen/state/compound-usage.jsonl
+ *   각 라인: {"at": ISO, "name": "<solution-slug>", "via": "mcp|cli|hook"}
+ *   crash-safe: 단순 fs.appendFileSync — 동시 append 는 OS 가 atomic 보장 (POSIX <PIPE_BUF).
+ */
+export declare const COMPOUND_USAGE_LOG: string;
+export interface UsageEntry {
+    at: string;
+    name: string;
+    via: 'mcp' | 'cli' | 'hook';
+}
+export declare function recordUsage(name: string, via?: UsageEntry['via']): void;
+/** 단순 카운터 — 승격 정책에서 호출. MVP 에선 미사용. */
+export declare function readUsageCounts(): Map<string, number>;

package/dist/store/compound-usage-store.js

@@ -0,0 +1,59 @@
+/**
+ * Forgen — compound usage signal store (Pathfinder D11 fix, MVP).
+ *
+ * 배경 (Deep Interview 2026-04-30 Round 5):
+ *   verified compound 23개, candidate 8개 — 그러나 mature 0. retro 회고에서
+ *   "활용률 측정 불가 — compound-search 호출 카운터 미수집" 확인. 즉 사용자가
+ *   compound 를 reuse 했다는 신호 자체가 잡히지 않아서 mature 승격 입력이 없음.
+ *
+ *   원칙(user-mirror, Round 4 Contrarian): forgen 자기 학습이 아니라 *사용자
+ *   reuse* 가 mature 의 권위 종착점. 따라서 compound-read 호출이 있을 때마다
+ *   "이 패턴이 사용됐다" 신호를 한 줄 기록.
+ *
+ * MVP 스코프: 신호 *수집*만. 승격 정책(예: 5회 reuse → mature) 은 다음 사이클.
+ *   기록만 잘 쌓이면 임계 설정·승격 로직은 위에 얹기 쉬움.
+ *
+ * 데이터: append-only JSONL at ~/.forgen/state/compound-usage.jsonl
+ *   각 라인: {"at": ISO, "name": "<solution-slug>", "via": "mcp|cli|hook"}
+ *   crash-safe: 단순 fs.appendFileSync — 동시 append 는 OS 가 atomic 보장 (POSIX <PIPE_BUF).
+ */
+import * as fs from 'node:fs';
+import * as path from 'node:path';
+import { STATE_DIR } from '../core/paths.js';
+export const COMPOUND_USAGE_LOG = path.join(STATE_DIR, 'compound-usage.jsonl');
+export function recordUsage(name, via = 'mcp') {
+    if (!name)
+        return;
+    try {
+        fs.mkdirSync(STATE_DIR, { recursive: true });
+        const entry = { at: new Date().toISOString(), name, via };
+        fs.appendFileSync(COMPOUND_USAGE_LOG, JSON.stringify(entry) + '\n');
+    }
+    catch {
+        // fail-open: 신호 수집 실패가 사용자 경험을 방해하면 안 됨
+    }
+}
+/** 단순 카운터 — 승격 정책에서 호출. MVP 에선 미사용. */
+export function readUsageCounts() {
+    const counts = new Map();
+    if (!fs.existsSync(COMPOUND_USAGE_LOG))
+        return counts;
+    try {
+        const lines = fs.readFileSync(COMPOUND_USAGE_LOG, 'utf-8').split('\n').filter(Boolean);
+        for (const line of lines) {
+            try {
+                const entry = JSON.parse(line);
+                if (typeof entry.name === 'string') {
+                    counts.set(entry.name, (counts.get(entry.name) ?? 0) + 1);
+                }
+            }
+            catch {
+                // skip malformed
+            }
+        }
+    }
+    catch {
+        // fail-open
+    }
+    return counts;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wooojin/forgen",
-  "version": "0.4.3",
+  "version": "0.4.5",
   "preferGlobal": true,
   "main": "dist/lib.js",
   "types": "./dist/lib.d.ts",

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://claude.ai/schemas/claude-plugin.json",
   "name": "forgen",
-  "version": "0.4.3",
+  "version": "0.4.5",
   "description": "Claude Code harness — the more you use Claude, the better it gets",
   "author": {
     "name": "jang-ujin",

package/scripts/postinstall.js

@@ -516,10 +516,34 @@ function generateAndWriteHooksJson() {
 }
 
 // ── 4. Install slash commands ──
+/** Build-time injected --with-codex shared snippet. Mirror of scripts/copy-assets.js. */
+const WITH_CODEX_SNIPPET = `
+
+---
+
+## \`--with-codex\` flag (cross-model review)
+
+If \`$ARGUMENTS\` contains any of \`--with-codex\`, \`--코덱스\`, \`with codex\`, \`코덱스 검토\`, \`코덱스로 검토\`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., \`/tmp/forgen-with-codex-$(date +%s).md\`).
+2. Invoke codex via Bash:
+   \`\`\`bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \\
+     -s read-only -c approval_policy="never" --skip-git-repo-check \\
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\\\u0027s output. Read the work product below and report ONLY:\\n1. Defects, gaps, or risks the original work missed\\n2. Specific disagreements with the original\\n3. Topics that should have been covered but were not\\n\\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\\n\\n<work>\\n%s\\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   \`\`\`
+3. Append the codex output under heading \`## Codex Cross-Review (--with-codex)\` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If \`codex: command not found\`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+`;
+
 function buildCommandContent(skillContent, skillName) {
   const descMatch = skillContent.match(/description:\s*(.+)/);
   const desc = descMatch?.[1]?.trim() ?? skillName;
-  return `# ${desc}\n\n<!-- forgen-managed -->\n\nActivate Forgen "${skillName}" mode for the task: $ARGUMENTS\n\n${skillContent}`;
+  return `# ${desc}\n\n<!-- forgen-managed -->\n\nActivate Forgen "${skillName}" mode for the task: $ARGUMENTS\n\n${skillContent}${WITH_CODEX_SNIPPET}`;
 }
 
 function safeWriteCommand(cmdPath, content) {
@@ -729,7 +753,7 @@ function cleanLegacyMcpFromSettings(settings) {
  * 이전 방식(3곳에서 각각 read-modify-write)은 중간에 다른 프로세스가
  * settings.json을 수정하면 데이터 유실 가능성이 있었습니다.
  */
-function main() {
+async function main() {
   // W-V2: 로컬 설치 시 전역 설정 수정 방지
   if (!process.env.npm_config_global && process.env.INIT_CWD && process.env.INIT_CWD !== PKG_ROOT) {
     // npm install (로컬) — postinstall 스킵
@@ -906,6 +930,39 @@ function main() {
   // sudo 실행 시 파일 소유권을 실제 유저로 변경
   fixOwnership(join(HOME, '.claude'), join(HOME, '.forgen'));
 
+  // ── 9. Self-check: 설치 산출물이 현재 Node 에서 실제로 로드되는지 확인 ──
+  //
+  // Why: 0.4.4 이전 빌드는 `import ... with { type: 'json' }` 를 사용해 Node
+  //   20.0-20.9 에서 모든 훅이 SyntaxError 로 깨졌다. 사용자는 npm i -g 가 정상
+  //   종료된 직후에야 "각종 훅들이 에러난다"는 증상을 보았다. self-check 가 있었
+  //   다면 install 시점에 즉시 실패를 노출했을 것.
+  //
+  // 동작: dist/hooks/hook-registry.js 를 dynamic import 로 로드 → HOOK_REGISTRY
+  //   배열에 entry 가 있는지 확인. 실패 시 stderr 로 구체적 원인 + Node 버전을
+  //   알리고 npm install 자체는 깨뜨리지 않음 (postinstall 정책 유지).
+  let selfCheckOk = false;
+  let selfCheckErr = '';
+  try {
+    const registryUrl = new URL('../dist/hooks/hook-registry.js', import.meta.url);
+    const mod = await import(registryUrl.href);
+    if (Array.isArray(mod?.HOOK_REGISTRY) && mod.HOOK_REGISTRY.length > 0) {
+      selfCheckOk = true;
+    } else {
+      selfCheckErr = 'HOOK_REGISTRY is empty or not an array';
+    }
+  } catch (err) {
+    selfCheckErr = err?.message ?? String(err);
+  }
+  if (!selfCheckOk) {
+    console.error('');
+    console.error(`[forgen] WARNING: hook self-check FAILED on Node ${process.version}.`);
+    console.error(`[forgen]   reason: ${selfCheckErr}`);
+    console.error('[forgen]   훅이 Claude Code 실행 시 로드 실패할 수 있습니다.');
+    console.error('[forgen]   Node 20.10+ 또는 22.x 사용을 권장합니다.');
+    console.error('[forgen]   문제 지속 시: https://github.com/forgen-team/forgen/issues');
+    console.error('');
+  }
+
   const parts = [];
   if (plugin) parts.push('plugin');
   if (hooksJsonResult) parts.push(`hooks.json (${hooksJsonResult.active}/${hooksJsonResult.total} active)`);
@@ -940,9 +997,7 @@ function main() {
   }
 }
 
-try {
-  main();
-} catch (err) {
+main().catch((err) => {
   // postinstall 실패가 npm install을 깨뜨리지 않되, 원인은 표시
   console.error(`[forgen] postinstall warning: ${err?.message ?? err}`);
-}
+});

package/skills/architecture-decision/SKILL.md

@@ -163,3 +163,24 @@ Positive / Negative / Risks / Follow-up
 </Arguments>
 
 $ARGUMENTS
+
+---
+
+## `--with-codex` flag (cross-model review)
+
+If `$ARGUMENTS` contains any of `--with-codex`, `--코덱스`, `with codex`, `코덱스 검토`, `코덱스로 검토`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., `/tmp/forgen-with-codex-$(date +%s).md`).
+2. Invoke codex via Bash:
+   ```bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \
+     -s read-only -c approval_policy="never" --skip-git-repo-check \
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\u0027s output. Read the work product below and report ONLY:\n1. Defects, gaps, or risks the original work missed\n2. Specific disagreements with the original\n3. Topics that should have been covered but were not\n\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\n\n<work>\n%s\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   ```
+3. Append the codex output under heading `## Codex Cross-Review (--with-codex)` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If `codex: command not found`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+

package/skills/calibrate/SKILL.md

@@ -21,7 +21,8 @@ description: This skill should be used when the user asks to "calibrate, 캘리
 calibrate는 두 가지 데이터 소스를 사용합니다:
 
 ### 1차 소스: Evidence 파일
-`~/.forgen/me/evidence/` 디렉토리의 JSON 파일을 읽습니다.
+`~/.forgen/me/behavior/` 디렉토리의 JSON 파일을 읽습니다.
+(파일명: UUID.json — correction-record MCP 도구가 작성. 같은 디렉토리의 auto-*.md 는 auto-compound 산출이므로 calibrate 분석 대상 아님.)
 각 파일의 구조:
 ```json
 {
@@ -52,8 +53,8 @@ evidence 0건 + compound 교정 패턴 0건이면:
 ## Phase 1: Evidence 로드 및 검증
 
 ```bash
-ls ~/.forgen/me/evidence/ 2>/dev/null || echo "EMPTY"
-cat ~/.forgen/me/evidence/*.json 2>/dev/null || echo "NO_FILES"
+ls ~/.forgen/me/behavior/*.json 2>/dev/null || echo "EMPTY"
+cat ~/.forgen/me/behavior/*.json 2>/dev/null || echo "NO_FILES"
 ```
 
 로드한 JSON 파일마다 다음을 검증합니다:
@@ -205,3 +206,24 @@ Compound 교차 검증:
 </Arguments>
 
 $ARGUMENTS
+
+---
+
+## `--with-codex` flag (cross-model review)
+
+If `$ARGUMENTS` contains any of `--with-codex`, `--코덱스`, `with codex`, `코덱스 검토`, `코덱스로 검토`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., `/tmp/forgen-with-codex-$(date +%s).md`).
+2. Invoke codex via Bash:
+   ```bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \
+     -s read-only -c approval_policy="never" --skip-git-repo-check \
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\u0027s output. Read the work product below and report ONLY:\n1. Defects, gaps, or risks the original work missed\n2. Specific disagreements with the original\n3. Topics that should have been covered but were not\n\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\n\n<work>\n%s\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   ```
+3. Append the codex output under heading `## Codex Cross-Review (--with-codex)` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If `codex: command not found`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+

package/skills/code-review/SKILL.md

@@ -199,3 +199,24 @@ VERDICT: {APPROVE / REQUEST CHANGES / COMMENT}
 </Arguments>
 
 $ARGUMENTS
+
+---
+
+## `--with-codex` flag (cross-model review)
+
+If `$ARGUMENTS` contains any of `--with-codex`, `--코덱스`, `with codex`, `코덱스 검토`, `코덱스로 검토`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., `/tmp/forgen-with-codex-$(date +%s).md`).
+2. Invoke codex via Bash:
+   ```bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \
+     -s read-only -c approval_policy="never" --skip-git-repo-check \
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\u0027s output. Read the work product below and report ONLY:\n1. Defects, gaps, or risks the original work missed\n2. Specific disagreements with the original\n3. Topics that should have been covered but were not\n\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\n\n<work>\n%s\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   ```
+3. Append the codex output under heading `## Codex Cross-Review (--with-codex)` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If `codex: command not found`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+

package/skills/compound/SKILL.md

@@ -157,3 +157,24 @@ NEVER: **Health Dashboard 건너뛰기**: 추출 후 반드시 Phase 5 실행.
 </Arguments>
 
 $ARGUMENTS
+
+---
+
+## `--with-codex` flag (cross-model review)
+
+If `$ARGUMENTS` contains any of `--with-codex`, `--코덱스`, `with codex`, `코덱스 검토`, `코덱스로 검토`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., `/tmp/forgen-with-codex-$(date +%s).md`).
+2. Invoke codex via Bash:
+   ```bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \
+     -s read-only -c approval_policy="never" --skip-git-repo-check \
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\u0027s output. Read the work product below and report ONLY:\n1. Defects, gaps, or risks the original work missed\n2. Specific disagreements with the original\n3. Topics that should have been covered but were not\n\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\n\n<work>\n%s\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   ```
+3. Append the codex output under heading `## Codex Cross-Review (--with-codex)` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If `codex: command not found`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+

package/skills/deep-interview/SKILL.md

@@ -264,3 +264,24 @@ NEVER: **챌린지 모드 건너뛰기**: Round 4+ 이후 반드시 적용.
 </Arguments>
 
 $ARGUMENTS
+
+---
+
+## `--with-codex` flag (cross-model review)
+
+If `$ARGUMENTS` contains any of `--with-codex`, `--코덱스`, `with codex`, `코덱스 검토`, `코덱스로 검토`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., `/tmp/forgen-with-codex-$(date +%s).md`).
+2. Invoke codex via Bash:
+   ```bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \
+     -s read-only -c approval_policy="never" --skip-git-repo-check \
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\u0027s output. Read the work product below and report ONLY:\n1. Defects, gaps, or risks the original work missed\n2. Specific disagreements with the original\n3. Topics that should have been covered but were not\n\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\n\n<work>\n%s\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   ```
+3. Append the codex output under heading `## Codex Cross-Review (--with-codex)` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If `codex: command not found`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+

package/skills/docker/SKILL.md

@@ -144,3 +144,24 @@ SECURITY SCAN / 보안 스캔
 </Arguments>
 
 $ARGUMENTS
+
+---
+
+## `--with-codex` flag (cross-model review)
+
+If `$ARGUMENTS` contains any of `--with-codex`, `--코덱스`, `with codex`, `코덱스 검토`, `코덱스로 검토`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., `/tmp/forgen-with-codex-$(date +%s).md`).
+2. Invoke codex via Bash:
+   ```bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \
+     -s read-only -c approval_policy="never" --skip-git-repo-check \
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\u0027s output. Read the work product below and report ONLY:\n1. Defects, gaps, or risks the original work missed\n2. Specific disagreements with the original\n3. Topics that should have been covered but were not\n\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\n\n<work>\n%s\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   ```
+3. Append the codex output under heading `## Codex Cross-Review (--with-codex)` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If `codex: command not found`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+

package/skills/forge-loop/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: forge-loop
-description: This skill should be used when the user asks to "forge-loop, 포지루프, 끝까지, don't stop". 주어진 작업을 PRD(User Story)로 분해하고, 모든 수용 기준이 충족될 때까지 반복 실행합니다.
+description: This skill should be used when the user asks to "forge-loop, 포지루프, 끝까지, don't stop, goal, 목표, goal lock, scope lock". 작업을 PRD(User Story)로 분해 + 모든 수용 기준 충족까지 반복 실행. `--goal-only` 플래그로 PRD/수용기준 박제만 (실행 사이클 없이) 가능 — goal-locking pattern lightweight 진입점.
 ---
 
 <Purpose>
@@ -73,6 +73,35 @@ EOF
 이 파일이 있어야 Claude가 중간에 멈추지 않도록 Stop 훅이 차단합니다.
 스토리 완료 시 `passes: true`로 업데이트. 전체 완료는 Stop 훅이 자동 처리.
 
+### goal-only 모드 — Phase 1 종료 분기
+
+`$ARGUMENTS` 에 `--goal-only` / `--goal` / `--lock-only` 중 하나가 포함된 경우,
+Phase 1 종료 직후 다음을 산출하고 종료 (Phase 2/3 건너뜀):
+
+1. 위 PRD JSON 의 stories 배열을 markdown Goal 박스로 변환:
+   ```
+   GOAL: <stories[0].title — 단일 story 면 한 문장 요약>
+   완료 기준 (Acceptance Criteria):
+     - [ ] <story[i].acceptanceCriteria[j] 각각 — 구체적 증거 타입 포함>
+   제약 (Out-of-Scope):
+     - <"수용 기준 품질 규칙" 표의 금지 패턴들>
+     - <사용자가 명시한 dry-run / touch 안 할 경로 등>
+   검증 방법:
+     - <각 AC 의 verification command (bash / curl / file check)>
+   컴파운드 패턴 (참고):
+     - <compound-search top 1-2 결과 — 본 작업 키워드로 검색>
+   ```
+
+2. 사용자에게 박스를 보여주고 안내:
+   ```
+   GOAL 박제 완료. 다음 옵션:
+   - 이 박스를 다른 컨텍스트/에이전트에 위임 → 복사 사용
+   - 본 세션에서 자동 실행 → `forge-loop resume` 로 Phase 2 이어 실행
+   상태 파일: ~/.forgen/state/forge-loop.json (resume 시 재활용)
+   ```
+
+3. 종료. **Anti-Polite-Stop 규칙은 goal-only 모드에 적용 안 함** — 박제가 목적이고 실행은 명시적 escalation 시에만.
+
 ## Phase 2: 스토리 실행 루프
 
 ### 2-1. Compound-In (스토리별)
@@ -193,6 +222,52 @@ compound에 저장하시겠습니까? [Y/n]
 <Arguments>
 - `[task description]`: 실행할 작업 설명. 생략 시 현재 대화 컨텍스트에서 추론.
 - `resume`: 이전에 중단된 루프를 재개합니다.
+- `--goal-only` (또는 `--goal`, `--lock-only`): **goal-locking lightweight 모드**.
+  Phase 1 (PRD + 수용 기준 + 상태 파일 저장) 까지만 실행하고 Phase 2/3 (자동
+  실행 루프 + 최종 검증) 은 건너뜁니다. 산출물은 *구조화된 Goal 박스* — 작업
+  범위 / 완료 기준 / 제약 / 검증 방법을 한 markdown 으로 박제. 사용자가 다른
+  컨텍스트나 에이전트에 그대로 붙여 위임 가능. 추후 `forge-loop resume` 로
+  자동 실행 사이클 escalate 가능 (상태 파일 재활용).
+
+  goal-only 모드의 산출물 포맷:
+  ```
+  GOAL: <한 문장 요약>
+  완료 기준 (Acceptance Criteria — 증거 타입 포함):
+    - [ ] AC1: <테스트 로그 / 파일 변경 / dry-run 출력>
+    - [ ] AC2: ...
+  제약 (Out-of-Scope / 안 할 것):
+    - <실 발송·배포·삭제 금지 / dry-run 한정>
+    - <touch 안 할 경로>
+  검증 방법:
+    - <bash 명령 / 파일 확인 / 외부 verification>
+  컴파운드 패턴 (참고):
+    - <compound-search 결과 top 1-2>
+  ```
+
+  goal-only 모드는 stop-guard 의 fact-vs-agreement / self-score-inflation
+  체크와 직접 연동 — Goal 박스 박제 후 응답이 "완료" 주장 시 AC 의 증거가
+  포함되어야 통과.
 </Arguments>
 
 $ARGUMENTS
+
+---
+
+## `--with-codex` flag (cross-model review)
+
+If `$ARGUMENTS` contains any of `--with-codex`, `--코덱스`, `with codex`, `코덱스 검토`, `코덱스로 검토`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., `/tmp/forgen-with-codex-$(date +%s).md`).
+2. Invoke codex via Bash:
+   ```bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \
+     -s read-only -c approval_policy="never" --skip-git-repo-check \
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\u0027s output. Read the work product below and report ONLY:\n1. Defects, gaps, or risks the original work missed\n2. Specific disagreements with the original\n3. Topics that should have been covered but were not\n\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\n\n<work>\n%s\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   ```
+3. Append the codex output under heading `## Codex Cross-Review (--with-codex)` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If `codex: command not found`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+

package/skills/learn/SKILL.md

@@ -214,3 +214,24 @@ PRUNE CANDIDATES / 정리 후보
 </Arguments>
 
 $ARGUMENTS
+
+---
+
+## `--with-codex` flag (cross-model review)
+
+If `$ARGUMENTS` contains any of `--with-codex`, `--코덱스`, `with codex`, `코덱스 검토`, `코덱스로 검토`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., `/tmp/forgen-with-codex-$(date +%s).md`).
+2. Invoke codex via Bash:
+   ```bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \
+     -s read-only -c approval_policy="never" --skip-git-repo-check \
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\u0027s output. Read the work product below and report ONLY:\n1. Defects, gaps, or risks the original work missed\n2. Specific disagreements with the original\n3. Topics that should have been covered but were not\n\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\n\n<work>\n%s\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   ```
+3. Append the codex output under heading `## Codex Cross-Review (--with-codex)` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If `codex: command not found`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+

package/skills/retro/SKILL.md

@@ -53,8 +53,8 @@ compound-list
 ### 1-3: 교정 기록
 
 ```bash
-ls -la ~/.forgen/me/evidence/ 2>/dev/null || echo "교정 데이터 없음"
-find ~/.forgen/me/evidence/ -name "*.json" -mtime -{period_days} 2>/dev/null | wc -l
+ls -la ~/.forgen/me/behavior/ 2>/dev/null || echo "교정 데이터 없음"
+find ~/.forgen/me/behavior/ -name "*.json" -mtime -{period_days} 2>/dev/null | wc -l
 ```
 
 ## Phase 2: 코드 활동 분석
@@ -197,3 +197,24 @@ RECOMMENDATIONS
 </Arguments>
 
 $ARGUMENTS
+
+---
+
+## `--with-codex` flag (cross-model review)
+
+If `$ARGUMENTS` contains any of `--with-codex`, `--코덱스`, `with codex`, `코덱스 검토`, `코덱스로 검토`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., `/tmp/forgen-with-codex-$(date +%s).md`).
+2. Invoke codex via Bash:
+   ```bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \
+     -s read-only -c approval_policy="never" --skip-git-repo-check \
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\u0027s output. Read the work product below and report ONLY:\n1. Defects, gaps, or risks the original work missed\n2. Specific disagreements with the original\n3. Topics that should have been covered but were not\n\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\n\n<work>\n%s\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   ```
+3. Append the codex output under heading `## Codex Cross-Review (--with-codex)` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If `codex: command not found`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+

package/skills/ship/SKILL.md

@@ -257,3 +257,24 @@ Action:  {다음 행동}
 </Arguments>
 
 $ARGUMENTS
+
+---
+
+## `--with-codex` flag (cross-model review)
+
+If `$ARGUMENTS` contains any of `--with-codex`, `--코덱스`, `with codex`, `코덱스 검토`, `코덱스로 검토`,
+then after completing the primary skill work, perform a cross-model review pass:
+
+1. Save your primary output text to a temp file (e.g., `/tmp/forgen-with-codex-$(date +%s).md`).
+2. Invoke codex via Bash:
+   ```bash
+   codex exec --json --ignore-user-config --ignore-rules --ephemeral \
+     -s read-only -c approval_policy="never" --skip-git-repo-check \
+     "$(printf 'You are a second-opinion reviewer for another AI assistant\\u0027s output. Read the work product below and report ONLY:\n1. Defects, gaps, or risks the original work missed\n2. Specific disagreements with the original\n3. Topics that should have been covered but were not\n\nOutput format: prioritized bullet list (max 15 items, severity-sorted, no prose intro). If you find nothing material, say "No critical issues found."\n\n<work>\n%s\n</work>' "$(cat /tmp/forgen-with-codex-*.md)")"
+   ```
+3. Append the codex output under heading `## Codex Cross-Review (--with-codex)` in your final response.
+4. If codex flags critical issues, briefly acknowledge + suggest follow-up.
+5. If `codex: command not found`, note in response and skip the review pass (do not fail).
+
+OPT-IN per invocation. Without the flag, skip this entire section.
+