create-harness-vibe-coding 0.5.2 → 0.6.1

package/README.md

@@ -26,7 +26,7 @@ Follow the README at https://github.com/zingspark/create-harness-vibe-coding to
 
 That's it. Two paths into the harness — you type `npx`, or your agent reads the sentence.
 
-[README-CN.md](README-CN.md) (中文)
+Chinese README: [README-CN.md](README-CN.md)
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-harness-vibe-coding",
-  "version": "0.5.2",
+  "version": "0.6.1",
   "description": "Scaffold a 0-1 product harness for AI-assisted research, PRD, planning, architecture, build, test, and feedback loops",
   "type": "module",
   "bin": {

package/src/generator.js

@@ -2,7 +2,9 @@ import fs from 'node:fs';
 import path from 'node:path';
 import { fileURLToPath } from 'node:url';
 
-const __dirname = path.dirname(fileURLToPath(import.meta.url));
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = path.dirname(__filename);
+const pkg = JSON.parse(fs.readFileSync(path.resolve(__dirname, '../package.json'), 'utf8'));
 const TEMPLATES_DIR = path.resolve(__dirname, '..', 'templates', 'common');
 const OPTIONAL_DIR = path.resolve(__dirname, '..', 'templates', 'optional');
 const OPTIONAL_CATALOG = path.join(OPTIONAL_DIR, 'catalog.json');
@@ -327,7 +329,11 @@ export function generate({
 
   // Resolve targetDir relative to cwd
   const resolvedDir = path.resolve(process.cwd(), targetDir);
-  const vars = { projectName };
+  const vars = {
+    projectName,
+    generatorVersion: pkg.version,
+    generatedTimestamp: new Date().toISOString(),
+  };
 
   const optional = resolveOptionalSelection({ withOptions, withoutOptions, preset });
   const fileSpecs = [

package/templates/common/.claude/agents/context-master.md

@@ -1,7 +1,7 @@
 ---
 name: context-master
 description: Use when context exceeds ~85% of the window, or during WF closeout to extract durable knowledge before compression. Read-only analysis except for writing compression suggestions to PROGRESS.md#Heartbeat.
-tools: Read, Grep, Glob
+tools: Read, Grep, Glob, Write
 model: haiku
 skills: harness-context
 ---

package/templates/common/.claude/agents/reviewer.md

@@ -22,6 +22,7 @@ Rules:
 - Do not write files.
 - Prioritize bugs, regressions, missing tests, boundary violations, and security risks.
 - Findings must include file and line when possible.
+- Flag unsupported factual claims: if a code comment, doc line, or agent output asserts a fact you cannot confirm by reading the referenced file, report it as a "Hallucination Risk" finding.
 - Separate critical/high findings from minor cleanup.
 - If no issues are found, state residual risk and test gaps.
 

package/templates/common/.claude/commands/wf-review.md

@@ -0,0 +1,32 @@
+# /wf-review [focus]
+
+Cross-model peer review. Invokes the OTHER agent CLI to review changes from a fresh perspective.
+
+## How it works
+
+1. Detect which runtime we're running under
+2. Prepare context: diff, relevant files, architecture docs, problem description
+3. Pipe to the OTHER CLI for independent review
+4. Synthesize the response
+
+## Required
+
+- Load `wf-review` skill.
+- MUST use `Bash` to invoke the other CLI — never simulate or fake the review.
+- Present the raw review output to the user, then add your own analysis.
+
+## CLI Detection
+
+- Check `which codex && echo CODEX || echo NO_CODEX` to detect Codex
+- Check `which claude && echo CLAUDE || echo NO_CLAUDE` to detect Claude
+- Use the OTHER CLI — the one NOT running this session. Never self-review.
+- If only one CLI is available: warn, then use it (single-model review is better than none).
+
+## Flow
+
+```text
+CEO prepares context (diff + architecture docs + focus prompt)
+→ Bash: codex exec "..."  (or claude -p "...")
+→ CEO reads output
+→ CEO presents findings + own analysis
+```

package/templates/common/.claude/skills/wf-review/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: wf-review
+description: Cross-model peer review. Invokes the other agent CLI (Codex or Claude) to independently review changes, architecture, or bug fixes. Use for /wf-review, peer review, second opinion, or when stuck.
+---
+
+# WF Review
+
+Cross-model peer review via the OTHER agent CLI. Fresh eyes on your changes.
+
+## Load
+
+- `Harness/README.md` for project context
+- Current diff or target files
+
+## How It Works
+
+1. **Detect runtime**: Check `which codex` and `which claude`
+2. **Prepare context**: Gather diff (`git diff`), relevant architecture docs, the specific question
+3. **Invoke the OTHER CLI** — the one we're NOT currently running under
+4. **Read and synthesize**: Present the raw output, then add analysis
+
+## CLI Commands
+
+| Runtime | Review Command |
+|---|---|
+| Claude → Codex | `git diff \| codex exec "..."` (include full diff, not just commit message) |
+| Codex → Claude | `git diff \| claude -p "..."` |
+| Either (fallback) | try the other CLI; if only one installed, use it (still better than self-review) |
+
+**Anti-self-review rule**: Detect which runtime we're in, then use the OTHER one. Never invoke the same CLI that's running the session.
+
+## Context to Include
+
+For a good review, pipe or include:
+- `git diff` or `git diff --cached`
+- Relevant `Harness/` docs (architecture.md, domain/ports.md if filled)
+- The specific focus: "find bugs", "critique architecture from 4+ dimensions", "fix this bug", "check for security issues"
+
+## Rules
+
+- Never simulate or fake the review. The Bash tool MUST invoke the other CLI.
+- If both CLIs fail, report the error — don't silently skip.
+- Present the raw review output to the user before adding your own analysis.
+- Distinguish between: the peer's findings (authoritative) and your interpretation (supplementary).
+
+## Return
+
+- Which CLI was used for review
+- Raw review output
+- CEO's synthesis and action items

package/templates/common/CLAUDE.md

@@ -11,7 +11,7 @@ Root entry for Claude Code. Keep this file short.
 - `Harness/README.md` is the task router. For every request, check `Harness/README.md#Load By Task`; if a row matches, read and follow those docs before acting.
 - `Harness/PROGRESS.md` is the global task index. Load at session start to see active task and task history.
 - If work spans more than one step, create a task capsule from `Harness/tasks/_template/` and update `Harness/tasks/<task-id>/PROGRESS.md`.
-- Use `/wf <task>`, `/wf-max [task]`, `/wf-learn`, `wf mode`, `wf max`, `workflow mode`, `wk mode`, `Harness/WF.md`, or `Harness/WF-MAX.md` for long, difficult, uncertain, multi-file, or repeated-failure work.
+- Use `/wf <task>`, `/wf-max [task]`, `/wf-learn`, `/wf-review [focus]`, `wf mode`, `wf max`, `workflow mode`, `wk mode`, `Harness/WF.md`, or `Harness/WF-MAX.md` for long, difficult, uncertain, multi-file, or repeated-failure work.
 - Use `subagent-orchestrator` and `Harness/subagents.md` when coordinating multiple subagents.
 - Use `/wf update` to check for and apply scaffold updates from GitHub. See `.claude/skills/wf-update/SKILL.md`.
 - Subagents are readers and reporters. Only the main agent writes to `Harness/tasks/<task-id>/PROGRESS.md` and `Harness/tasks/<task-id>/PLAN.md`.
@@ -27,6 +27,7 @@ Root entry for Claude Code. Keep this file short.
 - If multiple valid approaches exist and the choice affects architecture, scope, stack, or user-facing behavior, present trade-offs instead of picking silently.
 - State assumptions before implementation and record durable assumptions, decisions, blockers, handoffs, and verification evidence in `Harness/tasks/<task-id>/PLAN.md`.
 - If something is unclear, stop. Name what is unclear and ask instead of guessing.
+- Before asserting a fact about the codebase, read the file that proves it. If you cannot cite the file and line, do not assert.
 
 ## 3. Simplicity First
 
@@ -72,3 +73,4 @@ Root entry for Claude Code. Keep this file short.
 
 - Never call `EnterPlanMode` — delegate planning to `planner` subagents (see `Harness/WF.md`).
 - Never write code directly in `/wf` or `/wf-max` mode — delegate all implementation to subagents (see `Harness/WF-MAX.md`).
+- **Enforcement**: `.claude/settings.json` hooks prevent `EnterPlanMode` calls. Settings include `allowTools: ["!EnterPlanMode"]` for the main session.

package/templates/common/MEMORY.md

@@ -29,6 +29,7 @@ Stack-specific agents can be added after the product shape is known.
 - [wf-mode](../.claude/skills/wf-mode/SKILL.md) — long-task workflow: exploration, second plan, implementation, review, verification, heartbeat, and recovery loop.
 - [subagent-orchestrator](../.claude/skills/subagent-orchestrator/SKILL.md) — controller-led subagent orchestration, parallel read-only passes, review gates, and recovery handoffs.
 - [readme-optimizer](../.claude/skills/readme-optimizer/SKILL.md) — README preservation, append-only development sections, structured tables, and approved architecture diagrams.
+- [wf-review](../.claude/skills/wf-review/SKILL.md) — cross-model peer review: invoke the other agent CLI (Codex/Claude) for independent review.
 - [wf-learn](../.claude/skills/wf-learn/SKILL.md) — force memory learning cycle: context-master → memory-master → project + global memory.
 - [wf-update](../.claude/skills/wf-update/SKILL.md) — GitHub-based incremental harness update, checksum comparison, and safe in-place updates.
 - [wf-max](../.claude/skills/wf-max/SKILL.md) — maximum-parallelism workflow: write-set coloring, wave dispatch, parallel review per dimension.

package/templates/common/docs/README.md

@@ -61,6 +61,7 @@ Routing priority: if a request explicitly says `/wf <task>`, `/wf-max [task]`, `
 | Need architecture or boundaries | architecture, boundary, layer, domain, port, adapter, dependency | [architecture.md](architecture.md), [domain/ports.md](domain/ports.md) | layer map, ports, constraints |
 | Need WF mode | wf, /wf, wf mode, workflow mode, wk mode, long task, difficult, stuck, repeated failure | [WF.md](WF.md), [PROGRESS.md](PROGRESS.md), the current task `tasks/<id>/PROGRESS.md` and `tasks/<id>/PLAN.md` | exploration plan, second plan, heartbeat, recovery loop; explicit WF/WK loads subagent docs immediately |
 | Need to learn from errors | /wf-learn, wf learn, learn, remember, memory, lesson | [MEMORY.md](MEMORY.md), `.claude/skills/wf-learn/SKILL.md`, `Harness/memory/*` | context-master → memory-master → project + global memory |
+| Need peer review | /wf-review, peer review, second opinion, cross-check, stuck | `.claude/skills/wf-review/SKILL.md`, `Harness/README.md` | cross-model review via other CLI (Codex/Claude) |
 | Need WF Max mode | /wf-max, wf max, maximum parallelism, max parallel | [WF-MAX.md](WF-MAX.md), [WF.md](WF.md), [subagents.md](subagents.md), [dispatch.md](dispatch.md) | max-parallel exploration, write-set coloring, wave dispatch |
 | Adding harness to existing project | existing project, onboarding, migrate, bootstrap, preserve, conflict | [extension.md](extension.md), [PROGRESS.md](PROGRESS.md), root `README.md` and package/CI files | discovered project facts, preserved config, manual registration plan |
 | README optimization | README, docs, quickstart, install docs, architecture diagram, command table, documentation polish | root `README.md`, `.claude/skills/readme-optimizer/SKILL.md`, [PROGRESS.md](PROGRESS.md), [architecture.md](architecture.md) as needed | approved README mode, preserved sections, proposed diff plan |
@@ -111,8 +112,10 @@ Harness/tasks/_template/           task capsule template (copy to create new tas
 Harness/WF.md                      long-task workflow and recovery loop
 Harness/WF-MAX.md                  max-parallelism workflow with wave dispatch
 .claude/skills/wf-max/SKILL.md     max-parallelism skill loader
+.claude/skills/wf-review/SKILL.md  cross-model peer review skill
 .claude/commands/wf-max.md         /wf-max slash command bridge
 .claude/commands/learn.md          /wf-learn slash command bridge
+.claude/commands/wf-review.md      /wf-review slash command bridge
 Harness/lifecycle.md               0-1 product flow
 Harness/subagents.md               controller-led subagent orchestration
 Harness/context-loading.md         dynamic loading and subagent packs

package/templates/common/docs/harness/WF-MAX.md

@@ -22,7 +22,7 @@ CEO(1) ──┬── Manager₁(span) ──┬── Worker₁..ₙ
 ```
 
 - CEO: intent, scope, integration, final verification. Direct reports 3-5 Managers. **CEO never writes code directly** — dispatch Workers for all file changes. CEO only synthesizes results and decides next waves.
-- Manager: domain partition → parallel dispatch → synthesize → report. Serial across domains; parallel within domain.
+- Manager: domain partition → parallel dispatch → synthesize → report. Serial across domains; parallel within domain. **Manager agents must be defined by the project** (not shipped by the harness) — create them under `.claude/agents/` with the `Agent` tool enabled for nested spawning.
 - Worker: single file per write Worker (implementer, one file_claim). Single dimension/topic per read Worker (reviewer, researcher). File claims must be file-level disjoint. Topic-level splitting within a single file is only allowed for read-only Workers.
 - depth ≥3: Manager spawns Sub-Manager (span ≤7) instead of Worker. Recursive until leaf condition met.