agentleFS
Sign inStart free
MRCalderon3DMRCalderon3D/everything-game-dev-code/skills/workflow/risk-register/SKILL.md

risk-register

Skill105 starsChanged 8 months agoMITView on GitHub

Identify, track, and revisit the risks most likely to derail scope, quality, budget, or release readiness.

10 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

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    keep the register visible during milestone reviews

    line 29
  2. Distinctive:

    Keep this skill aligned with the relevant rules layer and current project documentation.

    line 59
  3. Distinctive:

    If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

Risk Register

Purpose

Identify, track, and revisit the risks most likely to derail scope, quality, budget, or release readiness.

Use When

  • planning major milestones
  • the project depends on new tech or external dependencies
  • scope or platform targets have changed

Inputs

  • milestone plan
  • technical unknowns
  • dependency map
  • team and vendor constraints

Process

  1. list risks by domain and owner
  2. score probability, impact, and trigger conditions
  3. define mitigation, fallback, and review cadence
  4. flag risks that require prototype or spike work
  5. keep the register visible during milestone reviews

Outputs

  • risk register
  • mitigation plan
  • trigger checklist
  • prototype or spike recommendations

Quality Bar

  • produces a current source of truth, not disconnected notes
  • names owners, risks, and next actions explicitly
  • separates decisions from assumptions and open questions

Common Failure Modes

  • outdated docs that no longer match reality
  • plans with no owner or no exit criteria
  • hiding risks until they become schedule blockers

Related Agents

  • producer
  • planner
  • architect
  • release-manager

Related Commands

  • milestone-plan
  • plan
  • release-check

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

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