resonance-ops-founder-os

Runs company OKRs, scorecards, weekly reviews, and agent authority budgets as typed ledger entries.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-founder-os-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resonance-ops-founder-os
Source: https://github.com/manusco/wolfgang/tree/main/.agents/skills/ops/founder-os
Command: npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-founder-os-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Founders running a business with a fleet of AI agents lose track of company state when goals, metrics, and decisions live in scattered prose and chat. This Skill turns the company into a system: OKRs, KPI scorecards, weekly reviews, decisions, and agent authority limits all live as typed, citable entries in a ledger instead of the founder's memory. ## Core Features & Use Cases - OKR Cascade and KPI Tree: Set one or two company objectives with numeric key results recorded as met- or exp- ledger entries, decomposed from a single north-star into leading and lagging drivers. - Weekly Business Review and Decision Log: Run an inspection-first review that reads the scorecard against targets, drills stuck metrics, and logs every call as a dec- entry that is superseded rather than overwritten. - Authority Budgets and Cadence: Define what each agent may spend, send, commit, or change across three escalation tiers with hard stops on money movement and investor comms, plus a per-function operating cadence spec. - Use Case: A founder asks to run the weekly review with MRR flat for three weeks and a paused paid-search experiment. The Skill flags the stuck metric, checks the leading-to-lagging link, logs decisions as dec- entries, and marks the experiment DONE_PENDING_OUTCOME with a due date instead of declaring victory early. ## Quick Start Ask the agent to run your weekly business review or set next quarter's OKR cascade against the company ledger.

Frequently Asked Questions about resonance-ops-founder-os

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set OKRs that cascade from company to team level?▼

Set one or two qualitative company objectives, then write three to five numeric key results per objective with targets and dates. Each function's key results must visibly sum toward the company target, and each is recorded as a met- or exp- ledger entry rather than kept in a doc.

How do I run a weekly business review with AI agents?▼

Start from the scorecard read against targets, drill every off-track or stalled metric, and end with decisions logged as dec- entries with one owner each. Work whose proof lands later ends DONE_PENDING_OUTCOME with a due date instead of being declared successful in the room.

What actions should an AI agent never do without founder approval?▼

Hard stops include money movement out of the company, investor and board communication, press or public statements, signed agreements, and production or security changes. A skill may prepare and recommend these actions, but the founder must always authorize them.

Why is setting a target I already hit considered a problem?▼

A target at or below a level already reached is sandbagging: a status report written in advance, not a goal. Healthy stretch key results land near 70 percent in a good quarter, and hitting 100 percent every time signals the bar was set too low.

Does this Skill schedule recurring reviews automatically?▼

No, it is pull-based and runs no daemon. It writes a cadence spec and hands timing to the host's own scheduler, such as cron or Task Scheduler invoking the CLI, while a session-start script surfaces any ledger entries whose due dates have arrived.