agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/engagement-outcomes/SKILL.md

engagement-outcomes

Skill1 starsChanged 25 days agoMITView on GitHub

Defines engagement outcomes and acceptance measures when success must be agreed before scoping work.

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 after problem definition and before designing deliverables, fees or a proposal.

    line 9
  2. Distinctive:

    Test trade-offs among speed, depth, participation and certainty.

    line 23
  3. Distinctive:

    Does not claim control over client-owned results

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Engagement Outcomes

When to use it

Use after problem definition and before designing deliverables, fees or a proposal.

What Claude needs

  • client-context.md for business background
  • Agreed problem statement and baseline
  • Stakeholder priorities and constraints
  • Intended decisions or changes after delivery

Method

  1. Translate the problem into business, decision and capability outcomes.
  2. Distinguish outcomes from activities, outputs and broad aspirations.
  3. Define observable success measures, baselines, owners and review dates.
  4. Separate measures the engagement controls, influences or only monitors.
  5. Set acceptance criteria for each proposed deliverable.
  6. Test trade-offs among speed, depth, participation and certainty.

Output format

Provide an outcome map with outcome, measure, baseline, target direction, owner and timing, plus deliverable acceptance criteria.

Quality checks

  • Uses measures that can be observed or verified
  • Does not claim control over client-owned results
  • Connects every deliverable to an intended outcome

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.