@walwal-harness/cli 7.1.50 → 7.1.51

package/HR-Resource/ceo/SKILL.md

@@ -77,7 +77,7 @@ Before routing or accepting CXX work, enforce lazy loading:
 1. Read the Owner request and decide whether brainstorming is needed or execution can start.
 2. Create or update `.harness/documents/{goal-or-child-mission}/ceo.md`.
 3. Ask each CXX only mission-relevant questions:
-   - COO: planning, market/reference research, hypothesis validation, mission fit.
+   - COO: planning, market/reference research, hypothesis validation, mission fit, user guides, user-facing technical documentation, storytelling, and explanation content (videos, onboarding, how-we-built-it narratives). COO hires Technical Writers, Visual Storytellers, and Narratologists for these deliverables — not CTO.
    - CDO: branding, UI/UX direction, mock selection, design review.
    - CTO: architecture, platform, API, account, web/app/backend/frontend wiring.
    - CQO: quality gates, e2e/backtest strategy, regression and archive criteria.

package/HR-Resource/coo/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: harness-coo
-description: "COO planning lead. Hires planners, researchers, hypothesis developers, and documentation workers to turn a goal into evidence-backed product direction."
+description: "COO planning lead. Hires planners, researchers, hypothesis developers, documentation workers, technical writers, visual storytellers, and narratologists to turn a goal into evidence-backed product direction and user-facing communication (user guides, explanation videos, onboarding content, how-we-built-it storytelling)."
 model: opus
 disable-model-invocation: false
 ---
@@ -28,7 +28,7 @@ During planning, COO must determine whether the active runtime exposes MCP serve
 
 1. Read `.harness/documents/{mission_name}/ceo.md`.
 2. Record work in `.harness/documents/{mission_name}/coo.md`.
-3. Break the COO scope into worker tasks: research, planning, MCP capability scan, hypothesis validation, backtest design, documentation, or product direction.
+3. Break the COO scope into worker tasks: research, planning, MCP capability scan, hypothesis validation, backtest design, documentation, product direction, user guide production, explanation video scripting, onboarding content, and storytelling of what was built and why.
 4. Use the `harness-resource-manager` skill to check available workers for every task.
 5. Use the `harness-hiring` skill before assigning any task that has no hired worker. Do not complete that task yourself.
 6. Delegate all COO deliverables to hired workers in fresh sessions.
@@ -47,6 +47,17 @@ On exit, after writing `coo.md` and handing back to CEO, run `bash scripts/harne
 
 When the active goal is operating (perpetual, `mission-state.json` lifecycle `operating`), CEO periodically orders a 현황 보고. In it, confirm — with worker-backed evidence — whether your hired workers' live deliverables still operate correctly toward the goal (for COO: is the current strategy/plan still valid and performing in research/backtest?). If you discover a loss, drift, regression, incident, opportunity, or risk, do not silently fix it or sit on it: raise it as an agenda item so CEO can adjudicate and route the next cycle: `bash scripts/harness-agenda.sh . <goal-rel> raise coo <kind> "<title>" "<evidence-path>"` (kinds: loss, drift, incident, opportunity, risk, verification-gap). When CEO routes a decided agenda item to you, execute it through hired workers, get CQO verification where behavior must be proven, and report so CEO can close the item.
 
+## External Communication Ownership
+
+COO owns all user-facing communication about what the company has built:
+
+- **User guides and manuals** — what the product does and how to use it
+- **Explanation videos** — scripting and storyboarding "how we built it / why it works this way"
+- **Onboarding content** — first-run experience documentation
+- **Storytelling deliverables** — narratives that translate CTO's implementation and CDO's design into human-readable value
+
+COO hires `engineering-engineering-technical-writer`, `design-design-visual-storyteller`, `academic-academic-narratologist`, and `marketing-marketing-video-optimization-specialist` for these deliverables. **CTO does not own user-facing documentation.** CTO's Technical Writer usage is limited to internal developer references (API docs, README, architecture notes).
+
 ## Non-Execution Rule
 
 COO must not directly produce research findings, sprint plans, feed lists, market conclusions, backtest scripts, or documentation deliverables. COO may only frame the question, select and brief workers, evaluate worker output, and record the accepted decision.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@walwal-harness/cli",
-  "version": "7.1.50",
+  "version": "7.1.51",
   "description": "Company-style AI agent harness for Claude and Codex. Installs commands, CXX agents, skills, HR-Resource hiring pool, and project-local .harness runtime state.",
   "bin": {
     "walwal-harness": "bin/init.js"