agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/map-dependencies/SKILL.md

map-dependencies

Skill0 starsChanged 16 days agoMITView on GitHub

Map team × system × date dependencies from process, contracts, and RAID. Use when the user asks for a dependency map, cross-team dependencies, or /map-dependencies. Do not invent dates or teams.

2 other projects use a version of this.

Adopted by

Most recently taken up by

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:

    Do not invent dates or teams.

    line 18
  2. Distinctive:

    If none of those exist, stop.

    line 33
  3. Distinctive:

    Read AGENTS.md if present.

    line 41

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

Map dependencies

One picture of who waits on whom. This is not RAID (update-raid still holds status) and not architecture.

Do not invent dates or teams.

Is this the right skill?

SignalDo this instead
Payload between systemswrite-integration-contract
Process stepsmap-process
Open risk/issue rowsupdate-raid

Required inputs

  • At least one of: process map, contracts, RAID dependencies
  • context/systems-of-record.md if it exists

If none of those exist, stop.

Human decisions (do not invent)

  • Needed-by dates that are not already on RAID or a plan

Procedure

  1. Read AGENTS.md if present. Read process map, contracts, RAID, systems-of-record.
  2. Find the home: docs/govern/dependencies.md (one file, update in place).
  3. Open references/dependencies-template.md. Copy every heading. Write n/a when unused.
  4. Each edge: from team/system, to team/system, what (contract or RAID id), needed-by (sourced or unknown).
  5. Flag missing contracts as gap.

Output

  • Path: docs/govern/dependencies.md
  • Template: references/dependencies-template.md

Quality bar

  • Every edge cites process, contract, or RAID
  • Dates are sourced or unknown
  • Systems match systems-of-record or are marked not in systems-of-record
  • Unused headings are n/a

Done

  1. Path
  2. Edge count + gap count
  3. Next skill: write-integration-contract for gaps; update-raid for dates

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