agentleFS
Sign inStart free
agoopintsaiagoopintsai/shipright/skills/delegate/SKILL.md

delegate

Skill2 starsChanged 16 days agoApache-2.0View on GitHub

Delegate mode. The main session judges, scouts read and search, executors write and run; saves the expensive model's quota. Use for "/shipright:delegate", "delegate mode", or when about to do large read or write work by hand.

78 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use state, preview and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    state

    Store and query a Microsoft Managed App's built-in state and file attachments with `ms project state` CLI schema commands and generated TypeScript clients. First, with the user signed in to the CLI, run `ms feature status --name state --json`; if `feature.enabled` is not `true`, recommend an alternative connector or data source.

    Also in 3 projects that use this

  • kv0906Skill

    preview

    Render vault notes as styled HTML and open in browser. Turn markdown docs, decisions, progress reports into readable previews. Use for "/preview docs/project-a/checkout-flow.md", "/preview progress all", "/preview decide auth-approach", or when user wants to see a doc before sharing.

    Also in 3 projects that use this

  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 5 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 3 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    skill-authoring

    Write Agent Skills that comply with the agentskills.io specification. WHEN: "create a skill", "new skill", "write a skill", "skill template", "skill structure", "review skill", "skill PR", "skill compliance", "SKILL.md format", "skill frontmatter", "skill best practices". DO NOT USE FOR: general documentation. INVOKES: vally CLI.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run python3 "${CLAUDE_PLUGIN_ROOT}/scripts/shipright_hooks.py" set delegate and relay the one-line output (switch the model menu to your …

    line 8
  2. Distinctive:

    Never spawn without a written brief.

    line 38
  3. Very specific:

    Every agent() in a Workflow must set model ('sonnet' or 'haiku').

    line 40

“Common” is measured: kept by at least 6 in 10 of the 68 edited versions of this file we could read. “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

/shipright:delegate

Run python3 "${CLAUDE_PLUGIN_ROOT}/scripts/shipright_hooks.py" set delegate and relay the one-line output (switch the model menu to your strongest model). End every reply with the marker [delegate].

What the hooks enforce

  1. Edit, Write, NotebookEdit: ask first. Writes belong to an executor.
  2. More than 5 personal lookups (Read, Grep, Glob, Bash, WebFetch, WebSearch) in one turn: denied. Dispatch a scout.
  3. Agent is neither blocked nor counted, but monitored: more than 4 concurrent, more than 8 this turn, or one over 10 minutes raises an alert, and your reply must end with a line Subagent status: ....

Who does what

RoleDoesModel
Judge (this session)Clarify, decompose, decide, review, synthesise, answer the humanthe strong model
shipright:scoutRead files, search code, check docs and the web, read-only commandshaiku
shipright:executorWrite code, edit files, run commands and testssonnet

Trivial work stays inline: a one or two line, single-file change that needs no research, or one short file you must read line by line to decide. A spawn has fixed overhead.

Brief format (every dispatch)

OBJECTIVE: one sentence, what is wanted
SCOPE: exact paths, globs or URLs (executors may touch only these)
CONTEXT: facts you already know, pasted in so the worker does not re-discover them
REPORT: the shape of the answer and a line limit
DON'T: rabbit holes to avoid

Doctrine

  • Never spawn without a written brief. Merge related small queries into one scout.
  • At most 4 workers in parallel; a Workflow's agents count too. Prefer few large briefs.
  • Every agent() in a Workflow must set model ('sonnet' or 'haiku'). Missing is denied by the hook; opus or fable asks first. Say how many and why before using a strong model.
  • Reports are at most 40 lines. Anything longer goes to a scratch file and the report names the path.
  • Trust but spot-check: verify load-bearing claims by pointer (path:line); do not re-read whole files.
  • Retry a failed worker once with a fixed brief, then escalate the model or take over, and say so.
  • Local heavy work (test suites, browsers, containers) runs one worker at a time.
  • Executors never merge and never open PRs unless the brief says so. Review the diff yourself before telling the human it is done.
  • Judgement, design trade-offs and grilling stay in this session; do not delegate them.

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.

Check your setup, free