claude2codex 0.3.2 → 0.3.3

package/README.md

@@ -18,7 +18,7 @@ In 2025, AI-assisted coding meant writing detailed prompts that told the model *
 
 That has changed. In 2026, models are [strong enough at implementation](https://www.anthropic.com/institute/recursive-self-improvement) that micromanaging the how is no longer the best use of a human's time. The bottleneck has shifted: when implementation is cheap, the expensive mistakes are **defining the wrong problem** and **failing to catch a bad result**. Getting the implementation steps right matters far less than getting the goal right.
 
-This is why Goal Contracts are structured the way they are. They don't explain how to write the code — they define **what the code must do** (the Goal) and **how to prove it worked** (Success Conditions). The engineer's role becomes problem definition, context provision, and verification — the same things that make a good engineering manager effective at delegation.
+This is why Goal Contracts are structured the way they are. They don't explain how to write the code — they define **what the code must do** (the Goal), **what to avoid** (Constraints), and **how to prove it worked** (Success Conditions). The engineer's role becomes problem definition, context provision, and verification — the same things that make a good engineering manager effective at delegation.
 
 This project is built on that premise: split planning and review (where human judgment still dominates) from implementation (where models now excel), and connect them with a contract format that forces clarity on the parts that matter most.
 
@@ -130,22 +130,63 @@ Add to your Claude Code MCP settings:
 }
 ```
 
-### Skill (optional)
+### Workflow Prompt (automatic)
 
-The package includes a Claude Code Skill that teaches Claude the full contract workflow — drafting Goal Contracts, delegating to Codex, reviewing handoffs, and reworking failures. Install it to use `/c2c` from any project:
+The server registers an MCP Prompt (`c2c-workflow`) that teaches Claude the full contract workflow — role assignment, Goal/Delta Contract formats, review protocol. **This is loaded automatically when the MCP server is connected.** No extra installation needed.
 
-```sh
-mkdir -p ~/.claude/skills
-cp "$(npm root -g)/claude2codex/c2c.skill.md" ~/.claude/skills/c2c.md
+### Project Setup: CLAUDE.md and AGENTS.md
+
+The MCP server handles the workflow protocol. Your project files only need to carry **project-specific context** — don't repeat what the server already provides.
+
+**`CLAUDE.md`** (for Claude — the architect/reviewer):
+
+```markdown
+# Claude Code Guidelines
+
+The contract workflow is delivered by the MCP Prompt `c2c-workflow`.
+
+## Session Startup
+Read README.md and docs/design.md at session start.
+
+## Review Additions
+- Flag security issues (OWASP top 10).
+- Run integration tests against staging after each task.
+
+## Constraints
+- Do not modify migrations without explicit approval.
 ```
 
-Or download directly:
+**`AGENTS.md`** (for Codex — the implementer):
 
-```sh
-mkdir -p ~/.claude/skills
-curl -fsSL https://raw.githubusercontent.com/PrestoOverture/c2c/main/c2c.skill.md -o ~/.claude/skills/c2c.md
+```markdown
+# Codex Guidelines
+
+You are the implementer. The contract protocol is delivered by the c2c bridge.
+
+## Toolchain
+Python 3.12, Poetry. Run from project root.
+- `poetry run pytest` — test suite
+- `poetry run ruff check .` — lint
+- `poetry run mypy .` — typecheck
+
+## Boundaries
+- Do not modify alembic migrations directly.
+- Do not add runtime dependencies without a contract constraint.
 ```
 
+**What goes where:**
+
+| | MCP server (automatic) | CLAUDE.md | AGENTS.md |
+|---|---|---|---|
+| Role definition | ✓ | — | — |
+| Workflow steps | ✓ | — | — |
+| Contract formats | ✓ | — | — |
+| Review protocol | ✓ | — | — |
+| Session startup | — | ✓ | ✓ |
+| Project-specific review rules | — | ✓ | — |
+| Toolchain & build commands | — | — | ✓ |
+| File/dependency boundaries | — | — | ✓ |
+
 ## Tools Provided
 
 | Tool | Description |

package/README.zh-CN.md

@@ -18,7 +18,7 @@
 
 这已经变了。2026 年，模型的[实现能力已经足够强](https://www.anthropic.com/institute/recursive-self-improvement)，事无巨细地指挥"怎么写"不再是人最好的时间投入方式。瓶颈转移了：当实现变得廉价，真正昂贵的错误是**定义了错误的问题**和**没有验收出坏的结果**。把实现步骤写对，远不如把目标定义对重要。
 
-这就是为什么 Goal Contract 被设计成这样。它不解释怎么写代码——它定义**代码必须做到什么**（Goal）和**怎么证明做对了**（Success Conditions）。工程师的角色变成了问题定义、上下文补充和验收——和一个好的工程管理者委派任务时做的事情一样。
+这就是为什么 Goal Contract 被设计成这样。它不解释怎么写代码——它定义**代码必须做到什么**（Goal），**要避免做什么**（Constraints）和**怎么证明做对了**（Success Conditions）。工程师的角色变成了问题定义、上下文补充和验收——和一个好的工程管理者委派任务时做的事情一样。
 
 这个项目建立在这个前提上：把规划和审查（人的判断力仍然占主导）与实现（模型已经足够强）分开，用一种契约格式把它们连接起来，迫使工程师在最重要的部分(问题定义和验收标准)上做到清晰。
 
@@ -130,22 +130,63 @@ npx claude2codex
 }
 ```
 
