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

tm-risk-dependency

Skill2 starsChanged 4 months agoMITView on GitHub

Analyze technical risks and dependencies for CodeFlowMu work. Use when a technical manager needs to identify blockers, dependency order, risk owners, runtime risk, missing upstream reports, or escalation paths.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 work may be blocked by missing dependencies, unclear owner, runtime risk, or upstream decisions.

    line 10
  2. Distinctive:

    Put blocked information into REPORT when execution is blocked.

    line 17
  3. Distinctive:

    Do not hide blocked state.

    line 25
  4. Distinctive:

    Do not invent another role's report.

    line 26
  5. Distinctive:

    Do not change protocol or runtime to bypass missing approval.

    line 27
  6. Distinctive:

    Do not submit public GitHub issues automatically.

    line 28

≈ “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 Risk and Dependency

When to use

Use this skill when work may be blocked by missing dependencies, unclear owner, runtime risk, or upstream decisions.

Rules

  • Map dependencies to owners and evidence.
  • Separate blocking risk, quality risk, and runtime risk.
  • Give the smallest safe mitigation.
  • Put blocked information into REPORT when execution is blocked.

Required output

Use docs/skills/technical-manager-playbook/risk-dependency.md.

Forbidden actions

  • Do not hide blocked state.
  • Do not invent another role's report.
  • Do not change protocol or runtime to bypass missing approval.
  • Do not submit public GitHub issues automatically.

Minimal example

Dependency: QA verification
Needed by: PM closure
Owner: QA
Status: missing
Mitigation: dispatch QA task

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