AI Agent Skill HUB

gsd-analyze-dependencies

Analyze phase dependencies and suggest Depends on entries for ROADMAP.md

26 stars
byZaneL1u
View on GitHubInstallation ↓

Best use case

gsd-analyze-dependencies is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Analyze phase dependencies and suggest Depends on entries for ROADMAP.md

Teams using gsd-analyze-dependencies should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/gsd-analyze-dependencies/SKILL.md --create-dirs "https://raw.githubusercontent.com/ZaneL1u/cloud-cli-proxy/main/.cursor/skills/gsd-analyze-dependencies/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/gsd-analyze-dependencies/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How gsd-analyze-dependencies Compares

Feature / Agentgsd-analyze-dependenciesStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Analyze phase dependencies and suggest Depends on entries for ROADMAP.md

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

<cursor_skill_adapter>
## A. Skill Invocation
- This skill is invoked when the user mentions `gsd-analyze-dependencies` or describes a task matching this skill.
- Treat all user text after the skill mention as `{{GSD_ARGS}}`.
- If no arguments are present, treat `{{GSD_ARGS}}` as empty.

## B. User Prompting
When the workflow needs user input, prompt the user conversationally:
- Present options as a numbered list in your response text
- Ask the user to reply with their choice
- For multi-select, ask for comma-separated numbers

## C. Tool Usage
Use these Cursor tools when executing GSD workflows:
- `Shell` for running commands (terminal operations)
- `StrReplace` for editing existing files
- `Read`, `Write`, `Glob`, `Grep`, `Task`, `WebSearch`, `WebFetch`, `TodoWrite` as needed

## D. Subagent Spawning
When the workflow needs to spawn a subagent:
- Use `Task(subagent_type="generalPurpose", ...)`
- The `model` parameter maps to Cursor's model options (e.g., "fast")
</cursor_skill_adapter>

<objective>
Analyze the phase dependency graph for the current milestone. For each phase pair, determine if there is a dependency relationship based on:
- File overlap (phases that modify the same files must be ordered)
- Semantic dependencies (a phase that uses an API built by another phase)
- Data flow (a phase that consumes output from another phase)

Then suggest `Depends on` updates to ROADMAP.md.
</objective>

<execution_context>
@/Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/workflows/analyze-dependencies.md
</execution_context>

<context>
No arguments required. Requires an active milestone with ROADMAP.md.

Run this command BEFORE `/gsd-manager` to fill in missing `Depends on` fields and prevent merge conflicts from unordered parallel execution.
</context>

<process>
Execute the analyze-dependencies workflow from @/Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/workflows/analyze-dependencies.md end-to-end.
Present dependency suggestions clearly and apply confirmed updates to ROADMAP.md.
</process>

Related Skills

gsd-undo

26
from ZaneL1u/cloud-cli-proxy

Safe git revert. Roll back phase or plan commits using the phase manifest with dependency checks.

gsd-ultraplan-phase

26
from ZaneL1u/cloud-cli-proxy

[BETA] Offload plan phase to Cursor's ultraplan cloud — drafts remotely while terminal stays free, review in browser with inline comments, import back via /gsd-import. Cursor only.

gsd-spike

26
from ZaneL1u/cloud-cli-proxy

Spike an idea through experiential exploration, or propose what to spike next (frontier mode)

gsd-spike-wrap-up

26
from ZaneL1u/cloud-cli-proxy

Package spike findings into a persistent project skill for future build conversations

gsd-spec-phase

26
from ZaneL1u/cloud-cli-proxy

Socratic spec refinement — clarify WHAT a phase delivers with ambiguity scoring before discuss-phase. Produces a SPEC.md with falsifiable requirements locked before implementati...

gsd-sketch

26
from ZaneL1u/cloud-cli-proxy

Sketch UI/design ideas with throwaway HTML mockups, or propose what to sketch next (frontier mode)

gsd-sketch-wrap-up

26
from ZaneL1u/cloud-cli-proxy

Package sketch design findings into a persistent project skill for future build conversations

gsd-secure-phase

26
from ZaneL1u/cloud-cli-proxy

Retroactively verify threat mitigations for a completed phase

gsd-scan

26
from ZaneL1u/cloud-cli-proxy

Rapid codebase assessment — lightweight alternative to /gsd-map-codebase

gsd-join-discord

26
from ZaneL1u/cloud-cli-proxy

Join the GSD Discord community

gsd-ingest-docs

26
from ZaneL1u/cloud-cli-proxy

Scan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context...

gsd-inbox

26
from ZaneL1u/cloud-cli-proxy

Triage and review all open GitHub issues and PRs against project templates and contribution guidelines