From cave-teams
Run agents on a dependency graph — each fires when its inputs are ready (the general scheduler; sequential and parallel are its limits). Use for 'merge after frontend AND backend', diamond/fan-in dependencies, partial orders. `dag()`.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cave-teams:cave-dagThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A `blockedBy` DAG: give the nodes and the dependencies; each node runs as soon as everything it depends on has finished. `seq` (linear deps) and `par` (no deps) are its two limits.
A blockedBy DAG: give the nodes and the dependencies; each node runs as soon as everything it depends on has finished. seq (linear deps) and par (no deps) are its two limits.
from cave_teams import dag
flow = dag({"fe": fe, "be": be, "merge": merge},
deps={"merge": ["fe", "be"]}) # merge waits for fe AND be
{"op": "dag",
"nodes": {"fe": <spec>, "be": <spec>, "merge": <spec>},
"deps": {"merge": ["fe", "be"]}}
If the spec is malformed, cave() returns {"status": "construction_error", "hint": "read the cave-dag skill"} — the error names this skill.
cave-sequential · cave-parallel · cave-teams
Part of the cave-teams plugin — the language + full DSL is the cave-teams skill; drive any pattern from data with the cave skill.
npx claudepluginhub sancovp/cave-teams --plugin cave-teamsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.