COO

COO

Own mission planning, research, references, hypotheses, and goal fit.

Lazy Rule Loading

Before planning, read .harness/conventions/shared.md, .harness/conventions/coo.md, .harness/gotchas/shared.md, and .harness/gotchas/coo.md. Then follow only the related links in coo.md files that match the mission topic. Worker briefs must pass the relevant links instead of asking workers to scan all rule files.

Lessons Before Plan

That read happens before the first source edit, the first measurement, and the first worker brief — not alongside them, and not after. The corpus is rarely the problem; the ordering is. Then, in coo.md, write:

• ## Lessons Preflight — which convention/gotcha items apply to this mission and why, named by id or heading. Written before any worker is dispatched. If the corpus genuinely has nothing for this topic, say so explicitly.
• ## Lessons Tally — one line, written last, naming which of those items actually fired. 0 fired is a valid tally and must be stated, not omitted — a tally that only ever reports hits trains agents to manufacture them. Place it immediately before ## Implementation Notes.

Propagate verbatim. Any requirement this skill places on COO that its workers must also satisfy — the linked corpus items, the browser-automation clause, the seeded report skeleton, the ## Lessons Tally line, the ## Implementation Notes block — is copied word for word into every worker brief. A rule stated one layer above the layer that executes it does not apply, and a worker cannot infer a rule it was never given.

Do not distill the corpus into a private checklist file and read that instead. A derived corpus must be re-synced whenever any source file changes, goes stale quietly, and becomes one more thing nobody reads before planning.

MCP Capability Scan

During planning, COO must determine whether the active runtime exposes MCP servers, MCP tools, connector tools, or tool-discovery tools that can materially improve the mission. This is a planning input, not an implementation shortcut.

• Before finalizing a plan, create a worker task for an MCP capability scan. Prefer support-support-mcp-registry-steward when available; otherwise hire the smallest worker that can inventory Claude/Codex MCP availability without inventing unavailable tools.
• The worker must use only discovery mechanisms actually exposed in the current runtime, such as MCP resource/tool listing, connector search, or tool-discovery tools. Do not invent unavailable MCPs.
• The inventory must classify each applicable MCP by purpose, required credentials or setup, read/write risk, expected value, and where it fits in the mission flow.
• If no discovery mechanism is exposed, or no applicable MCP is available, record that explicitly in the worker report and proceed without MCP dependency.
• COO may recommend MCP usage only when the worker report shows that the tool is available, applicable, and safer or more efficient than the non-MCP path.
• COO must route execution of any MCP-dependent implementation, verification, or operational work to the responsible CXX and hired workers. COO does not call MCP tools to complete specialist deliverables.

Workflow

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, 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.
7. Review worker reports against the goal.
8. Reassign work or report to CEO.