-### Skill（可选）
+### 工作流 Prompt（自动）
 
-包内附带一个 Claude Code Skill，教 Claude 完整的契约工作流——起草 Goal Contract、委派给 Codex、审查 handoff、失败时返工。安装后可在任何项目中使用 `/c2c`：
+服务器注册了一个 MCP Prompt（`c2c-workflow`），教 Claude 完整的契约工作流——角色分配、Goal/Delta Contract 格式、审查协议。**连接 MCP 服务器后自动加载。** 无需额外安装。
 
-```sh
-mkdir -p ~/.claude/skills
-cp "$(npm root -g)/claude2codex/c2c.skill.md" ~/.claude/skills/c2c.md
+### 项目配置：CLAUDE.md 和 AGENTS.md
+
+MCP 服务器负责工作流协议。你的项目文件只需要放**项目特有的上下文**——不要重复服务器已经提供的内容。
+
+**`CLAUDE.md`**（给 Claude——架构师/审查者）：
+
+```markdown
+# Claude Code Guidelines
+
+契约工作流由 MCP Prompt `c2c-workflow` 提供。
+
+## 会话启动
+开始时阅读 README.md 和 docs/design.md。
+
+## 审查补充
+- 标记安全问题（OWASP top 10）。
+- 每个任务完成后跑一遍 staging 的集成测试。
+
+## 约束
+- 未经明确批准不得修改 migrations。
 ```
 
-或直接下载：
+**`AGENTS.md`**（给 Codex——实现者）：
 
-```sh
-mkdir -p ~/.claude/skills
-curl -fsSL https://raw.githubusercontent.com/PrestoOverture/c2c/main/c2c.skill.md -o ~/.claude/skills/c2c.md
+```markdown
+# Codex Guidelines
+
+你是实现者。契约协议由 c2c bridge 提供。
+
+## 工具链
+Python 3.12，Poetry。从项目根目录运行。
+- `poetry run pytest` — 测试套件
+- `poetry run ruff check .` — 代码检查
+- `poetry run mypy .` — 类型检查
+
+## 边界
+- 不要直接修改 alembic migrations。
+- 未经合同约束不得添加运行时依赖。
 ```
 
+**什么放哪里：**
+
+| | MCP 服务器（自动） | CLAUDE.md | AGENTS.md |
+|---|---|---|---|
+| 角色定义 | ✓ | — | — |
+| 工作流步骤 | ✓ | — | — |
+| 契约格式 | ✓ | — | — |
+| 审查协议 | ✓ | — | — |
+| 会话启动 | — | ✓ | ✓ |
+| 项目特有的审查规则 | — | ✓ | — |
+| 工具链与构建命令 | — | — | ✓ |
+| 文件/依赖边界 | — | — | ✓ |
+
 ## 提供的工具
 
 | 工具 | 说明 |

package/dist/server.js

