agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/governance-designer/SKILL.md

governance-designer

Skill1 starsChanged 25 days agoMITView on GitHub

Designs engagement governance when decision rights, cadence, escalation and controls need definition.

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 at mobilisation or when an active engagement suffers slow decisions or unclear accountability.

    line 9
  2. Distinctive:

    Create status, risk, issue, decision and change-control registers.

    line 21
  3. Distinctive:

    Test governance load against engagement scale and simplify duplication.

    line 23

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

Governance Designer

When to use it

Use at mobilisation or when an active engagement suffers slow decisions or unclear accountability.

What Claude needs

  • client-context.md for business background
  • Statement of work, workplan and stakeholder map
  • Decision types and named role holders
  • Reporting, risk and escalation expectations

Method

  1. List recurring and milestone decisions required for delivery.
  2. Assign propose, input, decide and execute rights for each decision type.
  3. Design meeting cadence, purpose, attendees, inputs and outputs.
  4. Create status, risk, issue, decision and change-control registers.
  5. Define escalation thresholds, route, response time and resolution owner.
  6. Test governance load against engagement scale and simplify duplication.

Output format

Provide a governance map, decision-rights table, meeting calendar, register definitions and escalation path.

Quality checks

  • Gives every material decision one clear decider
  • Separates risks, issues, decisions and changes
  • Keeps governance proportionate to engagement complexity

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.