# Business Ops Operations Handbook

Build the operations handbook that documents how the company actually runs: operating...

- Repository: https://github.com/FerroxLabs/wayland (616 stars)
- Category: Business
- License: Apache-2.0
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add FerroxLabs/wayland --skill business-ops-operations-handbook -g -a claude-code -y`
Codex: `npx skills add FerroxLabs/wayland --skill business-ops-operations-handbook -g -a codex -y`
Cursor: `npx skills add FerroxLabs/wayland --skill business-ops-operations-handbook -g -a cursor -y`
Gemini CLI: `npx skills add FerroxLabs/wayland --skill business-ops-operations-handbook -g -a gemini-cli -y`

## Description

Build the operations handbook that documents how the company actually runs: operating cadences, decision rights, escalation paths, and the remaining operational sections. This is the operations handbook, distinct from an HR handbook. Use when the user wants a structured, multi-step build of a company operations handbook covering cadences, decision rights, and escalation. Do NOT use for an HR or employee policy handbook, or for a single section that one atomic skill can draft on its own.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Build the Operations Handbook

**Estimated time:** 60-90 minutes

This workflow builds the operations handbook: how the company runs day to day,
who decides what, and how problems escalate. It is the operations handbook, not
the HR handbook. The build proceeds through operating cadences, the decision
rights matrix, escalation paths, and the remaining operational sections, then
assembles them into one document. Review and refine each section before
advancing.

## Steps

**Step 1: Capture the Company Brief**

Open by telling the user you will build the operations handbook (how the company
runs day to day, distinct from an HR handbook), then ask them for: company stage,
headcount, key functions, and any existing operating cadence such as weekly
reviews or monthly business reviews. Ask these as a single grouped question and
wait for the answer. Record the response verbatim as the brief.

- Input: user description of stage, headcount, functions, existing cadences
- Output: a captured company brief
- Key focus: anchor every later section in the company's actual stage and size

**Step 2: Infer the Required Sections** (uses: ops-handbook)

From the brief, infer which handbook sections this company needs at its current
stage. List the inferred sections and give a one-paragraph reasoning. Surface the
inference to the user so they can add or remove sections before you build them.

- Input: company brief from Step 1
- Output: the list of required handbook sections with reasoning
- Key focus: right-size the handbook to the stage, no premature bureaucracy

**Step 3: Build the Operating Cadences** (uses: ops-handbook)

Build the operating cadences: the weeklies, monthlies, and quarterlies, each with
its purpose, owner, attendees, and inputs and outputs. Show the cadences to the
user and ask whether to refine them or proceed to decision rights. If they ask
for changes, revise against their feedback and show them again. Allow up to two
refinement passes.

The rest: https://github.com/FerroxLabs/wayland/blob/HEAD/src/process/resources/bundled-workflows/bodies/business-ops-operations-handbook/SKILL.md