agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/benefits-realisation/SKILL.md

benefits-realisation

Skill1 starsChanged 25 days agoMITView on GitHub

Builds a benefits realisation plan when expected value must be measured, owned and sustained after delivery.

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:

    Use during mobilisation and throughout delivery to keep outputs connected to measurable business outcomes.

    line 9

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

Benefits Realisation Plan

When to use it

Use during mobilisation and throughout delivery to keep outputs connected to measurable business outcomes.

What Claude needs

  • client-context.md and approved investment case
  • Benefit statements, baselines and target outcomes
  • Delivery milestones and operational owners
  • Data sources, assumptions and measurement cadence

Method

  1. Convert broad benefits into specific outcome statements.
  2. Build a benefit dependency map from deliverables to behavioural and business change.
  3. Define baseline, indicator, target direction and measurement method.
  4. Assign a benefit owner with authority to sustain the change.
  5. Schedule reviews at leading and lagging indicator points.
  6. Identify disbenefits, double counting and corrective triggers.

Output format

Provide a benefit map and register with Benefit, Baseline, Indicator, Target Direction, Data Source, Owner, Enablers, Timing and Corrective Trigger.

Quality checks

  • Benefits are outcomes rather than completed deliverables.
  • Measures avoid overlap and have credible data sources.
  • Each benefit has an accountable operational owner.

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.