OperationsCouncil

Solo-operator operability review. Can one person actually run, maintain, and recover this system after launch?

The Operations Council is a Claude Code skill that evaluates whether a project, system, website, workflow, or service can be operated and maintained by a solo founder without hidden complexity. Four roles — Operator, Support Desk, Process Auditor, Foreman — produce a single verdict: OPERABLE / FIX FIRST / NOT OPERABLE in under 1,200 tokens.

Operations only. Does not duplicate Tech, Marketing, Sales, Forge, TrueCouncilOf12, or TrueBusinessCouncil.

Install

1. Claude Code plugin marketplace

/plugin marketplace add ojesusmp/OperationsCouncil
/plugin install operations-council@operations-council

Verify: ~/.claude/skills/operations-council/SKILL.md exists and starts with ---\nname: operations-council.

2. Git clone (manual)

git clone https://github.com/ojesusmp/OperationsCouncil.git

Git does not run install scripts — this step is manual:

POSIX:

mkdir -p ~/.claude/skills/operations-council
cp OperationsCouncil/SKILL.md ~/.claude/skills/operations-council/SKILL.md

Windows PowerShell:

New-Item -ItemType Directory -Force "$env:USERPROFILE\.claude\skills\operations-council" | Out-Null
Copy-Item "OperationsCouncil\SKILL.md" "$env:USERPROFILE\.claude\skills\operations-council\SKILL.md"

Verify: sha256sum ~/.claude/skills/operations-council/SKILL.md matches the source.

3. npm

npm install -g @ojesusmp/operations-council

Windows + Node 24 + npm 11 may print MODULE_NOT_FOUND and exit 1 even though the postinstall copy succeeded. Verify with the printed SHA-256 or use npm pack + local tarball for a clean exit.

Verify: install.cjs prints copied ... (sha256=...) confirming the file landed at ~/.claude/skills/operations-council/SKILL.md.

Usage

operations-council Evaluate <system> for solo-operator operability.

Council runs four roles — Operator → Support Desk → Process Auditor → Foreman — and emits a 10-section report with a single verdict: OPERABLE / FIX FIRST / NOT OPERABLE.

See SKILL.md for the full protocol.

The 4 Roles

| Role | Owns | |------|------| | Operator | Day-to-day burden, credentials, single-points-of-failure, sustainability for 90 days | | Support Desk | Top failure modes, manual fallback, first-response template, recovery time | | Process Auditor | Setup runbook, secret rotation, restore-from-scratch, hidden dependencies | | Foreman | Verdict + minimum fix list (≤7 items, each ≤1 day operator time) |

The 10 mandatory output sections

1. Substrate echo
2. Operator burden
3. Setup burden
4. Daily/weekly maintenance
5. Failure handling
6. Manual fallback
7. Documentation gaps
8. Hidden dependencies
9. Minimum fix list
10. Verdict

Verdict ∈ {OPERABLE, FIX FIRST, NOT OPERABLE}. Missing facts default to FIX FIRST, never silently to OPERABLE.

Hard boundaries

• No new councils proposed inside output.
• No product code, copy, feature suggestions.
• No technical redesign (unless required to make operable, and then only as a fix-list item).
• No business strategy, marketing, sales, or ideation.
• No motivational language.

Siblings (do not duplicate)

• TechCouncil — architecture and engineering tradeoffs
• MarketingCouncil — positioning, copy, offers
• SalesCouncil — close, advance, objections
• forge-council — creative ideation
• TrueCouncilOf12 — 12-lens stakeholder analysis
• TrueBusinessCouncil — business model

OperationsCouncil owns operations only.

Credits

Built and maintained by Orlando Molina under TruePointAgents.

License

Released under the MIT License.