Founder Ops

Revenue-weighted prioritisation for solo founders. Tells you what to work on, then produces the deliverable inline — no plans, no fluff, just the next action that makes money.

Install
cmdop skills install agensi-founder-ops

Founder Ops is a skill aimed at solo founders managing multiple projects who face decision fatigue and context-switching overhead. Rather than producing a plan and asking for confirmation, it evaluates every candidate action using Revenue Proximity Scoring on a 1–5 scale, selects the highest-leverage move, and generates the actual deliverable — an email draft, marketing copy, code snippet, or configuration — within the same response.

The skill incorporates effort banding, which groups tasks by the work required, and opportunity evaluation to weigh actions against each other. An anti-busywork enforcement layer filters out low-value activity that feels productive but does not move revenue forward. The design explicitly accounts for neurodiversity and executive function challenges, aiming to reduce the cognitive load of deciding what to do next.

There are no tool calls listed for this skill, meaning its value is delivered through its reasoning and generation behavior rather than through discrete callable functions. It does not connect to external databases, APIs, or project management systems on its own. The skill is published by agensi. No package registry, version, license, or repository information is available in the current record.

Use cases

  • Prioritise a backlog of founder tasks by how directly each one generates revenue
  • Generate a cold outreach email as the immediate output of a prioritisation session
  • Produce a landing-page copy draft without a separate follow-up prompt
  • Identify and suppress low-value busywork from a weekly task list
  • Band pending tasks by effort level to match available energy or time
  • Evaluate a new opportunity against existing work using inline scoring

When to use it

  • Solo founders juggling several simultaneous ventures who need a single next action, not a project plan
  • When the desired output is a finished deliverable rather than advice on how to create one
  • When decision fatigue makes it hard to choose between competing tasks
  • When the user needs a workflow that accounts for executive function or neurodiversity considerations

When not to use it

  • Teams or organisations that need multi-user task assignment or project tracking integrations
  • Situations requiring connection to external tools, calendars, or databases — no such integrations are provided
  • When a structured project management system with persistent state is required
  • When the deliverable type needed falls outside text, copy, code, or config generation