agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/statement-of-work/SKILL.md

statement-of-work

Skill1 starsChanged 25 days agoMITView on GitHub

Drafts a precise statement of work when approved commercial intent must become operational commitments.

1 other project uses 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:

    Use after proposal alignment and before delivery begins, alongside appropriate legal terms.

    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

Statement of Work

When to use it

Use after proposal alignment and before delivery begins, alongside appropriate legal terms.

What Claude needs

  • client-context.md for business background
  • Approved proposal and negotiated changes
  • Deliverables, acceptance criteria and schedule
  • Fees, dependencies and governing agreement details

Method

  1. Reconcile all approved terms against the latest scope and fee version.
  2. Define services, deliverables, milestones and acceptance procedure precisely.
  3. Allocate supplier and client responsibilities using a RACI.
  4. State assumptions, dependencies, exclusions and access requirements.
  5. Specify fees, invoicing, expenses, change control and termination effects.
  6. Flag legal or ambiguous matters for qualified human review.

Output format

Provide numbered clauses for purpose, scope, deliverables, schedule, responsibilities, acceptance, fees, changes, assumptions and signatures.

Quality checks

  • Uses consistent names, dates and defined terms
  • Contains no commitments absent from the approved offer
  • Flags legal uncertainty instead of inventing language

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.