agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/delivery-model-selector/SKILL.md

delivery-model-selector

Skill1 starsChanged 24 days agoMITView on GitHub

Selects an engagement delivery model when format, participation and staffing choices affect success.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Use during solution design when choosing among advisory, project, workshop, sprint or retained support formats.

    line 9
  2. Distinctive:

    Create feasible delivery options with cadence, staffing and client participation.

    line 19
  3. Distinctive:

    Test each option against dependencies, risks and stakeholder availability.

    line 21

≈ “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

Delivery Model Selector

When to use it

Use during solution design when choosing among advisory, project, workshop, sprint or retained support formats.

What Claude needs

  • client-context.md for business background
  • Outcomes, scope and workplan
  • Stakeholder availability and capability
  • Timing, access, risk and budget constraints

Method

  1. Define decision criteria covering speed, uncertainty, collaboration, capability transfer and governance load.
  2. Create feasible delivery options with cadence, staffing and client participation.
  3. Compare options in a weighted decision matrix.
  4. Test each option against dependencies, risks and stakeholder availability.
  5. Select a preferred model and state the conditions that support it.
  6. Design a fallback if a critical assumption fails.

Output format

Provide an options table with model, cadence, roles, strengths, trade-offs and conditions, followed by recommendation and fallback.

Quality checks

  • Compares at least two genuinely feasible options
  • Reflects client workload in each option
  • Makes selection criteria and assumptions explicit

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.