create-harness-vibe-coding 0.4.0 → 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.0",
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": {
@@ -67,3 +67,8 @@ Root entry for Claude Code. Keep this file short.
67
67
  - **Context threshold trigger**: when context approaches ~85% of the window, dispatch `context-master` to analyze and write a non-blocking compression suggestion to `Harness/tasks/<task-id>/PROGRESS.md#Heartbeat`.
68
68
  - **Closeout trigger**: during WF closeout, dispatch `context-master` to extract durable knowledge, then `memory-master` to consolidate into `Harness/memory/*`.
69
69
  - Never record secrets, credentials, tokens, or private data.
70
+
71
+ ## 7. CEO Constraints
72
+
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`).
@@ -21,7 +21,7 @@ CEO(1) ──┬── Manager₁(span) ──┬── Worker₁..ₙ
21
21
  └── Manager₂(span) ── Worker₁..ₙ
22
22
  ```
23
23
 
24
- - CEO: intent, scope, integration, final verification. Direct reports 3-5 Managers.
24
+ - 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.
25
25
  - Manager: domain partition → parallel dispatch → synthesize → report. Serial across domains; parallel within domain.
26
26
  - 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.
27
27
  - depth ≥3: Manager spawns Sub-Manager (span ≤7) instead of Worker. Recursive until leaf condition met.