create-harness-vibe-coding 0.4.1 → 0.4.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-harness-vibe-coding",
3
- "version": "0.4.1",
3
+ "version": "0.4.2",
4
4
  "description": "Scaffold a 0-1 product harness for AI-assisted research, PRD, planning, architecture, build, test, and feedback loops",
5
5
  "type": "module",
6
6
  "bin": {
@@ -70,7 +70,5 @@ Root entry for Claude Code. Keep this file short.
70
70
 
71
71
  ## 7. CEO Constraints
72
72
 
73
- - Never call `EnterPlanMode` — it blocks the session waiting for user confirmation. Delegate all planning to `planner` subagents.
74
- - **Never write code directly in `/wf` or `/wf-max` mode.** CEO orchestrates only: dispatch subagents, review results, synthesize, decide next wave. Subagents write code; CEO does not touch files.
75
- - Exception: only when all subagents have failed, or the task is trivially flat (single file, <20 lines). Otherwise delegate everything.
76
- - Why: CEO context is the bottleneck. Every direct edit bloats context and degrades orchestration quality.
73
+ - Never call `EnterPlanMode` — delegate planning to `planner` subagents (see `Harness/WF.md`).
74
+ - Never write code directly in `/wf` or `/wf-max` mode delegate all implementation to subagents (see `Harness/WF-MAX.md`).