agentleFS
Sign inStart free
joinwell52-AIjoinwell52-AI/CodeFlowMu-open/skills/tm-delivery-governance/SKILL.md

tm-delivery-governance

Skill2 starsChanged 4 months agoMITView on GitHub

Coordinate technical delivery across CodeFlowMu roles without taking ADMIN authority. Use when a technical manager needs to split workstreams, sequence dependencies, define handoff points, track technical risks, or coordinate DEV/QA/OPS/PM/EVAL delivery.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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 this skill when technical work spans multiple roles or requires delivery sequencing.

    line 10
  2. Distinctive:

    Keep coordination separate from approval.

    line 16
  3. Distinctive:

    Do not archive, delete, or move lifecycle.

    line 25
  4. Distinctive:

    Do not submit public GitHub issues.

    line 26
  5. Distinctive:

    Do not assign unrelated file scope.

    line 27
  6. Distinctive:

    Do not change PM runtime skills.

    line 28
  7. Distinctive:

    Do not modify formal FCoP protocol.

    line 29

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

Technical Manager Delivery Governance

When to use

Use this skill when technical work spans multiple roles or requires delivery sequencing.

Rules

  • Define workstreams, owner, file scope, dependency, and acceptance.
  • Identify handoff points for TASK, REPORT, QA, PM, and ADMIN.
  • Keep coordination separate from approval.
  • Escalate governance decisions to PM or ADMIN.

Required output

Use docs/skills/technical-manager-playbook/delivery-governance.md.

Forbidden actions

  • Do not archive, delete, or move lifecycle.
  • Do not submit public GitHub issues.
  • Do not assign unrelated file scope.
  • Do not change PM runtime skills.
  • Do not modify formal FCoP protocol.

Minimal example

Workstream: docs skill catalog
Owner: DEV
Dependency: PM review
Acceptance: manifest parses, skill validation passes

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.

Check your setup, free