agentleFS
JipletJiplet/transformation-os/skills/pipeline/route-task/SKILL.md

route-task

Skill2 starsChanged 4 months agoMITView on GitHub

Route an incoming transformation-programme task to the right thinker lens (CSO/CFO/CAO/CIO/CPO/etc.) and skill. Use at the start of any task that involves analysis, decision-making, exec output, or skill selection, especially when the task signal is ambiguous (cost lever, data question, contract, headcount, working capital, savings phasing, client approval, ops feasibility, risk, steerco, one-pager).

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When Jacob provides a task, classify it and route to the right thinker lens + skill.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Task Routing — Thinker Lenses + Output Skills

When Jacob provides a task, classify it and route to the right thinker lens + skill. Thinkers CHALLENGE and SHAPE — they don't produce outputs. Skills produce outputs.

SignalLoad thinker(s) — Read the fileRoute to skill
Initiative sizing, prioritisation, "should we do this"context/cso.mdprogram-tracker, scenario-model
Data analysis, methodology, "is this right"context/cao.md + context/data-landscape.mdcategory-review, sql-review, data-request
Systems feasibility, SAP ECC / S4HANA, Databricks, Novus, VMP, master data, integration, IT dependency, automation feasibility, reporting capability gap, "can we system-enforce this"context/cio.md + context/data-landscape.mdsql-review, data-request, scenario-model
Cost modelling, pricing, inflation, market ratescontext/chief-economist.mdscenario-model, commercial-insight
Category strategy, vendor, panel, consolidationcontext/cpo.md + context/coo.mdcategory-review, commercial-insight
Headcount, leave, restructure, EA, labour costcontext/chief-people-officer.md + context/general-counsel.mdleave-liability-telco, scenario-model
Working capital, payment terms, DPO, DSO, cash flowcontext/cfo.mdscenario-model, commercial-insight
Savings recognition, P&L vs balance sheet, phasingcontext/cfo.mdprogram-tracker, exec-summary
Contract terms, EA clauses, procurement policy, legal feasibilitycontext/general-counsel.md + context/cro.mdcommercial-insight
Client approval / notification, head contract, SLA/KPI impact, contract reopen, price review, account team, named client (a telco client, a state-government facilities client, Defence, a national network client, state transport), IGET / indigenous / local content, client-specified vendorcontext/chief-client-officer.md + context/general-counsel.mdcommercial-insight, category-review
Operational feasibility, site adoption, change management, mobilisationcontext/coo.md + context/delivery-difficulties.mdepic-builder, scenario-model
Risk, insurance, WHS, vendor lock-in, regulatorycontext/cro.md + context/general-counsel.mdscenario-model, commercial-insight
Competitor, tender, contract award, market news—market-intel
Steerco, ExCo update, program statuscontext/cso.md + context/cfo.mdsteerco-pack, program-tracker
One-pager, CFO summary, exec briefcontext/cfo.mdexec-summary
Smartsheet data, team plan, task tracking—smartsheet
Web page, frontend, UI design, HTML artifactcontext/cdo.mdweb-frontend-design, impeccable/*, taste-skill/*, huashu-design, emil-design-eng (precedence rules in frontend-precedence skill)
Slide deck, presentation pipeline—See context/pipeline.md
New project setup / group spend analysis—See context/triggers.md

Rule: When a thinker column is specified, Read the file before responding. Don't rely on memory of its content. Multi-signal tasks load multiple thinkers — don't pick just one. When in doubt between CIO and CAO: CAO challenges "is this analysis right"; CIO challenges "can the system / data actually deliver this." When in doubt between Chief Client and CRO/GC: CRO/GC cover legal enforceability; Chief Client covers relationship reaction and client-side approval path.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.