agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/de-anthropocentric-research-engine/skills/map-dependencies/SKILL.md

map-dependencies

Skill505 starsChanged 49 days agoApache-2.0View on GitHub

Construct a dependency graph and identify cycles, critical paths, and parallelizable branches.

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

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If dependency types and blocking relations are explicit, consider sequence-work as the next tactic.

    line 27
  2. Distinctive:

    Every edge has direction, strength, and evidence.

    line 39

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

Purpose

Construct a dependency graph and identify cycles, critical paths, and parallelizable branches.

Input contract

required: [items, dependency_evidence, relation_schema]
optional: [criticality_rule, execution_context, candidate_order]
constraints: [the graph contains at least 2 items when the source protocol applies; dependency direction and strength are explicit]

Procedure

  1. Normalize item identifiers and proposed dependency relations.
  2. Classify each edge as strong or weak with evidence.
  3. Detect cycles, compute critical paths, and identify independent branches.
  4. Return the dependency graph and unresolved relation questions.

If dependency types and blocking relations are explicit, consider sequence-work as the next tactic.

Output contract

produces: [dependency_graph, cycle_register, critical_paths, independent_branches]
delta_fields: [findings, evidence_updates, uncertainties, open_questions]

Quality gates

  • At least 2 subproblems are represented where the source protocol applies.
  • Every edge has direction, strength, and evidence; cycles are reported rather than silently linearized.
  • Parallel branches are descriptive graph properties, not execution instructions.

Parameterization

The caller must provide item/subproblem schema, edge vocabulary, strength scale, evidence links, critical-path rule, and the scope in which parallel independence is assessed.

Failure and counterexamples

Reject self-justifying edges, cycles hidden by reordering, or "parallel" labels where shared prerequisites remain.

Provenance map

  • resolved: hypothesis-formation/dependency-mapping
  • resolved: creative-ideation/dependency-identification

Preserved source criteria ledger

sourcephysical linekindsource criterion
hypothesis-formation/dependency-mapping12numericRequires >=2 subproblems; labels strong/weak dependencies, detects cycles, identifies critical path and parallel opportunities.

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