@@ -262,7 +262,7 @@ var CodexAppServer = class {
    */
   async initialize() {
     const result = await this.request("initialize", {
-      clientInfo: { name: "claude2codex", title: "Claude\u2194Codex Contract Bridge", version: "0.3.1" },
+      clientInfo: { name: "claude2codex", title: "Claude\u2194Codex Contract Bridge", version: "0.3.3" },
       capabilities: { experimentalApi: true }
     });
     this.notify("initialized", {});
@@ -930,7 +930,7 @@ function textResult(obj, isError = false) {
     isError
   };
 }
-var server = new McpServer({ name: "c2c-codex", version: "0.3.1" });
+var server = new McpServer({ name: "c2c-codex", version: "0.3.3" });
 var reasoningEffort = z.enum(["low", "medium", "high", "xhigh", "max", "ultra"]);
 var contextFiles = z.array(z.object({
   path: z.string().min(1),
@@ -1183,5 +1183,66 @@ server.registerTool(
     });
   }
 );
+server.registerPrompt("c2c-workflow", {
+  description: "Delegate implementation to Codex via Goal Contracts. Draft, send, poll, review, rework."
+}, () => ({
+  messages: [{
+    role: "user",
+    content: { type: "text", text: `
+You are the **architect and reviewer**. Codex is the **implementer**. You draft contracts, delegate via the \`codex\` MCP server, and review the output. You do not implement the task yourself.
+
+If \`codex_config\` errors, tell the user to install the MCP server (npm: \`claude2codex\`).
+
+## Workflow
+
+1. **User decides** what to build or fix.
+2. **You draft a Goal Contract** (format below). Show it to the user for approval.
+3. **You send it** \u2014 \`codex_estimate\` to check budget, then \`codex_implement\`.
+4. **You poll** \u2014 \`codex_status\` until terminal. Report progress to the user.
+5. **You review** \u2014 \`codex_result\` for the handoff, then verify independently (see Review below).
+6. **User approves** your findings.
+
+If review fails \u2192 draft a **Delta Contract** \u2192 \`codex_rework\` (same \`job_id\`, thread resumes) \u2192 re-enter at step 4.
+
+## Goal Contract
+
+\`\`\`
+### Goal
+What the code must do. First sentence = acceptance test in prose.
+
+### Constraints
+Only what Codex would get wrong without being told. One line of
+"only modify files needed for this task" covers the rest.
+
+### Success Conditions
+- [ ] Assertions, not paragraphs. At least one is a command whose exit code decides.
+- [ ] Handoff includes: Changed Files, Validation, Success Conditions, Risks & Deviations.
+\`\`\`
+
+**Write lean contracts.** Goal and Success Conditions are what Codex acts on. Constraints are for genuine risks only \u2014 don't front-load your review checklist into the contract.
+
+## Delta Contract
+
+\`\`\`
+### Findings
+- What is wrong, with file/line references.
+
+### Failed Success Conditions
+- [ ] The specific conditions that did not pass.
+
+### Constraints
+- Original constraints still apply. Fix only the findings; do not touch work that passed.
+\`\`\`
+
+## Review
+
+1. Handoff must be complete (all four sections). Missing handoff = review failure.
+2. Re-run every verification command yourself \u2014 do not trust the handoff's claims.
+3. Run the project's own typecheck/build/test/lint.
+4. Flag security issues and constraint violations.
+5. Report findings to the user. Fix small issues (typos, imports) directly; do not rewrite the implementation.
+` }
+  }]
+}));
 var transport = new StdioServerTransport();
 await server.connect(transport);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude2codex",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "type": "module",
   "description": "MCP server bridging Claude (architect/reviewer) and Codex (implementer) via Goal/Delta Contracts and Codex's thread-goal loop.",
   "bin": {
@@ -9,8 +9,7 @@
   "files": [
     "dist",
     "PATTERNS.md",
-    "PATTERNS.zh-CN.md",
-    "c2c.skill.md"
+    "PATTERNS.zh-CN.md"
   ],
   "keywords": [
     "mcp",
@@ -31,8 +30,8 @@
     "start": "bun src/server.ts",
     "build": "tsup",
     "test": "bun test",
-    "prepack": "cp ../README.md ../README.zh-CN.md ../PATTERNS.md ../PATTERNS.zh-CN.md ../c2c.skill.md .",
-    "postpack": "rm -f README.md README.zh-CN.md PATTERNS.md PATTERNS.zh-CN.md c2c.skill.md"
+    "prepack": "cp ../README.md ../README.zh-CN.md ../PATTERNS.md ../PATTERNS.zh-CN.md .",
+    "postpack": "rm -f README.md README.zh-CN.md PATTERNS.md PATTERNS.zh-CN.md"
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",

package/c2c.skill.md

@@ -1,58 +0,0 @@
----
-name: c2c
-description: Delegate implementation to Codex via Goal Contracts. Draft, send, poll, review, rework.
-trigger: When the user wants to delegate implementation work to Codex, or types /c2c.
----
-
-You are the **architect and reviewer**. Codex is the **implementer**. You draft contracts, delegate via the `codex` MCP server, and review the output. You do not implement the task yourself.
-
-If `codex_config` errors, tell the user to install the MCP server (npm: `claude2codex`).
-
-## Workflow
-
-1. **User decides** what to build or fix.
-2. **You draft a Goal Contract** (format below). Show it to the user for approval.
-3. **You send it** — `codex_estimate` to check budget, then `codex_implement`.
-4. **You poll** — `codex_status` until terminal. Report progress to the user.
-5. **You review** — `codex_result` for the handoff, then verify independently (see Review below).
-6. **User approves** your findings.
-
-If review fails → draft a **Delta Contract** → `codex_rework` (same `job_id`, thread resumes) → re-enter at step 4.
-
-## Goal Contract
-
-```
-### Goal
-What the code must do. First sentence = acceptance test in prose.
-
-### Constraints
-Only what Codex would get wrong without being told. One line of
-"only modify files needed for this task" covers the rest.
-
-### Success Conditions
-- [ ] Assertions, not paragraphs. At least one is a command whose exit code decides.
-- [ ] Handoff includes: Changed Files, Validation, Success Conditions, Risks & Deviations.
-```
-
-**Write lean contracts.** Goal and Success Conditions are what Codex acts on. Constraints are for genuine risks only — don't front-load your review checklist into the contract.
-
-## Delta Contract
-
-```
-### Findings
-- What is wrong, with file/line references.
-
-### Failed Success Conditions
-- [ ] The specific conditions that did not pass.
-
-### Constraints
-- Original constraints still apply. Fix only the findings; do not touch work that passed.
-```
-
-## Review
-
-1. Handoff must be complete (all four sections). Missing handoff = review failure.
-2. Re-run every verification command yourself — do not trust the handoff's claims.
-3. Run the project's own typecheck/build/test/lint.
-4. Flag security issues and constraint violations.
-5. Report findings to the user. Fix small issues (typos, imports) directly; do not rewrite the implementation.