Skip to main content

dependencies

Show dependency graph and active blockers for a project or sprint Arguments: <project> [--cycle <current|next|name>].

Source facts

Repository
Agents-Store/codex-plugins
Last source activity
November 1, 2026 at 02:46
Detected SKILL.md language
English
Stars
0
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
dependencies
description
Show dependency graph and active blockers for a project or sprint Arguments: <project> [--cycle <current|next|name>].
# Dependencies Inspect work item relations to find active blockers, blocking chains, and risk items. Method and rules: the `plane-ops:work-items` skill. ## Arguments Format: `<project> [--cycle <current|next|name>] [--item <id>]` Parse from `"$ARGUMENTS"`. Without `--cycle` or `--item`, scan the whole active backlog. ## Process 1. **Bootstrap connector** — consult `connector-bootstrap`. Probe for the Plane resource tools `project`, `cycle`, `workitem` and `workitem_relation`. 2. **Resolve project** — `project(action=list)` → `project_id`. 3. **Scope the scan**: - `--cycle current` → items in the active cycle (`cycle(action=list, project_id, status=current)`, then `cycle(action=list_workitems, project_id, cycle_id, pql='stateGroup IN openStates()')`) - `--cycle <name>` → items in that cycle - `--item <id>` → just that item and its transitive relations - default → in-progress + unstarted items in the project: `workitem(action=list, project_id, pql='stateGroup IN ("unstarted","started")')` 4. **For each item, fetch relations** — `workitem_relation(action=list, project_id, workitem_id)`. Shortcut for one item: PQL `blocks("PROJ-148")` returns the items that block PROJ-148, `blockedBy("PROJ-148")` the items blocked by it (direction per the `get_pql_reference` wording — confirm on your instance; `workitem_relation(action=list)` is the authoritative answer). 5. **Build the graph** — direction matters: `blocked_by` (incoming), `blocking` (outgoing), plus any duplicate / relates-to / custom relation (`workitem_relation(action=list_definitions)` names them). 6. **Highlight risk**: - Items blocked by something not yet started - Items blocking 2+ other items (critical path candidates) - Cyclic dependencies (report explicitly) 7. **Present** as a table grouped by risk level (🔴 blocker chain, 🟡 single blocker, 🟢 no blockers). ## Example ``` /dependencies "TaskFlow" /dependencies "TaskFlow" --cycle current /dependencies "TaskFlow" --item PROJ-148 ``` ## Output Format ``` 🔴 Blocker chains PROJ-148 (Stripe webhook) ← blocks PROJ-152, PROJ-153, PROJ-160 blocked_by PROJ-140 (backlog, unestimated) 🟡 Single blockers PROJ-155 blocked_by PROJ-147 (in progress, @alice) 🟢 Clear PROJ-150, PROJ-151, … ```
View on GitHub