Product Launch Legal Review
anthropics/claude-for-legal
Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.
Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work.
Install Dependency And Risk Management
$ npx skills add cbrock84/headcount --skill dependency-and-risk-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount dependency-and-risk-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/pmo/skills/dependency-and-risk-management .claude/skills/dependency-and-risk-management && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dependency-and-risk-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/dependency-and-risk-management into .claude/skills/dependency-and-risk-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dependency-and-risk-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/dependency-and-risk-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill dependency-and-risk-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount dependency-and-risk-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/pmo/skills/dependency-and-risk-management .agents/skills/dependency-and-risk-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dependency-and-risk-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/dependency-and-risk-management into .agents/skills/dependency-and-risk-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dependency-and-risk-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill dependency-and-risk-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount dependency-and-risk-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/pmo/skills/dependency-and-risk-management .cursor/skills/dependency-and-risk-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dependency-and-risk-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/dependency-and-risk-management into .cursor/skills/dependency-and-risk-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dependency-and-risk-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/pmo/skills/dependency-and-risk-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill dependency-and-risk-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount dependency-and-risk-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/pmo/skills/dependency-and-risk-management .gemini/skills/dependency-and-risk-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dependency-and-risk-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/dependency-and-risk-management into .gemini/skills/dependency-and-risk-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dependency-and-risk-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount dependency-and-risk-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill dependency-and-risk-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/pmo/skills/dependency-and-risk-management .github/skills/dependency-and-risk-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dependency-and-risk-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/dependency-and-risk-management into .github/skills/dependency-and-risk-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dependency-and-risk-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill dependency-and-risk-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount dependency-and-risk-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/pmo/skills/dependency-and-risk-management .opencode/skills/dependency-and-risk-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dependency-and-risk-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/dependency-and-risk-management into .opencode/skills/dependency-and-risk-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dependency-and-risk-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dependency-and-risk-management- GitHub stars
- 2k
- Token cost
- ~926 tokens
- SKILL.md length
- 538 words
- Files
- 2 (incl. references)
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work.
- Tasks that involve Legal risk assessment
- SKILL.md covers Dependencies are commitments…, A risk register people…, Mitigate, or accept explicitly and Escalate early and specifically, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dependency And Risk Management is an agent skill from cbrock84/headcount. Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work. Use this to build a risk register that gets used, manage dependencies between teams, decide what to escalate and when, or work out why the same risks keep materializing unmanaged.
Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).
It sits in Legal & Compliance, covering Legal risk assessment. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
When your agent uses it
- Tasks that involve Legal risk assessment
Example prompts
- “Use the dependency-and-risk-management skill to manage delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating…”
- “/dependency-and-risk-management”
What it can do on your machine
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dependency And Risk Management loads about 926 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 538 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 538 words, ~926 tokens.
Download SKILL.mdSave it as
.claude/skills/dependency-and-risk-management/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- dependency-and-risk-management
- description
- Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work. Use this to build a risk register that gets used, manage dependencies between teams, decide what to escalate and when, or work out why the same risks keep materializing unmanaged.
Dependency and risk management
This is delivery risk: what could prevent this work from landing. Enterprise risk — the framework,
appetite and register at company level — is legal-risk:enterprise-risk, and the two should not be
merged.
Dependencies are commitments or they are wishes
A dependency in your plan that the owning team has not agreed to, with a date they have committed to, is a wish. Most plans contain several.
For each: what exactly is needed, from whom by name, by when, and what happens if it is late. Then confirm it with the owning team in a way they would recognize as a commitment — an item on their plan, not a mention in a meeting.
Track dependencies both ways. Teams reliably track what they are owed and forget what they owe, which is why everyone believes they are being let down.
The dangerous ones are transitive: your dependency has a dependency you cannot see. Trace at least one hop further than feels necessary, particularly where a shared specialist or a single team appears repeatedly.
A risk register people actually use
Most registers are written once for a gate and never opened. What makes one useful:
- Specific. "Integration delay" is a topic. "Vendor's API v2 is not released until March; our migration starts in February" is a risk you can act on.
- Sized on both axes — likelihood and impact — because the response differs entirely between a likely nuisance and an unlikely catastrophe.
- Owned by someone who can act, not by the project manager who can only report.
- Carrying a decision date — the point past which mitigation is no longer possible. This is the field most often omitted and the one that makes the register operational rather than decorative.
Review by exception: what changed, what is approaching its decision date. Reading the whole register aloud is how registers stop being read.
Show full SKILL.md (230 more words)Show less
Mitigate, or accept explicitly
Four responses: avoid by changing the plan, reduce likelihood or impact, transfer to someone better placed to carry it, or accept. Acceptance is legitimate and must be explicit, with a named accepter — an unacknowledged acceptance is just an unmanaged risk.
Distinguish mitigation from contingency. Mitigation lowers the chance; contingency is what you do when it happens anyway. Serious risks need both, and contingency needs to be prepared before it is required.
Escalate early and specifically
An escalation naming the decision needed, the options, and the date by which it is needed gets resolved. A general expression of concern gets acknowledged and nothing happens.
Escalate when the decision exceeds your authority or the decision date is approaching — not when the risk has already materialized, at which point it is a status report.
Sources
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Never
- Carry a dependency the owning team has not committed to.
- Log a risk without an owner who can act on it.
- Accept a risk without naming who accepted it.
- Escalate a concern without naming the decision required.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in plugins/pmo/skills/dependency-and-risk-management of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Dependency And Risk Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dependency And Risk Management this skillcbrock84/headcount | 2k | — | ~926 | Automated safety check: Pass | MIT | |
| Product Launch Legal Reviewanthropics/claude-for-legal | 9.6k | 2 repos | ~5k | Automated safety check: Pass | Apache-2.0 | |
| Legal Risk Visualizationzh-xx/legal-assistant-skills | 174 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Contract Renewal Trackeranthropics/claude-for-legal | 9.6k | 2 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Deep Risk Analysiszubair-trabzada/ai-legal-claude | 1.8k | — | ~1.9k | Automated safety check: Pass | None | |
| Canghe Tianyanchafreestylefly/canghe-skills | 461 | — | ~2.4k | Automated safety check: Pass | None |
Similar skills
- Official
Legal Risk Visualization
zh-xx/legal-assistant-skills
法律风险结构化分析与可视化。基于法律分析文本，执行五步风险抽取模型， 生成四层可视化输出（雷达图数据、风险矩阵、影响路径图、决策树）。
- Official
Contract Renewal Tracker
anthropics/claude-for-legal
Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.
Deep Risk Analysis
zubair-trabzada/ai-legal-claude
Clause-by-clause contract risk analysis with severity scoring, financial exposure estimates, and prioritized remediation guidance
Canghe Tianyancha
freestylefly/canghe-skills
Generates Tianyancha-style company and industry insight dashboards from researched enterprise data.
- Official
EU AI Act System Inventory
anthropics/claude-for-legal
Maintains a register of AI systems under the EU AI Act, recording each system's role and risk tier separately, because both can differ from one system to the next.
More from cbrock84/headcount
All 178 skills in this repoAgent Hierarchy
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
Account Based Marketing
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
Activation
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
AI ML Governance
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
AI Research Analyst
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
Related
Categories
Questions about Dependency And Risk Management
What does Dependency And Risk Management do?
Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work. Dependency And Risk Management is an agent skill from cbrock84/headcount. Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work.
When should I use Dependency And Risk Management?
Dependency And Risk Management fits situations like: tasks that involve Legal risk assessment.
How do I install Dependency And Risk Management in Claude Code?
Run `npx skills add cbrock84/headcount --skill dependency-and-risk-management -a claude-code`. Or copy the skill folder (plugins/pmo/skills/dependency-and-risk-management in cbrock84/headcount) into .claude/skills/dependency-and-risk-management in your project. Claude Code loads it when a task matches its description.
How do I install Dependency And Risk Management in Codex?
Run `npx skills add cbrock84/headcount --skill dependency-and-risk-management -a codex`. Or copy the skill folder (plugins/pmo/skills/dependency-and-risk-management in cbrock84/headcount) into .agents/skills/dependency-and-risk-management in your project. Codex loads it when a task matches its description.
Can I use Dependency And Risk Management in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill dependency-and-risk-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dependency-and-risk-management, .gemini/skills/dependency-and-risk-management, .github/skills/dependency-and-risk-management and .opencode/skills/dependency-and-risk-management in your project.
What does Dependency And Risk Management need to run?
SKILL.md names no scripts, command-line tools or credentials: Dependency And Risk Management is instructions for the agent only.
Does Dependency And Risk Management access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Dependency And Risk Management safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dependency And Risk Management use?
Dependency And Risk Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dependency And Risk Management use?
About 926 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 245 tokens, read only when the agent opens those files.
What are the alternatives to Dependency And Risk Management?
Skills that share tags, products or a category with Dependency And Risk Management: Product Launch Legal Review (anthropics/claude-for-legal, 9.6k stars), Legal Risk Visualization (zh-xx/legal-assistant-skills, 174 stars), Contract Renewal Tracker (anthropics/claude-for-legal, 9.6k stars) and Deep Risk Analysis (zubair-trabzada/ai-legal-claude, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dependency And Risk Management?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.